Research about installing Pivotal Cloud Foundry

Knowledge Sharing:
1. PCF Installation Virtual Appliance is known as Ops Manager
2. Binding a service instance to your application triggers credentials to be provisioned for the service instance and delivered to the application runtime in the VCAP_SERVICES environment variable.
3. Managed Services are defined as having been integrated with Cloud Foundry via APIs and enable end users to provision reserved resources and credentials on demand.
4. For local development we recommend using Bosh Lite to deploy your own local instance of Cloud Foundry.
5. A stemcell is a VM template with an embedded BOSH Agent.
6. “Cloud Foundry v2” they are referring to the version of the cloud controller API. The services API is versioned independently of the cloud controller API.
7. How a service is implemented is up to the service provider/developer. Cloud Foundry only requires that the service provider implement the service broker API. A broker can be implemented as a separate application, or by adding the required http endpoints to an existing service.
8. Pivotal Web Services was born as a place agile teams could rapidly update and scale applications across multiple environments and let Cloud Foundry maintain their applications’ health in production.
9.  PWS is Pivotal’s public Platform-as-a-Service offering. PaaS systems let you host apps by pushing them to a service rather than having to configure and maintain separate installations of web servers, load balancers and so on. PWS is a hosted installation of the open-source Cloud Foundry project, to which Pivotal is a primary contributor.
10. bosh-lite uses Vagrant and a Warden BOSH CPI to deploy Cloud Foundry in a VM. A single VM is created using Vagrant, then each Cloud Foundry component is deployed in its own Warden container using BOSH. bosh-lite supports VMware Fusion, Virtualbox, and AWS
11. In the previous release of Cloud Foundry, Micro Cloud Foundry was a useful tool for Cloud Foundry developers or anyone with a need to run a local instance of Cloud Foundry. Micro Cloud Foundry has not been upgraded for Cloud Foundry v2.


References:
http://docs.pivotal.io/pivotalcf/getstarted/#system
https://upload.wikimedia.org/wikipedia/commons/9/96/VMware_vSphere_in_the_Enterprise_diagram_v1.0.gif
http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-78933728-7F02-43AF-ABD8-0BDCE10418A6.html
http://stackshare.io/stackups/heroku-vs-pivotal-web-services
http://yourstory.com/2012/07/tutorial-getting-started-with-cloud-foundry-part-13/

Local Instance of Cloud Foundry:
https://github.com/cloudfoundry/bosh-lite
https://github.com/cloudfoundry/warden
http://yourstory.com/2012/07/tutorial-getting-started-with-cloud-foundry-part-13/


Docker vs Warden:
http://jamie-wang.iteye.com/blog/2175918
https://gist.github.com/syslxg/5a2ef3cb54f77d6c6572

Challenges:
1. Service Instances
2. Bind Service Instances
3.

Buildpacks:
https://spring.io/blog/2015/04/27/binding-to-data-services-with-spring-boot-in-cloud-foundry
http://blog.altoros.com/creating-a-custom-cloud-foundry-buildpack-from-scratch-whats-under-the-hood.html