Make your Data Center sing with Converged Architectures

What does this CI concept mean? A converged architecture is, to put it simply, a purpose built system, with the inclusion of Server, Storage, and Network, designed to ease the build of a centralized environment for the data center. By this I mean, there’re servers and storage combined with networking, so that with very minor configuration after plugging the equipment in, one will be able to manage the environment as a whole.

In the early days of this concept, prior to the creation of VCE, I worked on a team at EMC called the vSpecialists. Our task was to seek out appropriate sales opportunities wherein an architecture like this would be viable, and qualify our prospects for what was called the vBlock. These included Cisco Switches, the just released Nexus line, Cisco Servers, the also freshly released UCS blades and EMC storage. These vBlocks were very conscripted toward sizing, and very dedicated to housing virtualized environments. VMware was critical to the entire infrastructure. In order for these systems to be validated by the federation, all workloads on these would need to be virtualized. The key, and the reason that this was more significant than what customers may already have in their environments was the management layer. A piece of software combining UCS Manager, IOS for the Switch layer, and storage management was pulled together called Ionix. This was where the magic occurred.

Then came a number of competitors. NetApp released the FlexPod in response. The FlexPod was just that. More flexible. Workloads were not required to be virtual exclusively, obviously, storage in this case would be NetApp, and importantly, the customer would be able to configure these based less rigidly on their sizing requirements, and build them up further as they needed.

There were other companies, most notably Hewlett Packard and IBM that built alternative solutions, but the vBlock and FlexPod were really the main players.

After a bit of time, a new category was created. This was called HyperConvergence. The early players in this field were Nutanix and Simplivity. Both these companies built much smaller architectures. These are called Hyper Converged, most reasonably. They were originally seen as entry points for organizations looking to virtualize from a zero point, or point type solutions for new circumstantial projects like VDI. They’ve grown both in technology and function to the point where companies today are basing their entire virtual environments on them. While Nutanix is leveraging new OS models, building management layers onto KVM and replication strategies for DR, Simplivity has other compelling pieces, such as a storage deduplication model, and replication making for compelling rationale for pursuing.

There are also many new players in the HyperConverged marketplace, making it the fastest growing segment of the market now. Hybrid cloud models are making these types of approaches very appealing to IT managers setting direction for the future of their data centers. Be sure to look for new players in the game like Pivot3, Scale Computing, IdealStor, and bigger companies like Hewlett Packard and the EVO approach from Vmware with Evo Rail and Evo Rack getting it’s official launch this week at VMworld.

  • Does anyone have experiencing in creating a SW dashboard view of an enterprise FlexPod?  Looking for some mix of API/SNMP polling at the component/location level that bubbles up into a North America dashboard for overall status of computer/network/storage as well as a HyperV and VMware status widget ... This might be asking for the kitchen sink, but if you have good examples of the components like a sub-dashboard for UCS, and one for NetApp, and another for ESXi/VC that would be most appreciated to hear of how you might have built that out and which major metrics you are monitoring and alerting on.  

  • We are actually moving towards that direction and are currently running with 3 of our first Simplivity nodes emoticons_happy.png

  • I have always been interested in working with one of these converged architectures; unfortunately, we need more flexibility than what those can currently offer.  I would like to see (and if there is something out there please let me know) that offers some of the simplicity that is touted by the converged architectures with the flexibility of a more modular architecture.

  • I think that you're right, in many ways. I think that often, the advancements made in technology make for new issues, sometimes worse issues that must be resolved. To leverage your example, that of VOIP, the potential benefits of telecom merging with network is inescapable, but wow, the complexities are daunting.

    I'd also agree that the best recipient of these struggles is the vendor. But, these are the growing pains of the industry. There aren't many technologies in the data center that last as long as telecom switches. If it works, it works.... But when changes need to be made it requires significant investment.

    In the data side of the equation, lifecycle for hardware is far less. One typically anticipates the equipment to last for the duration of the depreciation of the equipment. If only software were able to advance as quickly.

  • As a Network Analyst and former Engineer, my focus has been on up time and reliability.  Convergence entered my life back in the '90's when network hardware designers and their companies started working toward the converged network theme: "Why build three parallel networks (Data, Voice, and Video) when you can save money by running all three on the same wire?"

    Well, the road from back then to today's been mighty rocky.  It's proven that putting all your eggs into one basket is a poor idea indeed, since when the network's down, EVERYTHING's down.

    Yep, build up to reduce that likelihood, buy hardware with multiple power supplies, get bigger power supplies (because powering VOIP is a hidden and unadvertised cost of moving to VOIP), go with VSS paired Distribution switches with port-channels to Access switches that run off big chasses with dual supervisor modules, then upgrade the core to handle the extra traffic, then increase the complexity of the network configuration by adding QoS and CoS and ToS variables, then deal with WAN pipe bottlenecking, buy bigger pipes, replace all the optics to handle more throughput due to video needs, etc.

    You know who wins?

    Not the telephone users--they have more phone outages with VoIP than when their phones ran off the 20-year-old rock-solid phone switches.

    Not the network users--they're told by vendors they must have gig-to-the-desktop or their apps won't run (but NPM proves they're only using 5 and 11 KByte files most often).

    Not the Video users, since they've had to spend tons extra on replacing their hardware with new Codecs and as a result get told they have to throttle their broadcast-quality camera transmissions down to 768K or less because not all of their clients are in cities or sites that can get anything more than bonded T1's for WAN service.

    The ones who benefit are those who make, sell, and support the network equipment that had to be replaced and upgraded and monitored and upgraded over and over just to run those three networks on one.  The Cisco's and HP's of the world.

    I'm not saying they're evil.  I'm just floating the idea that network convergence isn't the money saver folks like HP or Cisco may claim it is.

    If "forewarned is forearmed," then you might starting thinking about parallels between the world I described and the world of Converged Data Center Architecture.

    Yep, I'm looking forward to the Cisco ACI data center infrastructure that will replace our traditional Cisco Nexus Core/Distribution/Access solution.  After it's designed and deployed, it should make life more transparent and easier for groups to see out of their silos, especially where VM-ware and Cisco UCS and ACI Networking converge.

    The dollars spent will be many.  But at what cost will a Converged Data Center Architecture come?  What will we learn (or have to relearn) about putting all our eggs into one basket?

Thwack - Symbolize TM, R, and C