In my first installment about converged Infrastructure, I gave an outline of what it is, and how it will change the way in which IT infrastructure is managed.
In this installment, I’ll go a bit deeper and explain the source of capital and operational improvements converged Infrastructure offers – and why it’s such a compelling opportunity to pursue.
But first, the most important distinction to make between converged infrastructure and “the old way of doing business” is that management – as well as the technology – is also converged. Consider how many point-products you currently use for infrastructure management (i.e. other than managing your software stack).
This diagram at right has resonated with customers and analysts alike. It highlights, albeit in a stylized fashion, just how many point-products an average-sized IT department is using. This results in clear impact in
- Operational complexity – coordinating tool use, procedures, interdependencies and fault-tracking
- Operational cost – the raw expense it costs to acquire and then annually maintain them
- Capital cost – if you count all of the separate hardware components they’re trying to manage
What might be possible if you could virtualize all of the physical infrastructure components, and then have a single tool to manipulate them logically?
Well, then you’d be able to throw-out roughly 80% of the physical components (and associated costs) and reduce the operational complexity roughly the same amount.
In all, we can go from roughly a dozen point-products down to just 2-3 (see diagram above). Now: What’s the impact on costs?
On the capital cost side, since I/O is consolidated, it literally means fewer NICs and elimination of most HBAs since they can be virtualized too. Consolidating I/O also implies converged transport, meaning fewer cables (typically only 1 per server, 2 if teamed/redundant). And a converged transport also allows for fewer switches needed on the network. Also remember that with few moving (physical) parts, you also have to purchase few software tools and licenses. See diagram below.
On the operational cost side, there are the benefits of simpler management, less on-the-floor maintenance, and even less power consumption. With fewer physical components and a more virtual infrastructure, entire server configurations can be created more simply, often with only a single management tool. That means creating and assigning NICs, HBAs, ports, addresses and world-wide names. It means creating segregated VLAN networks, creating and assigning data and storage switches. And it means automatically creating and assigning boot LUNs. The server configuration is just what you’re used to – except it’s defined in software. And all from a single unified management console. The result: Buying, integrating and maintaining less software.
Referencing the diagram at right, here's what this looks like on a physical level is fewer components: Costly NIC and HBA cards are virtualized, with their physical transport now consolidated over Ethernet ports, and switches/cables now replaced by a logically-configured switch.Ever wonder why converged infrastructure is developing such a following? It’s because physical simplicity breeds operational efficiency. And that means much less sustained cost and effort. And an easier time at your job.
Next installment: What Converged Infrastructure is not.
Posts
1 comment:
Now that much of the physical and operational aspects are virtualized and cost savings realized, I would think there is an offset in terms of management and monitoring (old tools against newer virtualized infrastructure don't necessarily scale)
Do you have a benchmark for management, maintenance and support costs?
Post a Comment