DEVOPS / A CONCEPT NOTE
Configuration Management
automating server setup and software configuration at scale
Overview · mechanism
pitfall · examples
01 / THE SHORT VERSION
The idea in a few sentences.
Tools like Ansible, Puppet, or Chef define the desired state of servers in code — packages installed, services running, files placed. Ansible is agentless (SSH-based), while Puppet/Chef use agents. Running the tool converges the server toward the declared state, fixing any drift.
02 / FOLLOW THE MECHANISM
How ansible converges a server
Control node
runs
ansible-playbookwith an inventory (list of hosts) and a playbook (YAML tasks).Ansible engine
SSHs into each host (or uses WinRM for Windows) and copies the Python modules needed for the tasks.
Each task
checks the current state first (idempotency). Only makes changes if the actual state doesn't match the desired state.
Result
reports changed=1, failed=0, ok=15 per host. Changed tasks are shown in yellow, unchanged in green.
04 / COMMAND NOTES
Read the command, then the result.
Inspect the flags and arguments before trying an example. Snippets can need local setup, replacement values, or resources in your own environment.
test SSH connectivity to all inventory hosts
ansible all -m pingdry-run a playbook without making changes
ansible-playbook --check playbook.yml05 / CHECK YOURSELF
Could you explain Configuration Management to a teammate?
Try it out loud in two sentences: what it is, and the one detail that changes the picture. If you stall, the gap is the part to reread.
Up next in Delivery & operationsArtifact Managementstoring, versioning, and distributing build outputs