Ansible Automation
Getting Ansible working across a set of servers: inventory and authentication, ad-hoc commands, and writing and running playbooks. It records how to get started rather than restating the module reference.
Chapters
About this series
This series records the path to getting Ansible working: connecting one control node to a handful of managed nodes (inventory, authentication, the first-login fingerprint check), then moving up to ad-hoc commands and playbooks.
The goal is not to restate the module reference — the official documentation already does that well — but to record where the first setup actually gets stuck. The barrier to Ansible is not its syntax but its starting point: how to write the inventory, whether to authenticate with a key or a password, and why the first connection is blocked by a fingerprint prompt. In the docs these are scattered; in practice they arrive as one connected chain.