Devops or: How I Learned to Stop Worrying and Love the Ops Team
summary
Argues developers must deliver concrete ops-ready artifacts: everything in shared version control, integration and infrastructure tests plus end-to-end suites, visible CI like Jenkins, and a staging environment that mirrors production (devs have root there). Recommends config management (Puppet, Chef, CFEngine), packaging via apt/yum, service discovery with DNS SRV records, ops-held secrets, feature switches (Gargoyle), structured logging/session IDs, exception tracking (Sentry/New Relic), SNMP/Ganglia metrics, and scripts/console shells so incidents get fixed, not paged repeatedly.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:22DEVELOPERS
- 1:58OPERATIONS
- 2:41DEVOPS
- 4:33SHARED VERSION CONTROL
- 5:30TESTING
- 7:05CONTINUOUS INTEGRATION
- 7:53INTEGRATION ENVIRONMENTS
- 10:15CONFIGURATION
- 12:57DEPLOYMENT TECHNIQUES
- 14:01SCALING
- 18:57LOGGING
- 20:02DON'T BE PRETTYLOG
- 21:08EXCEPTION TRACKING
- 22:54STATISTICS
- 23:47NAGIOS
- 26:18SNMP
- 27:17MANAGING ERRORS
- 28:46TOOLS OF THE TRADE
- 30:12CONSOLE
- 31:08SCRIPT EVERYTHING
- 31:39MANAGEMENT INTERFACES
related talks
25mDevOps for Pointy-Haired Bosses
44mDevOps for developers (or maybe against them?!)
33mOperations: a developer's guide
58mDevOps Counseling: 10 ways to help your Dev and Ops people love each other
53mGround Truths of a Rugged DevOps Practitioner
16mDevOps - Philosophy vs Practice
51mElemental devops
31mDevOps for Java Developers (Or Maybe Against Them?!)