Cloud Foundry Announces New Version, Deprecates Old
In an email to users on June 6th, Cloud Foundry announced the demise of its current service and planned launch of Cloud Foundry V2. The new service will become a paid service along with a new architecture and new features including a web console, team development and buildpacks for customizing languages and runtime environments. There will also be support for custom domains and a services marketplace.
Cloud Foundry V2 will become available on June 10th as a paid service. At the time of writing, pricing for the new service had not yet been announced. The old V1 service, which Cloud Foundry refers to as the "free beta phase" will be discontinued on June 30th. Existing users must migrate their applications to the V2 service. The migration isn't automatic and applications that are not migrated by the deadline will be deleted, however there are new features that Cloud Foundry says will justify the effort of migration.
Buildpacks are a major new feature and architectural change that drives the requirement for migration between V1 and V2. Buildpacks were originally developed by Heroku to modularize and allow customization of the supported languages and application stacks. The Cloud Foundry buildpacks are modelled off the Heroku implementation and Cloud Foundry says they are interested in working with Heroku to standardize the concept and enable portability between platforms. Cloud Foundry will provide standard buildpacks for Ruby, Node and Java applications. There are a large number of third-party Heroku buildpacks available which should run in Cloud Foundry V2 with little or no modification.
A third-party services marketplace is another new feature in the V2 Cloud Foundry although not many details have been announced prior to the V2 launch. James Watters, Head of Product, Marketing & Ecosystem at Cloud Foundry revealed in the developers forum that they are currently onboarding partners for the launch. The new add-on API will not be compatible with the Heroku add-on API as Cloud Foundry plans to provide improved capability for usage-based billing and multi-instance service provisioning. James also revealed that Cloud Foundry is partnering with AppDirect to build their add-on API and ecosystem. AppDirect is an established cloud service marketplace which supports service marketplaces for companies such as Rackspace, Verizon and Comcast. the AppDirect developer community already has documentation on how to build services for Cloud Foundry.
Cloud Foundry was originally developed as an open-source Platform-as-a-Service by VMWare. It along with other VMWare products was recently spun out into a new company Pivotal which is a joint venture between VMWare, EMC and GE. The Cloud Foundry software remains open-source.
Are you a CloudFoundry user? Tell us what you think of the new changes.