Managing many servers.
WHAT THE PROBLEM IS
Servers configured by hand diverge, and nobody knows what differs.
WHAT CONFIGURATION MANAGEMENT PROVIDES
A written description of the intended state, applied repeatedly.
WHAT THAT ACHIEVES
Servers that match A record of what is configured Rebuilding without guesswork
WHAT THE COMMON TOOLS DO
Connect, compare current state against the description, and change only what differs.
WHAT IDEMPOTENT MEANS HERE
Applying the description twice changes nothing the second time.
WHY THAT IS THE CENTRAL PROPERTY
It makes running it safe and routine rather than risky.
WHAT TO PUT UNDER MANAGEMENT FIRST
Packages installed Users and keys Service configuration Scheduled tasks
WHAT TO KEEP OUT
Secrets, unless properly encrypted.
WHAT THE SIMPLEST STARTING POINT IS
Scripts in version control, run consistently.
WHY THAT COUNTS
It captures the intent, which is most of the benefit.
WHAT TO AVOID
Adopting a large tool for two servers Describing state in a tool and also changing things by hand
WHY THAT SECOND POINT
Manual changes are overwritten, or worse, silently retained.
WHAT TO ESTABLISH
That the description is the authority.
