Exiting Vacuum: Integrating Configuration Management into your Ecosystem
summary
Argues that configuration management must sit in an ecosystem: use Vagrant + Chef for local reproducible builds, push binaries into package repos (Artifactory/Nexus) and keep CM code in version control, wire CI (Jenkins) to bootstrap test instances and run integration tests with minitest/bats. Prefers primitives (package, template, service) over shelling out, shows a working Vagrant+Chef Tomcat demo, warns about legacy teams and suggests starting small (OS provisioning or one unstable tier) and iterating with refactoring.
AI-written summary · about
chapters (6)
- 0:00Start
- 8:05Configuration Management is NOT
- 12:41In a perfect universe
- 28:02Keep an Open Mind
- 29:23Refactoring Happens
- 30:18Brownfielding
related talks
13mConfig Management for Programmers: How to Set Up Virtual Machines the Easy Way
53mChange your tools, change your outcome
01h 19mThe Business of Configuration Management
33mDeveloping for Multi-Component Environments While Keeping Your Sanity
28mFrom Monitoring to Automated Testing of Your Infrastructure Code
33mOperations: a developer's guide
25mVagrant: The Stick and Carrot of a DevOps Leader
42mCI Techniques for Delivering the Chef-Repo: Three Case Studies