Pulling the Puppet Strings with Ansible
summary
Red Hat IT describes migrating from CFEngine and a monolithic Puppet estate into Ansible since 2014, abandoning Puppet for new RHEL7/8 systems after wrestling with 500,000 lines of Puppet manifests and slow, flaky dependency ordering. The team uses Ansible for provisioning (AWS, OpenStack), configuration, OpenShift ops, and CI/CD, deploys AWX (Tower) for centralized execution and credentialed auto-healing (Nagios → Tower playbooks), evaluates Vault/Barbican for secrets, and builds a greenfield data center managed top-to-bottom by Ansible.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:05A Brief History of RH IT Config Management
- 5:02CF Engine Migration to Puppet (2007)
- 6:24Puppet Management Ideal
- 7:28Realities of Puppet a decade later...
- 11:43Hybrid Approach
- 13:25Tower / AWX
- 16:04Full Adoption
- 18:28Federated Management
- 20:52Playbook Management
- 22:36RHIT Operating System Support
- 26:55Lessons Learned
- 31:36Next Steps
related talks
34mIs that an Ansible? Stop holding it like a Puppet
26mOpenHPC on Ansible
36mGentle Introduction to Ansible
29mGood Practices and Security for your Ansible Automation Platform 2
39mContinuous Deployment with Ansible
29mAnsible Automation Platform based on OpenShift
18mManaging Standard Operating Envs with Ansible
39mAnsible - Your First Step Into Server Provisioning