How Cloud Controller Makes the Foundry Go ‘Round
summary
Cloud Controller runs the Platform as a Service control plane, holds the Cloud Controller database as source of truth, and actually coordinates push → package → droplet → run flow across DEA or Diego back ends. The team refactors CC to expose a new v3 API that breaks the tight coupling of packages/droplets so a single push can spawn multiple process types and one-off tasks. Work includes moving the CC bridge functionality and offloading heavy upload/matching to a bitservice.
AI-written summary · about
chapters (7)
- 0:00Introduction to Cloud Controller
- 1:45Cloud Controller components
- 3:30App push workflow deep dive
- 10:12Backend support DEA vs Diego
- 14:24Apps and services integration
- 18:01V3 API and new features
- 22:33Q&A and community resources
related talks
25mNext steps in the Cloud Foundry API and why...
35mResource Management Ecosystem and Cloud Foundry - A Review of the State of the Art
02mCloud Foundry
48mCloud Foundry - your PaaS on OpenStack
01h 03mDeep Dive into Pivotal Cloud Foundry 2.0
03mCloud Foundry
01mIntroduction: Cloud Foundry
43mHow Platforms Work