Skip to main content

HP Software Universe

I attended and spoke at HPSU this year. It was a good conference, and HP is making a lot of progress on the products which we are very interested in. I'm going to go into each of these and explain some of what I saw, and what we are up to with each product.

  • HP NAS
    • New UI is coming down the road.
    • Additional of bare metal provisioning.
    • Internally
      • We are moving from 7.0 to 7.2 here in the next few weeks.
      • We are just finishing up a MS-SQL Multimaster setup with the UK this week. It's been painful, and taken us 4 attempts now, but we are close.
  • HP SAS
    • Some interesting stuff with other customers, best practices, and other tips on it.
    • Internally
      • We are moving towards a small SAS deployment in 2008, probably 200-400 systems. Just firming up some budgets, since we are splitting the cost among a couple budgets.
  • HP OO
    • Tons of new content, which makes OO above and beyond.
    • Multimaster is coming down the pipe, which should be really nice. Since the platform of OO is very similar to NAS it should be easily done.
  • HP BAC/RUM
    • Lots of progress in RUM, especially generic TCP Monitoring.
    • Correlation of alarms coming into BAC.
    • Baselining and auto thresholding – REALLY GOOD TO SEE THIS IN BPM!
      • They have taken this another level higher, and they show you how it would have worked if you use the suggested thresholds.
    • Problem management and workflow ideas which should help the usage.
    • Integration of OM into UCMDB, and other feeds to and from the UCMDB.
  • HP BPM
    • Interesting customer presentation of a large distributed BPM they deploy at branch offices. Very good use case, and well managed. They deal with BPM problems in a good way.
  • HP OM
    • Sitescope integration in OM 8.1.
    • New enhancements around usability and reporting.
    • HTTP agent is excellent, and much easier to deal with than the old agent.

Comments

Popular posts from this blog

Dynatrace Growth Misinformation

For my valued readers: I wanted to point out some issues I’ve recently seen in the public domain. As a Gartner analyst, I heard many claims about 200% growth, and all kind of data points which have little basis in fact. When those vendors are asked what actual numbers they are basing those growth claims on, often the questions are dodged. Dynatrace, recently used the Gartner name and brand in a press release. In Its First Year as an Independent Company, Gartner Ranks Dynatrace #1 in APM Market http://www.prweb.com/releases/2015/06/prweb12773790.htm I want to clarify the issues in their statements based on the actual Gartner facts published by Gartner in its Market Share data: Dynatrace says in their press release: “expand globally with more than three times the revenue of other new generation APM vendors” First, let’s look at how new the various technologies are: Dynatrace Data Center RUM (DCRUM) is based on the Adlex technology acquired in 2005, but was cr

Vsphere server issues and upgrade progress

So I found out that using the host update tool versus Vcenter update manager is much easier and more reliable when moving from ESXi 3.5 to 4.0. Before I was using the update manager and it wasn't working all that reliably. So far I haven't had any issues using the host update tool. I've done many upgrades now, and I only have 4 left, 3 of which I am doing this weekend. Whenever I speak to vmware they always think I'm using ESX, when I prefer and expect that people should move to the more appliance model of ESXi. With 4.0 they are pretty much on par, and I'm going to stick with ESXi. On one of my vsphere 4.0 servers (virtualcenter) its doing this annoying thing when I try to use the performance overview:   Perf Charts service experienced and internal error.   Message: Report application initialization is not completed successfully. Retry in 60 seconds.   In my stats.log I see this.   [28 Aug 09, 22:28:07] [ERROR] com.vmware.vim.stats.webui.startup.Stat

Misunderstanding "Open Tracing" for the Enterprise

When first hearing of the OpenTracing project in 2016 there was excitement, finally an open standard for tracing. First, what is a trace? A trace is following a transaction from different services to build an end to end picture. The latency of each transaction segment is captured to determine which is slow, or causing performance issues. The trace may also include metadata such as metrics and logs, more on that later. Great, so if this is open this will solve all interoperability issues we have, and allow me to use multiple APM and tracing tools at once? It will help avoid vendor or project lock-in, unlock cloud services which are opaque or invisible? Nope! Why not? Today there are so many different implementations of tracing providing end to end transaction monitoring, and the reason why is that each project or vendor has different capabilities and use cases for the traces. Most tool users don't need to know the implementation details, but when manually instrumenting wi