Cloud Foundry is an open source, multi cloud application platform as a service (PaaS) governed by the Cloud Foundry Foundation, a 501(c)(6) organization.
The software was originally developed by VMware and then transferred to Pivotal Software, a joint venture by EMC, VMware and General Electric.
Maps, Directions, and Place Reviews
History
Originally conceived in 2009, Cloud Foundry was designed and developed by a small team at VMware led by Derek Collison and was originally called Project B29. At the time, a different PaaS project written in Java for Amazon EC2 used the name Cloud Foundry. It was founded by Chris Richardson in 2008 and acquired by SpringSource in 2009, the same year VMWare acquired SpringSource. The current project is unrelated to the project under SpringSource, but the name was adopted when the original SpringSource project ended.
The announcement of Cloud Foundry took place in April 2011. A year later, in April 2012, BOSH, an open source tool chain for release engineering, deployment & life-cycle management of large scale distributed services, was publicly launched. In April 2013, Pivotal was created from EMC and VMware, to market assets including Cloud Foundry, Rabbit and Spring.
By February 2014, it was announced that there would be an open governance foundation established with seven Platinum members and two Gold members. In May 2014, there was an announcement of expanded membership with the addition of eight new companies. By December 2014, the membership had increased to 40.
Cloud Foundry Getting Started Video
Cloud Foundry Foundation
In January 2015, the Cloud Foundry Foundation was created as an independent not-for-profit 501(c)(6) Linux Foundation Collaborative Project.
Following the creation of the Cloud Foundry Foundation, the Cloud Foundry software (source code and all associated trademarks) was transferred to be held by the open source software foundation. It is primarily written in Ruby, Go and Java.
As of March 2017, the foundation had 70 members.
The foundation serves as a neutral party holding all Cloud Foundry intellectual property. Once intellectual property is contributed to Cloud Foundry, it becomes property of the Foundation and these assets cannot be transferred to for-profit entities, as per the laws governing 501(c)(6) organizations. The Foundation holds two contributed types of intellectual property: trademarks and a copyright on the collective work of the community. It also has a license to use and re-license all code contributions, but does not own copyright on those contributions.
Usage
Cloud Foundry is promoted for continuous delivery as it supports the full application development lifecycle, from initial development through all testing stages to deployment. Cloud Foundry's container-based architecture runs apps in any programming language over a variety of cloud service providers. This multi-cloud environment allows developers to leverage the cloud platform that suits specific app workloads and move those workloads as necessary within minutes with no changes to the app.
Users have access to one or more spaces, which typically correspond to a lifecycle stage. 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 often 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 starts 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 cfapps.io domain, so if this Spring Music application had been deployed to PWS, its URL would have been spring-music-v1.cfapps.io.
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 deleted, all of its containers are destroyed and their resources are freed for other applications 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.
Services
Applications deployed to Cloud Foundry access external resources via a Open Service Broker API, which was launched in December 2016.
In a platform, all external dependencies such as databases, messaging systems, files systems and so on are considered Services. Cloud Foundry allows administrators to create a marketplace of services, from which users can provision reserved resources on-demand. When an application is pushed to Cloud Foundry the services it needs may also be specified. This process puts the credentials in an environment variable.
Software
The development of Cloud Foundry is controlled by the Cloud Foundry Foundation.
The source code is under an Apache License 2.0. and contributions are governed by the Cloud Foundry contributors' licenses for individuals and corporations.
Born on a container-based architecture, Cloud Foundry is able to support innovation in containers through collaboration with other projects and standards such as OCI and CNI.
Supported runtimes and frameworks include:
Typically, Cloud Foundry is installed on-premises running over VMware's vSphere virtualization infrastructure, although deployment to OpenStack is an option using BOSH.
It is also possible to install Cloud Foundry using a BOSH-Lite Vagrant VM onto VirtualBox or AWS.
Platform
The Cloud Foundry platform is available from either the Cloud Foundry Foundation as open source software or from multiple commercial providers as either a product or a service. Cloud Foundry is open source software and hence available to anyone. Deploying Cloud Foundry involves interfacing with the underlying infrastructure using the Cloud Foundry BOSH deployment system, another open source tool governed by the Cloud Foundry Foundation.
A commercial version called Pivotal Cloud Foundry (PCF) is available from Pivotal. It provides extra tools for installation and administration not included in the open software product. Pivotal Web Services (PWS), however, is an instance of Pivotal Cloud Foundry hosted on Amazon Web Services (AWS).
In December 2015, the Cloud Foundry Foundation announced the "Cloud Foundry PaaS Certification program" which delineated criteria to be considered a Cloud Foundry Certified Provider. As of June 2016, the list of certified providers includes:
- Atos Canopy
- CenturyLink App Fog
- GE Predix
- HPE Helion Stackato 4.0
- Huawei FusionStage
- IBM Bluemix
- Pivotal Cloud Foundry
- SAP Cloud Platform
- Swisscom Application Cloud
Source of the article : Wikipedia
EmoticonEmoticon