No Compromise: Use Ansible properly or stick to your scripts
summary
Shows concrete fixes: replace fragile shell/command tasks with a custom Ansible module written in Python that implements proper version checks, supports check mode, and returns accurate changed/results so `ansible --check` actually predicts changes. Adds unit tests (pytest) and playbook asserts, moves app configuration into Ansible templates so handlers only restart what changed, and uses local_action/fake hosts plus a REST client to deploy to Mesos via API. Result: dry runs work, fewer unnecessary restarts, automated rollouts.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:27No Compromise: Use Ansible properly or stick to your scripts
- 1:02Short Ansible Example
- 3:18Where do we use Ansible
- 4:42How we started
- 6:50Application Deployment Problems
- 9:21Why an Ansible Module?
- 10:51A Bundle Deployment Module
- 12:53Usage Testing
- 17:01Eat your own Dog Food
- 18:54Deployment without Machines
- 20:34Deploy to a fake Host
- 22:07Summary
- 23:50Configuration and Handler Problems
