Is that an Ansible? Stop holding it like a Puppet
summary
Compares Puppet’s agented state convergence (agents, master, Hiera, PuppetDB) with Ansible’s agentless orchestration (SSH, playbooks, roles, inventories) and concludes: use Puppet when you need continuous, convergent state across many OS variants and large scale; use Ansible for just‑in‑time deployments and ordered orchestration, CI/CD style tasks, or when orchestration needs to wait for services to become ready. Mentions tooling ecosystem (Puppet Forge, Ansible Galaxy, Foreman, AWX) and that running both together is common and practical.
AI-written summary · about
chapters (13)
- 0:00Introduction and setup
- 1:26Why talk about Puppet and Ansible
- 4:41Config management basics
- 7:28How Puppet works
- 8:34How Ansible works
- 12:50Puppet vs Ansible differences
- 16:42When to use Puppet
- 19:51When to use Ansible
- 21:59Metaphor for Puppet and Ansible
- 23:47Ansible best practices
- 28:23Puppet vs Ansible use cases
- 31:41Final recommendations
- 32:23Closing and job opportunities
related talks
36mPulling the Puppet Strings with Ansible
46mAnsible for developers
37mAnsible 101
01h 05mAnsible Basics
36mGentle Introduction to Ansible
49mWhen PowerShell Is Better Than Ansible? Recipes for Managing 1,000+ Servers
28mNo Compromise: Use Ansible properly or stick to your scripts
39mContinuous Deployment with Ansible