About two weeks ago, CRN published an article about VMware Zephyr project. According to the article, VMware plans to launch a public IaaS cloud to compete with Amazon EC2, Microsoft Azure, and more directly with existing VMware vCloud service providers. The reason for the move is “because none of its service provider partners are moving fast enough. Look at the adoption rate of vCloud Director with service providers — it is non-existent.”
VMware released the long-awaited vCloud API at VMworld 2010. The API is based on REST with 75 URLs defined in the user related part as you would find in the vCloud API Specification and vCloud API Programming Guide.
I am an OO guy (I am sure many of you are as well), and find it difficult to go through the 75 URLs and numerous XML tags as either input or return. These URLs are like trees in a forest. But where is the forest?
So I decided to create and show you a UML diagram (shown below) so that you can easily capture the key concepts of the vCloud API. In fact, there was a similar diagram in the programming guide of version 0.8.
Since the term “vCloud” was made public at VMworld 2008 in Las Vegas, VMware has been working hard to define and implement its vCloud vision and strategies.
In 2009, VMware announced vCloudExpress with service provider partners such as Terremark. VMware also submitted its vCloud API spec to DMTF so that the industry could benefit from the standardized management of APIs. VMware also acquired SpringSource in 2009. The acquisition attracted a lot of attention, scrutiny and questions.
Earlier this year VMware acquired Zimbra, the leading provider of SaaS collaboration software, and subsequently it also bought RabbitMQ. Both are now part of the VMware SpringSource portfolio. Last week, VMware and Saleforce.com announced vmforce.com which is a joint venture targeting enterprise PaaS cloud. Yesterday VMware announced acquisition of GemStone (pending).
With these acquisitions and announcements, the company’s strategy is clearer than ever. Looking back again, VMware has been building a cloud product and service portfolio under the vCloud umbrella. Some previously misunderstood acquisitions become well aligned in the vision and strategies of vCloud.
vCloud is not the only player in the industry but VMware is well on its way. Given its deep roots in enterprise data center virtualization, no one can ignore the potential of VMware in cloud computing.
To help enterprises better understand vCloud, I offer ten things you should know:
Some of you may have noticed that VMware released vCloud API Spec version 0.9 last week. The 9 page document describes all the functions and corresponding REST syntax of version 0.9. Better than I had expected, it highlighted changes from version 0.8. So if you have read previous version, you can just scan for the changes with keywords: CHANGED, NEW, REMOVED.
The vCloud API includes the following categories of functions.
newScale recently announced it would support VMware vCloud API in a press release.
San Mateo, Calif. – February 17, 2010 – newScale®, Inc., pioneers of the self-service IT storefront for the enterprise, today announced it will support the VMware vCloud API, a key component of the VMware vCloud initiative. Enterprises and service providers integrating with the VMware vCloud API can now use the newScale FrontOfficeTM Suite to effectively manage and control self-service requests for cloud resources as well as their physical and virtual environments.
This announcement underscores newScale’s continuing commitment to supporting multi-vendor, cross-platform data center and cloud infrastructures. The newScale FrontOffice Suite – a complete set of Service Catalog solutions for managing IT services from cradle to grave – integrates with VMware vSphereTM 4 and VMware vCenterTM Server. newScale is also a member of the VMware Technology Alliance Partner (TAP) program. By leveraging the VMware vCloud API, newScale demonstrates its ongoing support for a wide range of virtualization and cloud infrastructures, giving newScale customers maximum flexibility, efficiency, and agility in their data center deployments.