Ansible

Series: Ansible Like a Pro Part 1: Why Ansible Won Config Management — Config management landscape, why Ansible won, the architecture of ansible-navigator and execution environments Part 2: Building a Real Execution Environment — Pinned and private collections, Python dependency conflicts, the additional_build_steps escape hatch, a local registry for sharing Part 3 ← You are here — Inventories, your first real playbook, the navigator TUI versus stdout, artifacts and replay, and the first-week mistakes Part 4: Roles, Reuse, and Keeping It Honest — Planned Two parts of plumbing. That’s what you’ve sat through so far. Part 1 was the why, Part 2 was the container the why runs in. Neither of them configured a single server. ...

Series: Ansible Like a Pro Part 1: Why Ansible Won Config Management — Config management landscape, why Ansible won, the architecture of ansible-navigator and execution environments Part 2 ← You are here — Building a real execution environment: pinned and private collections, Python dependency conflicts, the additional_build_steps escape hatch, and a local registry for sharing Part 3: Writing Your First Playbook with Navigator — Inventories, your first real playbook, the navigator TUI versus stdout, artifacts and replay, and the first-week mistakes In Part 1 we built an execution environment. Twenty lines of YAML, one ansible-builder build, and we were running playbooks inside a container. That was the toy. ...

Series: Ansible Like a Pro Part 1 ← You are here — Config management landscape, why Ansible won, architecture of ansible-navigator and execution environments Part 2: Building a Real Execution Environment — Pinned and private collections, Python dependency conflicts, the additional_build_steps escape hatch, a local registry for sharing Part 3: Writing Your First Playbook with Navigator — Inventories, your first real playbook, the navigator TUI versus stdout, artifacts and replay, and the first-week mistakes I’ve been doing config management for over a decade now. Puppet in 2012. Chef in 2014. Salt around 2016. Ansible since 2017. I’ve got the scars. ...

Creating a modular, reproducible automation framework to deploy OpenStack and validate networking performance.