Research about Docker Support in Pivotal Cloud Foundry

Knowledge Sharing:
1.  Diego builds out the new runtime architecture for Cloud Foundry, replacing the DEAs and Health Manager.
2.  Diego also helps bring a cleaner container abstraction with Warden, the container technology developed originally for Cloud Foundry.
3.  Diego does not run Docker containers. It has an interface to run compatible images in Warden containers. For the end user, there is very little difference. You can push a Docker image into Warden. Diego is designed to run different backends.
4.  The droplet execution manager (DEA), health manager and some of the cloud controller are now taken care of by Diego, Whelan said
5.  Docker is important for the future of PaaS. Every new PaaS has a strong connection to Docker. To ignore Docker containers ina PaaS would be suicidal.
6.  Diego does that (admittedly with more specificity) and a lot more: containerization, log aggregation, routing, health-management, etc
7.  Each App Lifecycle provides a set of binaries that manage an application lifecycle that specific to Cloud Foundry.
8.  One of the selling points of Diego, is that you support various container backends, such as Windows or Docker.
Functionality is being added to enable end-users to push Docker images directly into a Cloud Foundry cluster running Diego.


References:
http://htmlpreview.github.io/?https://raw.githubusercontent.com/cloudfoundry-incubator/diego-design-notes/master/clickable-diego-overview/clickable-diego-overview.html
http://thenewstack.io/docker-on-diego-cloud-foundrys-new-elastic-runtime/
http://i1.wp.com/blog.cloudfoundry.com/wp-content/uploads/2013/02/fa2_fig021.jpg
http://blog.pivotal.io/pivotal-cloud-foundry/features/cloud-foundry-container-technology-a-garden-overview
http://www.activestate.com/blog/2014/09/cloud-foundry-diego-explained-onsi-fakhouri