Why does it take HP so long to integrate their products
I was talking with a fellow VMware nerd today about cloud and infrastructure gear. And I can’t help but wonder why it takes HP so long to execute on integrating their products, mostly around the support tools. Look HP owns a complete stack now, network, compute, storage and software. Along with their suites of tools that you need to use to manage all these devices independently. To me this is their biggest failure and does not appear to be getting fixed anytime soon.
This is a big bonus of working Cisco UCS because there is just one place that I need to go to configure, manage, patch a blade environment. With HP I might have to use the Onboard Administrators, Virtual Connect manager and HP SIM. This seems like such a no brainer that HP could have fixed years ago, because the HP Blade systems have been around for years.
So if HP wants to rule the market in the Cloud era they need to reduce their tools into less management points. I should be able to do everything in one console for compute and if they could roll in storage to this also would be a huge win. And if they are properly motivated they can. Now a unified tool for automation of hardware that could reach into VMware with API’s would be the next big win. I know they are working on some of this but last that I saw it still sounded like there would be too many moving pieces.
So HP I challenge you to solve this issue with your massive amount of Talent, code and other resources. You need to become innovate again and make products that people want to own and desire for other reasons than you have a large install base and are cheaper.
If you want some examples you can read my post about the comparison of what tools it takes to manage HP vs Cisco blades chassis here.
About Brian Suhr
Brian is a VCDX5-DCV and a Sr. Tech Marketing Engineer at Nutanix and owner of this website. He is active in the VMware community and helps lead the Chicago VMUG group. Specializing in VDI and Cloud project designs. Awarded VMware vExpert status 6 years for 2016 - 2011. VCP3, VCP5, VCP5-Iaas, VCP-Cloud, VCAP-DTD, VCAP5-DCD, VCAP5-DCA, VCA-DT, VCP5-DT, Cisco UCS Design