June 17, 2009

Exclusive review: HP BladeSystem Matrix

HP's state-of-the-art blade server system and array of automation tools haven't squeezed all manual labor out of service provisioning, but they show the automated and adaptive datacenter is within reach

Bottom Line
HP BladeSystem Matrix incorporates a wide array of moving parts and ties them together well. It’s still a significantly complex solution, but part of the purchase price includes integration. The hardware is impressive, and the management tools are functional if not completely polished. HP might not have reached the Holy Grail of general datacenter automation just yet, but it's definitely on the right track.

During the Big Dig, the city of Boston erected a sign saying, "Rome wasn't built in a day. If it was, we would have hired their contractor." That's a good way to describe the general state of affairs regarding the ideal of divorcing services from hardware and pushing server management away from the physical layer. HP's BladeSystem Matrix goes a long way toward realizing this ideal of an automated datacenter, providing a wide array of very useful tools and functions, but falling just shy of the lofty goal of truly hands-free datacenter service deployment. Of course, nobody else has reached that particular goal either.

Although Matrix is newly packaged, it's not accurate to portray it as a completely new product. It's built on the foundation of HP Systems Insight Manager, with a heaping helping of associated services such as rapid-deployment software (HP's RDP), Microsoft Active Directory, server virtualization (VMware, XenServer, or Microsoft Hyper-V), and hardware in the form of the HP BladeSystem c-Class blade chassis and HP StorageWorks EVA Fibre Channel storage framework. At the center of all these moving parts sits the new piece: HP Insight Orchestration.

[ Take InfoWorld's scrolling tour through service provisioning and management in HP BladeSystem Matrix. ]

It's probably best to think of Insight Orchestration as, well, an orchestra conductor, weaving a multitude of players into a coherent symphony. The sheet music for this particular piece is based on templates created via a drag-and-drop, Flash-based interface, and reference everything needed to build a single server or a group of physical or virtual servers, including all network and storage links. With the possible exception of Scalent's Virtual Operating Environment, nothing is as close to defining the automated or adaptive datacenter as HP's Insight Orchestration.

From the ground up
It all starts with the hardware. HP's Matrix product is built from existing HP hardware offerings, including the EVA4400 and BladeSystem c7000 blade chassis. In the mix are the usual Fibre Channel SAN fabric switches and Ethernet switches. However, the two network switches really don't play into the overall picture. This is possible due to the 10G Ethernet modules and the 8Gb Fibre Channel links present in the chassis. Essentially, each chassis has all the bandwidth it needs with these links, releasing administrators and the Insight Orchestration software from the onus of having to interact at the layer-2 level to provide VLAN assignments and such.

The hardware in my test lab consisted of two c-Class chassis with a total of five blades, two EVA 4400 SAN arrays, two 8Gb Fibre Channel switches, and an HP ProCurve 5406zl switch with four 10G links and a few gigabit Ethernet links. This was the core of the Matrix solution. On the side were a few ProLiant DL 360 G5s running Microsoft Active Directory, the HP ProLiant Essentials Rapid Deployment Pack (RDP) server, and the HP Insight suite, including the Insight Orchestration software. All this hardware was separated into two racks, each roughly half full.

The setup and initial configuration of the Matrix product is not for the faint of heart. You must know your way around all the products quite well and be able to provide an adequate framework for the Matrix layer to function. Fortunately, HP currently sells the Matrix fully assembled only, and when the racks arrive, an HP integration tech comes along to get the solution up and running, provide some training, and do basic integration with an existing infrastructure.

Test Center Scorecard
20%20%20%20%10%10%
HP BladeSystem Matrix799978
8.3
Very Good

Close

On Twitter now

Server virtualization

Powered by Twitter

White Paper

D2D Virtual Tape Library Replication Primer

This whitepaper explains the terminology and concepts behind Data Replication technologies and establishes some sizing rules through worked examples. Learn the new paradigm in disaster tolerance—protect data anywhere.

Download now »

Trial

Free 30-Day Desktop Virtualization Trial

Download a free 30–day trial and experience how XenDesktop delivers a pristine, on–demand desktop experience to users on whatever device they choose, while cutting IT complexity and costs.

Download now »

White Paper

Why Your Firewall, VPN, and IEEE 802.11i Aren't Enough to Protect Your Network

The emergence of WLANs has created a new breed of security threats to enterprise networks.

Included in HP ProCurve WLAN solutions is security technology that alleviates threats from WLANs through:
* Monitoring wireless activity inside and out of the enterprise
* Classifying WLAN transmissions into harmful and harmless
* Preventing transmissions that pose a security threat to the enterprise network
* Locating participating devices for physical remediation

Download now »
clintre 17-Jun-09 9:39am
HP has spent a lot of time playing catch up to at first Egenera and now Cisco UCS. They are about 70% of the way there to a complete solution. It is still far too complex in how you have to use several products to compete with one.
shinelite 24-Jun-09 5:04am
I have recently seen Matrix at the HP Tech Forum. Matrix uses tried and true HP components such as HPSIM, RDP, Scripting tools, ICE and adds Orchestration. This is quite an elegant solution (not perfect) but great none the less. Matrix was developed before UCS. Egenera has way too many dependencies and 100% more moving parts and is difficult to troubleshoot. Can you buy a single Cisco UCS component today? Okay, one or two…. How long has Cisco been building servers and the server goodies? What is Cisco’s market share in that space? Where are all those servers Cisco keeps talking about? UCS requires a DataCenter rebuild to work! UCS has dependencies on NEW CISCO switches (VnTags) and full implementation of FCoE. Do the math and their own designs have little or no bandwidth per server. Cisco’s vision – Break the entire DataCenter and rebuild it with our stuff with inadequate response times… Cisco wants to own the data path and force everything to the backbone and back. Oh, and what OS choice, Storage choice, Server choice, Hyper-Visor choice and Switch choice do you have with Cisco? Answer to all above questions - 1 (Linux, EMC, Cisco, VMWare and Cisco) I wouldn’t call that open or smart. Cisco is trying to brute force their way into the hearts and minds of the server teams through the network and C level management. It ain’t working. They have been here and understand 0% of the server, OS and application. No Kool-Aide here please.
dags 26-Jun-09 11:53am
So lets cut through the FUD. You can buy Cisco UCS today and there are more components than two, as Cisco announced support for racks as well as blades. Using your points on marketshare and time, then customers should not evaluate HP for switching, collaboration, IP voice, wireless, and fibre-channel. What matters is what vendor is solving a problem. Putting a mask and a body around a bunch of single tools, operating as a system, is not a solution. The rebuild of the Data Center is in the most polite way I can put it, IS BS. This shinelite is clearly an HP employee or someone who is massively punch drunk on this marketing BS. What about Virtual Connect? Forcing a customer to buy VC Ethernet to get FC - gimme a break. Everything leaving a UCS system is standard Ethernet and Fibre-channel - another BS point. UCS is a system, not an assembly of loosely integrated components. Using that debate, I guess any IO module in an HP c-Class server can leverage the Virtual Connect feature set... Not. Bandwidth per server. I guess you should pay for a 10G connection and only deliver 2.5G per interface, or whatever 100Mbps increment you create - which then - eliminates any single interface from sending at 10G. Not so in UCS. You are also limited to 4 virtual interfaces per Flex-10 module. And.. they are Ethernet only. UCS can support up to 128 per adapter. Remember FCoE is a ratified standard. Those vendors slinging FUD to the customer base is doing so because they do not have a product. shinelite is also incorrect on the OS and hypervisor support. To all readers, do your due diligence and ignore this posters version of the national enquirer post. To understand whether something is open or smart, you need to pick up your head from the HP sales reps and their marketing BS. No that would be open and smart.

Sign up to receive InfoWorld Resource Alerts

Subscribe to the Virtualization Newsletter

Receive a weekly digest of the latest news, analysis, views, and opinions about the growing world of virtualization.

©1994-2009 Infoworld, Inc.