Infrastructure as code
Aug. 19, 2015•0 likes•586 views
Download to read offline
Report
Software
A quick overview of the practice of infrastructure as code, along with an intro to Puppet and Vagrant
rouanwFollow
More Related Content
More from rouanw
NDC Security 2023rouanw
Is this okay!? DevSecCon ⚡ 2022rouanw
Fail better with QA in Productionrouanw
Qa in production singular 2019rouanw
How to review a pull requestrouanw
Rouan's design principlesrouanw
Recently uploaded
Why Should You Choose a Personal Trainer over Group Gym Classes? Neighborhood Trainer
What is Microsoft Power BI used for.pptxJohnCommuserv
A Guide to Java Dynamic Proxies and It in CodingMikeConner22
ROAD TO NODES - Intro to Neo4j + NeoDash.pdfNeo4j
Deckible POV - Point of ViewNick Kellet
Winter 24 Highlights.pdfPatrickYANG48
Infrastructure as code
- 1. v a g r a n t a n d p u p p e t INFRASTRUCTURE AS CODE Rouan Wilsenach @rouanw
- 2. WHAT ? 2
- 3. 3 Scripting the configuration of your environment
- 4. WHY ? 4
- 5. 5 Confidence
- 6. 6 INTENTIONALITY By design, not coincidence
- 7. 7 TIME TO RECOVERY Automated testing. Reproducibility.
- 8. 8 BONUS: SOURCE CONTROL Collaboration. Tracking. Continuous Integration.
- 9. HOW ? 9
- 12. A BIT ABOUT PUPPET 12 Declarative Idempotent Dependency Tree
- 13. AND VAGRANT ? 13
- 14. VAGRANT 14 Testing infrastructure automation Production-like development Virtualisation wrapper
- 15. DEMO Let’s look at some code 15
- 16. For questions or suggestions: ! Rouan Wilsenach @rouanw rmw@thoughtworks.com THANK YOU