For those organizations on the journey of transforming their datacenters to meet the demand of a modern IT consumption model, it’s easy to envision what cloud euphoria could/should look like. That’s mostly because vision is quite cheap – all it takes is a little imagination (maybe), a few Google queries, several visits by your favorite vendor(s), and perhaps a top-down mandate or two. The problem is execution can break the bank if the vision is not in line with the organization’s core objectives. It’s easy to get carried away in the planning stages with all the options, gizmos and cloudy widgets out there – often delaying the project and creating budget shortfalls. Cloud:Fail. But this journey doesn’t have to be difficult (or horrendously expensive). Finding the right solution is half the battle…just don’t go gluing several disparate products together that were never intended to comingle and burn time and money trying to integrate them. Sure you might eventually achieve something that resembles a cloud, but you’re guaranteed to hit several unnecessary pain points on the way.
Of course I’m not suggesting putting all your eggs in one vendor’s basket guarantees success. Nor am I suggesting that VMware’s basket is the only one that provides everything you’ll ever need for a successful cloud deployment. In fact, VMware prides itself with an enormous (and growing) partner ecosystem that provides unique approaches and technologies to cloudy problems and beyond. What I am suggesting, however, is the need to pick and choose wisely. Well integrated clouds = well functioning clouds = happy clouds and happy customers. Integration means common frameworks and interfaces, extensible API’s, automation via orchestration, app portability across clouds, and technologies that are purpose-built for the job(s) at hand. And as a bonus, integration can mean leveraging what you already have – an infrastructure awaiting the transformation of a lifetime. That’s right, the cloud journey should not be a rip-and-replace proposition.
There’s another major component to this – while I spend the majority of my time helping organizations and federal agencies adopt the cloud and transform their infrastructures, there’s often something else on the customer’s mind that can’t be ignored. It’s a long-term strategy delivered in nine datacenter-shattering words: “I want to get out of the infrastructure business”. I’m hearing this more often than not and it cannot be ignored. What they are referring to is the need to eventually shift workloads to public clouds rather than continue to invest in their own infrastructures. This strategy makes perfect sense. As the adoption of public cloud services increases, more and more CIO’s are finding new comfort levels in handing over their apps and workloads to trusted cloud providers, albeit slowly. But this also introduces new challenges. How does an organization well on its way to delivering an enterprise/private cloud to the business ensure that future adoption of public clouds does not mean starting from scratch? What about managing and securing those workloads just as you would in the private cloud? Public cloud providers need to be an extension of your private cloud, giving you the freedom of application placement, the ability to migrate workloads back and forth, and providing single-pane-of-glass visibility into all workloads and all clouds. This endeavor requires the right planning, tools, and frameworks to be successful.
Here are the top “asks” from customers currently on, or getting ready to start, this journey (in no particular order):
- Private cloud now…public cloud later (or both…now)
- Workload portability (across clouds / cloud providers)
- A holistic management approach
- End-to-end visibility
- Dynamic security
- Cloud-worthy scalability
If any of this is resonating, then you’re probably in a similar situation. CIO’s are pushing the deployment of private clouds while simultaneously considering public cloud options. Therefor the solution needs to deliver everything we know and love of the private cloud while laying down the framework for public cloud expansion. Problem is not many solutions out there can do this. Public cloud providers often run proprietary frameworks and management tools to keep costs low and private cloud solutions are generally focused on just that (being private).
VMware has put a lot of effort in leveraging the success of vSphere – the cloud’s critical foundation – to help take a controlling lead up the software stack and deliver a cloud solution for both private and public (i.e. hybrid) clouds. And through the VMware Service Provider Program (VSPP), they have also enabled a new generation of cloud service providers that build their offerings using the same vCloud frameworks available to enterprises. As a result, each and every one of these vCloud-powered service providers instantly becomes a possible extension of your private cloud, placing the power of the hybrid cloud – and all the “asks” above – at your fingertips.
Here’s what that looks like from a 1,00ft view…
Let’s review this diagram:
1 – Physical Infrastructure: commodity compute, storage, and network infrastructure.
2 – vSphere Virtualization: hardware abstraction layer and cloud foundation. Delivers physical compute, storage, and networks as resource pools, datastores, and portgroups (or dvPortgroups).
3 – Provider Virtual Datacenter (PvDC) and Organizational Virtual Datacenter (OvDC): delivered by vCloud Director as the first layer of cloud abstraction. resources are simply consumed as capacity and delivered on demand.
4 – vCenter Orchestrator: key technology for cloud integration, automation, and orchestration across native and 3rd-party solutions.
5 – vCenter Operations: holistic management framework for visibility into performance, capacity, compliance, and overall health.
6 – Security & Compliance: dynamic, policy-based security and compliance tools across clouds using vShield Edge and vCenter Configuration Manager (vCM)
7 – VMware Service Manager for Cloud Provisioning (VSM-CP): self-service web portal and business process engine tying it all together. Integrates with vCO for mega automation.
8 –vCloud Connector (vCC): single pane of glass control of clouds and workloads. enables workload portability to/from private and public vClouds and traditional vSphere environments.
Last but not least is the very important question of “openness” in the cloud (don’t get me started on heterogeneous hypervisors!). VMware spearheaded the OVF standard several years ago, which has been adopted by the industry as a whole as a means of migrating vSphere-based workloads to non-vSphere hypervisors (and the clouds above them) with metadata in tact. In fact, OVF remains a key technology in the Hybrid cloud scenarios and is an integral part of workload portability across clouds. OVF gives customers the ability to move workloads in/out of vSphere and vCloud environments and into other solutions that support the standard. Just beware of solutions that will happily accept OVF workloads but not so happily give them back (warning: the majority won’t).
The end result: cloud goodness, happy CIO’s, and streamlined IT. How’s that for a differentiator?