Update: As has been pointed out by numerous people (comments and twitter) FlexPod is indeed hypervisor agnostic. Check out the Cisco DesignZone for FlexPod to see all the validated solutions. Learning that changes the details of this post slightly but the bottom line and overall sentiment is still the same. Thanks to @friea and Satinder for your help!
As if we need more information or opinions on this subject but much of what has already been written has been written by partners, manufacturers, or journalists. I am a customer and full disclosure I am a NetApp customer. Actually a pair of Nexus 5k’s short of a FlexPod customer, too.
You all know what the differences are between those solutions by now (if not see HERE). Here is a regurgitation of a few main points:
- Vblock is not a reference architecture and is not really included in this comparison. Vblock has strict requirements for software versions and only included EMC, VMware, and Cisco components.
- FlexPod is a reference architecture that includes NetApp, Cisco, and VMware (see update above). Since it is a reference architecture and not a prebuilt and validated solution it is less rigid. However, it still requires components from those 2 vendors.
- VSPEX is also a reference architecture that includes components from several more vendors including Brocade, Microsoft, and Citrix.
Without getting into the debate on reference architecture (FlexPod, VSPEX) vs prepackaged solution (Vblock) I do want to compare and contrast the reference architectures themselves. Vblock is a great solution where it fits but it is really not part of the reference architecture discussion. FlexPod is closed to Cisco and VMware along with NetApp storage. No one can argue that those are not best of breed components but there are many customers out there that already have infrastructure with Citrix, Brocade, or god forbid Hyper-V. Those customers have barriers to rip-and-replace and the reference architectures do allow for some flexibility on the journey.
What I see with VSPEX, though, is really exciting. It will allow partners to co-brand their solution and give them the flexibility to use different hypervisors (Microsoft, Citrix, VMware) and networking (Cisco, Brocade). Obviously you’re locked into EMC storage with VSPEX but so too are you locked into NetApp with FlexPod. This move, in my opinion, really shows EMC’s commitment to changing its reputation with the partner community. Now don’t get me wrong, what value is co-branding really adding? But it does provide a mechanism for the partner to feel more engaged and provide that “This is OUR solution, not EMC’s. We, the partner, are providing this value to you.” The partner can then have additional instruments for revenue generation in terms of support, managed services, and consulting around the solution they’ve built around the VSPEX reference architecture.
Having said all that I think FlexPod has established itself as a great reference architecture. Its adoption rate has been growing and it is relatively mature. Since FlexPod is limited to VMware and Cisco it has an advantage of fewer options and better integration & management through tools such as Cloupia. It remains to be seen if VSPEX will produce a management and integration layer like that of Vblock and FlexPod but I think I can safely assume that it will.
The bottom line is that I feel as a customer it is better to have options especially if I have existing non-VMware and non-Cisco infrastructure. I also already have established, trusted relationships with my EMC and NetApp partners who already know my environment. So allowing them to build us a custom solution based on a proven (or yet to be proven) reference architecture would be a great opportunity. A little competition also helps the market innovate and continue to produce great partners on both sides of the aisle. Now the lingering question I have is how long until Dell produces its competitor?





Recent Comments