Cloud Foundry Diego Overview
summary
Diego replaces DEAs as Cloud Foundry’s official container runtime and proves scale by running 250,000 application instances across ~1,200 cells using a SQL-backed BBS (MySQL/Postgres) and an Auctioneer that places work on Garden/Guardian cells. Operators get a CLI inspector, CF Diego Operator Toolkit ("cfdot"), that decodes protobuf BBS APIs to JSON for jq. Diego supports LRPs (auto-restart, scalable) and one-off tasks, adds local route emitters, a locket SQL lock service, and Windows container work in progress.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:50Diego Core Components
- 6:49Diego Workload Types
- 9:45Running LRP Instances
- 13:30Diego Cell Evolution
- 16:41Scale Improvements and Validation
- 19:09Stability: Component Coordination
- 23:14cfdot: Diego Operator Toolkit
- 25:28cfdot: Examples Example: Count of app instance states
- 26:52Ideas for Next Steps
related talks
32mCloud Foundry Diego Update
30mDiego Runtime Overview
35mResource Management Ecosystem and Cloud Foundry - A Review of the State of the Art
32mImplementing the Schedulers: A Look at the Internals of Diego...
31mScaling a Distributed Container Management System: Diego Performance
28mDiego vs Eirini: How to Choose the Best Fitting Container...
21mA Retrospective on a Decade of Contributing to Cloud Foundry
24mCloud Foundry and Containers (or: Where does Cloud Foundry Fit in the Container Ecosystem?)