One of the key characteristics of cloud—whether it’s public, private, or hybrid—is the ability to scale in whatever dimension makes sense for your workloads’ needs. The traditional direction for storage scaling was up—adding more shelves of capacity as needed. But now that capacity generally comes with a lot of all-flash IO, and so the controller becomes the bottleneck. And piling up shelves of capacity only creates a growing failure domain—lose the controllers and lose the data on ALL the shelves to which they are attached.
And so more organizations have shifted the direction of their scale plans to out. This entails adding more nodes—interconnecting arrays to join their controllers together, and adding both capacity and performance. This adds redundancy of controllers and increases your ability to put all that performance to effective use.
The challenge here is to keep storage scale-out as simple as say… scaling compute. If you need more compute resources for your cloud workloads, you simply install a new virtualized server, add it to the resource pool and automatic live migration optimizes the VMs across the pool.
Fortunately, the previously mentioned category of VM-aware storage has this visibility across your pool and capability to optimize the placement of every VM. Simply add another node of VM-aware storage, and intelligent algorithms re-distribute VMs to best balance capacity and performance requirements. Best of all, it all happens automatically without admin intervention.
Now remember that scale also means spinning workloads up and down. When we’re talking about scale in the context of cloud, bear in mind that it should be possible to expand the size of a resource pool as well as shrink resource pools when workload demands begin to diminish.
But, there is a real difference in achieving scale in a public cloud as opposed to a private cloud, which means that the two sides of your hybrid cloud will have somewhat different capabilities here. On the public cloud front, you can temporarily provision a resource and then, when you’re done with it, deprovision that resource on the fly without incurring any capital expenditure costs. On the private side of your hybrid cloud, if you run out of a resource, you’ll need to buy more and deploy it before you can provision it for use. If you have a temporary workload, even if you deprovision the resource when you’re done with it, the resource still physically exists in your data center and you’ve paid for it. In a private data center, by deprovisioning resources, you’re making them available for use by other workloads.
Put concisely, on the public side, you get the full cloud experience, which includes both economics and operational efficiency. On the private side of your hybrid cloud, the focus is on making things easier to expand and contract and to make more efficient use of your resources.