Preface
Picture the scene. It’s 3 AM. An ops engineer or developer has just been paged. Her brain feels sluggish; simple tasks seem to take just that little bit longer and her body is telling her it’s still asleep. This state of tiredness is something that many of us in on-call rotations often deal with as part of our jobs, albeit not a particularly welcome one.
When debugging complex issues in this state, I find myself most grateful for the modern incarnations of configuration management (CM) systems that we as operations professionals are able to make use of today. Although configuration management has been around for a long time, it’s only in the last few years that CM systems like Chef, Puppet, CFEngine, Ansible, and SaltStack have come along to evolve these tools from loosely-coupled collections of shell scripts and wiki pages into the rich orchestration frameworks we have today.
When I get paged at 3 AM, I’m quickly able to introspect into any changes that might have been made to the server or system in question and kick-start the late-night troubleshooting process. Imagine if instead of being able to run one command to look at the running config on one of my servers, I instead had to trawl through an internal wiki to find the install document that detailed that specific configuration. This very process might in fact be what some of you are using right now, and to you I say: be strong, brave engineer! There is hope and its name is configuration management!
In this book, we focus ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access