In a previous entry I mentioned that one of the first VMware/Springsource connect points would be in the number of applications VMware would be able to lay claim to being vSphere ready since. We've seen SpringSource already discuss integration with vApp, today we learn about Cloud Foundry.
SpringSource Cloud Foundry provides an easy-to-use self-service approach, enabling developers to deploy their applications in minutes using a simple web interface. It offers automation of common deployment blueprints and intelligent, SLA-driven resource allocation with automatic scaling and automatic infrastructure repair.
Cloud Foundry builds on familiar Java technologies that SpringSource leads or makes a significant contribution to. The core runtime is our tc Server product, built on and wholly compatible with Apache Tomcat. We use the Apache HTTP web server for load balancing, and integrate Hyperic technologies for monitoring and management. We also provide a relational database (MySQL). Cloud Foundry allows the user to specify the desired application server and database configuration through a web interface, concealing the complexity of achieving the desired result, ensuring that the required steps reflect the intent rather than the details, and that configuration and deployment is repeatable. We expect that most users will be deploying Spring or Grails applications, although Cloud Foundry is not limited to Spring and Grails applications.
Thus, the programming and deployment model is wholly built on open source. The Cloud Foundry service also builds on open source: the Cloud Tools project, founded and led by Chris Richardson, which provides a set of tools for deploying, managing and testing enterprise Java applications in a cloud environment.
This initial release runs on Amazon EC2 cloud infrastructure. However, one of the key elements of Cloud Foundry is the abstraction it provides over such infrastructure. As with the Spring Framework, we will work to enhance developer choice. In the future, Cloud Foundry will give developers a consistent experience over both public (off-premise) and private (on-premise) clouds, empowering organizations to make the most appropriate choices. Our conversations with customers make it clear that such a unified approach is a key need that is presently unmet in the industry. A key part of addressing this need will be Cloud Foundry also running on VMware vSphere infrastructure, which provides uniquely advanced on-premise cloud infrastructure.
And this is how VMware plan to put some clear blue water between themselves and those who think there's a business in just selling and/or supporting commodity hypervisors. Today Cloud Foundry supports Amazon EC2, in the future it will support vSphere and other technologies. The private cloud discussion now takes an interesting twist for VMware as Google App Engine and Microsoft Azure are potential public cloud deployment targets for Cloud Foundry.
But vSphere may be the only internal cloud platform supported. (Speculation on my part. I don't have any insight on that matter.)
Interesting things going on. The game is starting to heat up and it's looking like whoever has the largest application count stands the best chance of winning.
