VMware’s cloud initiative depends upon customers and vendors using vSphere. Will it prevent true cloud interoperability?
VMware talks a good game about interoperability, but its cloud initiative threatens to introduce a type of vendor lock-in that rival virtualization vendors claim they would not impose.
While competitors Citrix and Microsoft have embraced the notion of supporting multiple virtualization platforms with their software, VMware has long maintained that its management tools will support only its own hypervisor. Now its growing cloud initiative, highlighted at this week’s VMworld conference, depends upon customers and vendors using its vSphere virtualization platform, which could prevent true cloud interoperability.
When VMware unveiled its cloud initiative for service providers last year, 100 vendors had signed up. Today more than 1,000 service providers worldwide are on board, providing cloud-based computing services based upon vSphere. AT&T, Savvis, Terremark and Verizon Business are just a few examples.
VMware’s service provider program highlights one of the key goals of the cloud computing movement: that IT shops should be able to host workloads either in their own data centers or externally with a cloud provider, and have the ability to quickly move those workloads from one location to another and manage them all from the same pane of glass.
VMware is promising this capability -- but only in cases in which both the customer and the service provider are using vSphere.
Competitors claim this limitation is unacceptable, and say that virtual machines should have the benefits of mobility no matter what hypervisor the customer or cloud vendor uses.
VMware officials contend they are trying to promote open standards by submitting their own vCloud API to the Distributed Management Task Force (DMTF), in an effort to promote interoperability among public cloud platforms. VMware CTO Stephen Herrod said VMware submitted the API to DMTF because the company wants a “broad ecosystem of compatible clouds,” even including those not running VMware software. But vCloud is still a VMware-centric API, at least until other hypervisor vendors start using it, says Burton Group analyst Chris Wolf.
“In terms of VMware, sure they talk about choice,” Wolf says. “But the choice is really of service provider platforms, not of the virtual infrastructure. So you are locking yourself into a proprietary virtual infrastructure.”
The vCloud API can only become “an open standard when there are multiple vendor implementations,” Wolf continues. “Otherwise the vCloud API is marketing.”
VMware officials say customers won’t be locked into VMware-based clouds, with CEO Paul Maritz stressing the importance of avoiding a “Hotel California” scenario where “you can check applications into the cloud, but you can’t check them out.”
Wolf says customers may still have trouble moving applications out of VMware-based clouds, although the same could be said of many cloud services.
“It’s easy on the surface to say ‘you can move the VM to somewhere else,’” Wolf says. “Sure, but what about all of the storage? I might have terabytes of storage that are attached to a single cloud provider and that could be extremely problematic.”
Determining how to get data out of one provider’s cloud and onto another service provider platform has to be part of the service level agreement, Wolf says. “Otherwise that could be an enormous element of lock-in and makes it that much more difficult when you think about changing providers.”
True interoperability among cloud platforms is perhaps several years away, says Gartner analyst Cameron Haight. There are several technical concerns, such as figuring out how “one cloud provider [can] consume the metadata associated with a virtual machine coming from another vendor,” and thus understand its service requirements, he says.
VMware opening up the vCloud API makes it conceivable that a third party could superimpose the API onto a competing virtualization framework, although this might be difficult to achieve in practice, Haight says.
“We have a long way to go in the industry [with respect to cloud interoperability],” Haight writes in an e-mail. “Some current large cloud providers (Amazon, etc.) are not that involved in standards efforts. I tell Gartner clients that we are [expecting] at least a multi-year scenario for not only agreements on semantics and APIs to occur, but also for actual implementation to be realized.”
Citrix CTO Simon Crosby says customers should be able to bridge the gap between internal and external clouds without worrying what type of hypervisor is being used. Enterprise customers shouldn’t have “to ask the cloud vendor whose virtual infrastructure product was used to build the cloud,” Crosby says.
Citrix and Xen.org, the maker of the open source Xen hypervisor, are pushing the “Xen Cloud Platform,” an initiative designed to allow flexibility in which hypervisors are used to build virtual machines running on cloud services.
While VMware has a large number of cloud vendors on board, Xen.org can claim some momentum of its own with prominent cloud platforms such as Amazon and Rackspace using Xen. But Xen.org says it won’t matter what hypervisor is in use, saying its goal is to achieve broad interoperability across virtualization platforms with standards such as the Open Virtualization Format, allowing “virtual appliances … packaged in a hypervisor-independent format for easy transport between internal and external clouds with no vendor lock-in.”
VMware CEO Paul Maritz has no plans to let VMware software manage hypervisors created by rival vendors, he said during a Q&A session with media. Maritz was speaking about vSphere software, rather than VMware’s cloud partner program, but he noted that there is a tradeoff between supporting existing VMware customers and encouraging a more heterogeneous IT environment, he said.
Supporting rival virtualization products is “something we think about,” he said. But “at this point in time we think our challenge is to help our existing customers, all 150,000 of them, do more with their environments and lift their management up.”
VMware isn’t opposed to changing course if the market demands it, however.
“If [supporting multiple hypervisors] became a significant customer demand, we’d look at it,” Maritz said.
The different approaches taken by Citrix and VMware may come down to simple market realities. VMware is the dominant vendor in the x86 virtualization market, claiming 970 of the Fortune 1000 companies as customers. If service providers find it easier to support just one virtualization platform, they are likely to choose the most widely implemented technology – VMware’s. Citrix is a much smaller player and must support multiple hypervisors, including its own, Microsoft’s, and VMware’s, to create a successful cloud initiative.
“There’s a business need for them to support multiple hypervisors that VMware doesn’t have,” Wolf says.