Programming your Infrastructure
summary
Argues that infrastructure must be written and maintained like an application: cookbooks do one thing (an elasticSearch cookbook installs elasticSearch only), commented code gets deleted rather than left as zombies, linters and tests catch regressions, and automation actually runs in CI. Shows practical practices: small reusable cookbooks, unit/integration/acceptance testing, and using Chef and Molecule to lint and verify that the infrastructure code actually works.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:28Scenario
- 0:43Build new infrastructure
- 1:13Good Code
- 1:28Keep in Mind
- 1:43Sandy Mats
- 1:58Reusable Code
- 2:13Elastic Search
- 2:28Commenting
- 2:43Code zombies
- 2:58Delete key
- 3:13Writing maintainable code
- 3:43Methods of testing
- 3:58Code Coverage
- 4:13Tools
- 4:28Testing
related talks
06mIgnite: Programming your infrastructure
46mImplementing Infrastructure as Code
28mFrom Monitoring to Automated Testing of Your Infrastructure Code
46mThink of your infrastructure as code
42mInfrastructure as Code - Lessons learned from Dev to Ops
54mInfrastructure as code (anti) Patterns
01h 21mTest Driving your Rails Infrastructure with Chef
01h 02mTools and Techniques for Infrastructure as Code