On Tuesday VMware announced their answer to the public cloud: the vCloud Hybrid Service (vCHS). One of the biggest hurdles for the roughly 500,000 VMware customers has been that their on-premise, private infrastructure isn’t directly interoperable with any sizable public clouds, like Amazon AWS or RackSpace. If you want to move towards a public or hybrid cloud model you need to add additional software, like Enstratius’ offerings or VMware’s own vCloud Automation Center. You could also use the vCloud Connector, but that relies on having another vCloud available. One of VMware’s frustrations has been the adoption rate of partners, most refusing to build full vCloud implementations, effectively trapping VMware customers inside their own data centers.
Articles Tagged with vFabric
So now we know what Paul Maritz’s real job is going to be. VMware has announced on its Executive Team Blog that they will form a new organization, The Pivotal Initiative, which will collect EMC’s and VMware’s application focused people and assets into one group. This will include the people and the technology assets from EMC’s Greenplum and Pivotal Labs organizations, and the people and technology assets from the VMware vFabric (Spring and Gemfire), Cloud Foundry and Cetas organizations.
At VMworld VMware announced the release of the vCloud Suite of products. This new suite of packages, depending on the level purchased, bundles together several individual products into a single purchase point. See the table later for details of which package includes which product.
However, to me the most interesting point was the fact that this suite is purchased per processor, not per VM. This, coupled with VMware’s announcement of the death of vRAM, means that you can in theory now get a lot more bang per buck spent with no artificial limits set on usage.
For quite a number of years, VMware has made it very clear that it views virtualization not only as a technology that provides significant benefits to data centers, but also a technology that disrupts the existing virtualization management solutions, and opens an opportunity for new management solutions to be offered and adopted by enterprises. VMware has also made it clear that it intends to capitalize upon this opportunity by fielding a family of strong products in the Virtualization Management area.
People often equate VMware with vSphere (certainly VMware’s flagship product). But VMware is not a one product or even a one product line company. VMware is in fact five different businesses, each of which make different current contributions, have different long term strategic value, and have different synergies with the others. These five businesses are like an engine, three boxcars and a caboose.
As mentioned in my previous piece I’ve been doing some prototyping using SpringSource’s Grails. Grails can be thought of as the top of the stack. If you pick up Grails you would naturally pull in the other pieces of SpringSource, including vFabric and ultimately CloudFoundry. In a future post I will deal with what happens when you stick Grails onto CloudFoundry, but at this stage I’ve been assessing the health of the SpringSource Ecosystem.