Open Access Articles- Top Results for Cloud Foundry

Cloud Foundry

Cloud Foundry
Developer(s) VMware
Pivotal Software
Initial release 2011
Written in Ruby, Go
Type Cloud computing
License Apache License 2.0

Cloud Foundry is an open source cloud computing platform as a service (PaaS) originally developed by VMware and now owned by Pivotal Software - a joint venture by EMC, VMware and General Electric. Cloud Foundry was designed and developed by a small team from Google led by Derek Collison and was originally called project B29.[1][2][3] It is an Infrastructure as a Service (IaaS), comparable to Google Storage and Amazon S3 online storage services.

Cloud Foundry was also a Java PaaS for Amazon EC2 founded by Chris Richardson in 2008 and acquired by SpringSource in 2009 [4] (the same month VMware acquired SpringSource). The current product is unrelated to the project under SpringSource, but the name was adopted when the original SpringSource project was end-of-life'd. Cloud Foundry is primarily written in Ruby and Go.


Cloud Foundry comes in three flavors.

Other companies also offer platform as a service products using the Cloud Foundry platform.


Cloud Foundry supports the full lifecycle, from initial development, through all testing stages, to deployment. It is therefore well-suited to the continuous delivery strategy. Users have access to one or more spaces, which typically correspond to a lifecycle stages. For example, an application ready for QA testing might be pushed (deployed) to its project's QA space. Different users can be restricted to different spaces with different access permissions in each.

Developers require an additional tool, the Cloud Foundry cf Command Line Interface. It is written in Go. Installers exist for MS Windows, MacOS, and Linux.

The cf utility provides many options, but for deployment cf push is all that is required. It accepts arguments to specify the name of the application, where to load it from and the URL that should be used to access it. For example:

   cf push spring-music -i 2 -m 512M -n spring-music-v1 -p build/libs/spring-music.war

pushes the Java web application spring-music. Two instances are deployed (this is a Java web-application so by default this is two Tomcat instances), each with 512M of memory. The URL ends with spring-music-v1 and the web-archive (application) can be found at build/libs/spring-music.war. Every Cloud Foundry instance manages one or more domains. For example all Pivotal Web Services (PWS) applications are accessed via the domain, so if this Spring Music application had been deployed to PWS, its URL would have been

When an application is deployed to Cloud Foundry, an image is created for it and stored internally. The image is then deployed to a Warden container to run in. For multiple instances, multiple images are started on multiple containers. This is where BOSH comes in - Cloud Foundry's internal Controller uses BOSH to get the underlying infrastructure to spin up virtual machines to run the Warden containers on. When an application is terminated, all its VMs can be recycled for another application to use. If the application instance crashes, its container is killed and a new Warden container is started automatically. A container only ever runs one application ensuring isolation, security and resilience.

A load-balancing router sits at the front of Cloud Foundry to route incoming requests to the correct application - essentially to one of the containers where the application is running.


Applications deployed to Cloud Foundry access external resources via Services. In a PaaS environment, all external dependencies such as databases, messaging systems, files systems and so on are Services. When an application is pushed to Cloud Foundry, you can specify the services it should use also. Depending on the application language, auto-configuration of services is possible - for example a Java application requiring a MySQL database picks up the MySQL service on Cloud Foundry if it is the only one defined in the current space.

Services have to be deployed to the platform first and then are available to any application using it. Another advantage of Pivotal CF is that many pre-defined services can be deployed into it directly using the Administration Console. Users of the Open Source Cloud Foundry must make services available by writing and running BOSH scripts.

PWS provides a large number of services thanks to a partnership arrangement with App Direct.

The following services are available to Pivotal CF and on PWS:


Although Cloud Foundry is a Pivotal Product, its direction is controlled by a Foundation (similar to how Rackspace, NASA and others started the OpenStack Foundation).[10] By mid-2014, 33 companies had signed up to the Cloud Foundry Foundation.[11]

The source code is under an Apache 2.0 license, and contributions are governed by the Cloud Foundry contributors' licenses for individuals and corporations. These licenses grant both copyright and patent access and protection to the Cloud Foundry Foundation, which is the same model that VMware followed with the Spring Framework from SpringSource.

Supported runtimes and frameworks include:[12][13]

Language Runtime Framework
Java Java 6, Java 7, Java 8 Spring Framework 3.x, 4.x
Ruby Ruby 1.8, Ruby 1.9, Ruby 2.0 Rails, Sinatra
Node.js V8 JavaScript Engine (from Google Chrome) Node.js
Scala Scala 2.x Play 2.x, Lift
Python Python

Typically, Cloud Foundry is installed on-premise running over VMware's vSphere virtualization infrastructure, although deployment to OpenStack is an option using BOSH.[14]

It is also possible to run Cloud Foundry instances on VMware Fusion or Virtualbox using Vagrant and on AWS.[15]

See also



External links

Official website

Lua error in package.lua at line 80: module 'Module:Buffer' not found.