OpenStack Development: The Infrastructure Behind the Infrastructure
summary
OpenStack runs a bespoke CI stack that gates every change and handles spikes of contributions (up to 200 contribution activities an hour); it uses garrett, git review, Jenkins with Jenkins Job Builder, and speculative test orchestration via zuul to merge changes only after unit and 45-minute integration tests pass. Dev environments use devstack and cached VM images across multiple OpenStack clouds; logs (terabytes per cycle) feed Elasticsearch/Logstash for failure analysis. The system reduces merge breakage, runs ~1,000 test clouds daily, and recovers from flaky external services via caching and retries.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:38Components of OpenStack
- 3:21Horizontal efforts
- 5:15Release management
- 8:02Contributors
- 9:45Onboarding
- 10:54Developer Infrastructure
- 14:28Developer Environment
- 17:44Project Gating
- 18:48Automation
- 19:32Developer Workflow
- 23:30Garrett
- 25:01Garrett screenshots
- 26:22Garrett diff view
- 27:05Launchpad integration
- 28:34Garrett Review
- 30:42Testing
- 32:11Challenges
- 34:14Garrett Git Prep
- 35:13Dev Stack Gate
- 35:47Problems
- 37:44Nodes
- 39:08Zuul
- 40:06Simulation
- 43:20Gate Pipeline
- 43:51Jenkins Job Builder
- 45:32Jenkins Job Template
- 48:28Nova Job Template
- 50:10Git Repository
