Production Operations & Config Management

What is it?

Production operations means changing servers safely and repeatably: version-controlled config, change windows, and configuration management (Ansible) that describes the desired state so many hosts stay identical.

Why it matters

Hand-editing 50 servers guarantees drift and mistakes. Describing the desired state once and applying it everywhere makes changes reviewable, repeatable and reversible.

Where you see it

An Ansible playbook declares 'package X present, service Y running, file Z with these contents'; running it makes reality match, and re-running is idempotent.

What normal looks like

Config in version control, changes applied through review and config management, and every host in a group provably identical.

What suspicious looks like

Snowflake servers hand-edited differently, an undocumented change no one can reproduce, or drift where 'identical' hosts behave differently.

How analysts investigate

When two 'identical' hosts differ, compare their managed config and history; the desired-state model makes the diff and the fix explicit rather than a mystery.

Common beginner mistakes

Hand-editing production instead of changing the source-of-truth config.
Applying a change to all hosts at once with no canary or rollback.

Desired state, everywhere, reversibly

  Ansible playbook (desired state, version-controlled):
    - package: nginx  state: present
    - service: nginx  state: started, enabled
    - copy: nginx.conf → /etc/nginx/  (then reload)
  apply to 50 hosts → all identical; re-run = no change (idempotent)
  change the PLAYBOOK, never hand-edit a single box

Config management applies a reviewed, version-controlled desired state to many hosts, idempotently.

Quick check

Two 'identical' web servers behave differently. Most likely cause?

A quick self-check — it doesn't affect your XP or progress.