Do you Know a Runbook From a Flip Book?...
summary
Survey of what ops teams actually keep and use: runbooks with step‑by‑step failover and malware‑cleanup procedures, cookbooks and tutorials for config and integration, manifests and dependency lists from the monitoring and CM systems, and repository scripts for vendor customizations. A pilot cat‑database is built and deployed; a botnet uploads bogus records, the runbook directs switching nodes and firewall rules, a repo script cleans the DB, vendor provides hotfix — documentation and artifacts prove decisive for rapid incident response.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:43Old school ops is not dead It's not even resting
- 5:30Planning vs Responding Making a thing happen
- 5:59#%!& Implementation How does it work??? What does it do? Will it help me? How do I make it do what I want?
- 9:29Does this software address my problem?
- 10:49Informal documentation: making sure details aren't lost Ticket systems are nifty Wikis are awesome
- 12:06The runbook: helping frazzled humans remember stuff on the first try
- 15:26Growing project needs food! Um, to adhere to internal process Configuration management Naming conventions Deployment window schedules
- 17:32Capturing history for parts that appear out of nowhere
- 19:57MONTHS LATER...
- 25:48Runbooks and checklists don't leave room for much thinking Because you won't have it either
related talks
42mLessons Learned from Cloud Ops
51mOctopus Runbooks, putting the Ops in DevOps
22mBe prepared for production incidents
15mIncident Ready: Chaos Engineer Your Incident Response
43mLearning from Firefighters to Improve Systems Reliability
33mOperations: a developer's guide
31mThe RunWhen Authors Community: Royalties For Runbooks
25mNetwork Automation Tools & Technology