Welcome!

Eclipse Authors: Adrian Bridgwater, John Cowan, Hovhannes Avoyan, CloudCommons 2011, Paul Miller

Related Topics: Web 2.0, Cloud Expo

Web 2.0: Article

VMware's vCloud API Still Hazy, Ambitions Are Clear

VMware's vCloud API

VMware continues to make noise around its forthcoming vCloud API initiative. According to an announcement last week VMware has developed a new API aimed at offering service providers with the ability to easily migrate between public and private VMware-based clouds. Like the previous announcement, details are sketchy other than to say "select group" of partners are using it. When asked to comment or share a copy of the vCloud API, the companies involved indicated they were covered by an NDA. Those companies include SAVVIS, SunGard, Telefonica, Telstra and Terremark.

According to my source, the vCloud API will be released "publicly very shortly". Funny that same source said that back in November as well.

Actually what I found most was the quote VMware's Dan Chu, vice president of emerging products and markets made in the Network World website. In the post he outlines "that one of the drivers for the API was the lack of standardisation for cloud computing interoperability." He goes on to say that the company was looking to build on its work with Distributed Management Task Force (DMTF) on the open virtualisation format (OVF). "The industry needs to take a big step towards interoperability. We hope to work with the appropriate bodies to move forward to establish a common standard."

As for being interoperable, VMware is saying that its various management tools will only work on top of the VMware hypervisor. In other words, physical servers and servers virtualised by Microsoft, Citrix or any other vendor will not be compatible with the vCloud initiative. Summarized, we're interoperable as long as it's VMware.

According to the Network World website, VMware has already submitted a draft of its VMware vCloud API to enable consistent mobility, provisioning, management, and service assurance of applications running in internal and external clouds." (What!? Did I miss something here?)

What concerns me about this is that Winston Bumpus is both President of the DMTF as well as Director of Standards Architecture at VMware. This would seem to mean that Bumpus has the ability to submit draft API specifications directly to the DMTF without any outside public review. He in effect has the ability to to define cloud standards directly, thus giving VMware a "somewhat" unfair advantage in terms of defining the future direction for standards-compliant cloud platforms, VMware based or otherwise. If the DMTF accepts the vCloud API specification, that would mean VMware essentially owns the cloud API standard. A standard that no one other then a select group of VMware's partners has ever actual had a chance to review.

I'll keep you updated as more details emerge.

More Stories By Reuven Cohen

Reuven Cohen is Founder & CTO for Toronto based Enomaly Inc. - leading developer of Cloud Computing products and solutions focused on enterprise businesses. Enomaly's products include the Enomaly elastic computing platform, an open source cloud platform that enables a scalable enterprise IT and local cloud infrastructure platform. Cohen is a thought leader in the emerging cloud computing industry and maintains a blog at www.elasticvapor.com.

Reuven is also founder of several technology organizations;
Enomaly.com - Elastic Computing Platform (Cloud Computing),
Cloud Camp - Local Cloud Computing events,
the Unified Cloud Interface Project - Semantic Cloud Abstraction API
Cloud Interoperability Forum - Cloud Standards Group.

(twitter @ruv : Linkedin : RSS Feed)