There were quite a few announcements this week at the HP Technology Forum in Vegas.Â Several of these announcements were extremely interesting, of these the ones that resonated the most with me were:
Iâ€™m not familiar with the Superdome 1 nor am I in any way an expert on non x86 architectures.Â In fact thatâ€™s exactly what struck me as excellent about this product announcement.Â It allows the mission critical servers that a company chooses to, or must run on non x86 hardware to run right alongside the more common x86 architecture in the same chassis.Â This further consolidates the datacenter and reduces infrastructure for customers with mixed environments, of which there are many.Â While there is a current push in some customers to migrate all data center applications onto x86 based platforms, this is not: fast, cheap, or good for every use case.Â Superdome 2 provides a common infrastructure for both the mission critical applications and the x86 based applications.
For a more technical description see Kevin Houston’s Superdome 2 blog: http://bladesmadesimple.com/2010/04/its-a-bird-its-a-plane-its-superdome-2-on-a-blade-server/.
Note: As stated Iâ€™m no expert in this space and I have no technical knowledge of the Superdome platform, conceptually it makes a lot of sense and it seems like a move in the right direction.
There was a lot of talk in some of the key notes about common look feel and infrastructure of the separate HP systems (storage, servers, etc.)Â At first I laughed this off as a â€˜who caresâ€™ but then I started to think about it.Â If HP takes this message seriously and standardizes rail kits, cable management, components (where possible), etc. this will have big benefits for administration and deployment of equipment.
If youâ€™ve never done a good deal of racking/stacking of data center gear you may not see the value here, but I spent a lot of time on the integration side with this as part of my job.Â Within a single vendor (or sometimes product line) rail kits for server/storage, rack mounting hardware, etc can all be different.Â This adds time and complexity to integrating systems and can sometimes lead to less than ideal systems.Â For example the first vBlock I helped a partner configure (for demo purposes only) had the two UCS systems stacked on top of one another on the bottom of the rack with no mounting hardware.Â The reason for this was the EMC racks being used had different rail mounts than the UCS system was designed for.Â Issues like this can cause problems and delays, especially when the people in charge of infrastructure arenâ€™t properly engaged during purchasing (very common.)
Overall I can see this as a very good thing for the end user.
This is the piece that really grabbed my attention while watching the constant Twitter stream of HP announcements.Â HP FlexFabric brings network consolidation to the HP blade chassis.Â I specifically say network consolidation, because HP got this piece right.Â Yes it does FCoE, but that doesnâ€™t mean you have to.Â FlexFabric provides the converged network tools to provide any protocol you want over 10GE to the blades and split that out to separate networks at a chassis level.Â Hereâ€™s a picture of the switch from Kevin Houstonâ€™s blog: http://bladesmadesimple.com/2010/06/first-look-hps-new-blade-servers-and-converged-switch-hptf/.
The first thing to note when looking at this device is that all the front end uplink ports look the same, so how do they split out Fibre Channel and Ethernet?Â The answer is Qlogic (the manufacturer of the switch) has been doing some heavy lifting on the engineering side.Â Theyâ€™ve designed the front end ports to support the optics for either Fibre Channel or 10GE.Â This means youâ€™ve got flexibility in how you use your bandwidth.Â The ability to do this is an industry first, although the Cisco Nexus 5000 hardware ASIC is capable and has been since FCS it was implemented on a per-module basis rather than per-port basis like this switch.Â
The next piece that was quite interesting and really provides flexibility and choice to the HP FlexFabric concept is their decision to use Emulexâ€™s OneConnect adapter as the LAN on Motherboard (LOM.)Â This was a very smart decision by HP.Â Emulexâ€™s OneConnect is a product that has impressed me from square one, it shows a traditionally Fibre Channel company embracing the fact that Ethernet is the future of storage but not locking the decision into an Upper Layer protocol (ULP.)Â OneConnect provides 10GE connectivity, TCP offload, iSCSI offload/boot, and FCoE capability all on the same card, now thatâ€™s a converged network!Â HP seems to have seen the value there as well and built this into the system board.Â
Take a step back and soak that in, LOM has been owned by Intel, Broadcom, and other traditional NIC vendors since the beginning.Â Emulex until last year was looked at as one of two solid FC HBA vendors.Â As of this week HP announced the ousting of the traditional NIC vendor for a traditional FC vendor on their system board.Â Thatâ€™s a big win for Emulex.Â Kudos to Emulex for the technology (and business decisions behind it) and to HP for recognizing that value.
Looking a little deeper the next big piece of this overall architecture is that the whole FlexFabric system supports HPâ€™s FlexConnect technology which allows a server admin to carve up a single physical 10GE link into four logical links which are presented to the OS as individual NICs.
The only drawback I see to the FlexFabric picture is the fact that FCoE is only used within the chassis and split into separate networks from there.Â This can definitely increase the required infrastructure depending on the architecture.Â Iâ€™ll wait to go to deep into that until I hear a few good lines of thinking on why that direction was taken.
HP had a strong week in Vegas, these were only a few of the announcements, several others including mind blowing stuff from HP labs (start protecting John Conner now) can be found on blogs and HPâ€™s website.Â Of all of the announcements FlexFabric was the one that really caught my attention.Â It embraces the idea of I/O consolidation without clinging to FCoE as the only way to do it and it greatly increases the competitive landscape in that market which always benefits the end-user/customer.
Comments, corrections, bitches moans, gripes and complaints all welcome.