A Retrospective on a Decade of Contributing to Cloud Foundry
Talkat Cloud Foundry Day North America 2024 · on Wednesday, 2024-05-15· at 09:40· Education Center, 2nd Floor·
summary
Timeline of decisions that made Cloud Foundry reliable: Diego replaces fragile DEAs, swaps etcd for plain MySQL and scales 250,000 containers after a two‑year rewrite; Cloud Controller V3 rethinks objects and replaces metaprogrammed V2, enabling processes, packages and droplets but leaving many users on V2; a perm microservice for custom roles fails against V2 complexity so CF management and cron jobs fill the gap; logs standardize to RFC3339 timestamps but an octet‑framed syslog change once breaks downstream parsers.
AI-written summary · about
chapters (9)
- 0:00Introduction and overview
- 1:26Health manager challenges and race conditions
- 3:33Diego rewrite and data store decisions
- 5:20Cloud Controller V3 API development
- 8:30Permissions service and API compatibility
- 11:38Hyrum's Law and API dependencies
- 13:03Standardizing timestamp formats
- 15:30CIS log drain protocol breakage
- 20:24Conclusion and future of Cloud Foundry
related talks
17mKeynote: State of the Project
31mA Developer’s Perspective on Cloud Foundry Operations: One Month in the Trenches
37mCloud Foundry Diego Overview
30mWhat's New in the Cloud Foundry Ecosystem?
15mThe Cloud Foundry Renaissance
35mResource Management Ecosystem and Cloud Foundry - A Review of the State of the Art
23mFive Years of Cloud Foundry at Rakuten
30mPanel Discussion: Welcoming V3: Modernizing the Cloud Foundry API