Test-driven infrastructure development
summary
Claims that Test-Driven Development applied to Ansible roles lets teams ship automation into legacy, heterogeneous infrastructure with far fewer surprises, by writing tests against existing systems first, encoding operational knowledge as runnable checks, and running them in CI. The workflow uses molecule to create OpenStack/AWS/docker instances, uses pytest/testinfra style assertions to catch missing flags, privilege‑escalation and kernel/network differences, and treats Ansible roles as verified, deployable artifacts.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 0:31Title
- 1:09Who am I
- 3:52Why DNS
- 4:46Ansible
- 7:16Panic
- 7:28Peter
- 8:18Coding
- 9:42Documentation
- 10:25Performance testing
- 11:15DNS
- 12:19Testdriven infrastructure development
- 14:11Testing from who does know
- 14:29Testing from kunos
- 15:48Standard extensions
- 16:15Test run code
- 17:16Privilege escalation
- 17:53Alternative DNS server
- 18:27Network rules
- 19:00SSL certificate
- 19:12Open source
- 19:57Molecule
- 22:39Test workflow
- 23:24Example workflow
- 24:00Docker integration
- 24:53Support scenario
- 25:35Scenariobased workflow automation
- 27:00Scenario UDP tunnel
- 27:39Scenario convergence
- 27:55Conclusion
related talks
47mTest infrastructure on steroids
42mDevOps workflows with Ansible Engine/Tower
52mTest Driven Delivery of Infrastructure-As-Code
28mFrom Monitoring to Automated Testing of Your Infrastructure Code
15mTransforming Testing: The Power of TestOps
17mTDD for Infrastructure Code
12mProgressive DevOps approach using Ansible
33mTest Driven DevOps