Code Review for Operations
summary
OpenStack infrastructure uses 600 repositories and runs roughly 100,000 reviews over ~20,000 commits in six months, so expect scale problems: small patches land fast, big patches stall, and urgent ops sometimes get self‑approved. The stack uses Gerrit/Git, Jenkins and Jenkins Job Builder, Puppet/Ansible/Terraform, disk image builder and custom dashboards. Experiment shows ad hoc operational work can be codified: a beta tool called finger longer checks shell tasks into git and robots execute them after review.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:52Code Review for Operations
- 3:00Vocabulary
- 3:37Definition of Code Review
- 4:12What is a Code Review
- 4:31Why do people do Code Review
- 6:05Code Review Process
- 6:20Tools and Techniques
- 7:05Two Pass System
- 8:24Infrastructure
- 8:42Tooling
- 9:11How does code review change developers
- 9:47What does code review do
- 11:06Test definition
- 13:26Code review
- 15:47The game
- 17:05How does code review change
- 18:06First and Second Person Yellow
- 18:55Chickens Pigs
- 19:52Work in Progress
- 20:03Silence
- 20:43Hostages
- 21:37Server Lifecycle Management
- 22:10FingLonger
- 26:56Questions
related talks
54mOpenStack Development: The Infrastructure Behind the Infrastructure
31mDevOps 2.0 - Bigger, Badder with More Automation
53mGround Truths of a Rugged DevOps Practitioner
35mGitOps - Operations by Pull Request
35mPanel: GitOps User Stories
29mTales from the Branches: GitOps in the Real World
13mDevOps automation with Go
35mGitOps - the holy grail of devops