Downloaded 15 times
Infrastructure as Code
- 1.
- 2. Why Infrastructure asCode matters: a short story
- 3. “the Enterprise” Business EngineeringOperations Project A Project B Project C Ping! Value Stream
- 4. “Enterprise Projects” Business EngineeringOperations Project A Project B Project C Ping! Value Stream Let’s create a new product
- 5. Business Engineering Operations ProjectA Project B Project C Ping! Value Stream We’re going agile! CI, TDD 2 weeks
- 6. Business Engineering Operations ProjectA Project B Project C Ping! Value Stream Oh crap!
- 7. Business Engineering Operations ProjectA Project B Project C Ping! Value Stream Application is working fine on Test environment
- 8. Business Engineering Operations ProjectA Project B Project C Ping! Value Stream We’re ready to go live!
- 9. Business Engineering Operations ProjectA Project B Project C Ping! Value Stream YaY!
- 10. Business Engineering Operations ProjectA Project B Project C Ping! Value Stream Oh crap!
- 11. Business Engineering Operations ProjectA Project B Project C Ping! Value Stream We need a staging and production environment
- 12. Business Engineering Operations ProjectA Project B Project C Ping! Value Stream Sure but…
- 13. Business Engineering Operations ProjectA Project B Project C Ping! Value Stream We need to prepare those environments
- 14. Business Engineering Operations ProjectA Project B Project C Ping! Value Stream It will take 2 weeks
- 15. Business Engineering Operations ProjectA Project B Project C Ping! Value Stream Oh crap!Oh crap!
- 16. Eventually the environments areavailable and ready
- 17. but there isa Configuration mismatch b/w Test, Staging and Production
- 18. Houston, we havea problem!
- 19. Business Engineering Operations ProjectA Project B Project C Ping! Value Stream Oh crap!Oh crap! Oh crap!
- 20. an additional 2days to figure out the configuration issues
- 21. and finally theymanage to deploy the new application in production
- 22. instead of 2weeks Final outcome…
- 23. 4 weeks &2 days to production! Final outcome…
- 24. The problem isn’toperations
- 25. The problem islack of automation
- 26. The problem isthat they’re configuring and provisioning infrastructure manually
- 27.
- 28. In this talk,we’ll go through a real-world example:
- 29. We’ll deploy aloadbalancer and 2 droplet instances on DigitalOcean
- 30. with Terraform asour Infrastructure as Code tool
- 31. • I’m PrasantKumar • Senior DevOps Architect @
- 32. Want a free10$ credit on DigitalOcean? Tweet: #iacwithdoIaC rocks
- 33. Slides and Codefrom this talk: github.com/prasantk/iac slideshare.net/prasantk82
- 34. Outline • Infrastructure asCode Introduction • It’s requirements • Demo • Q & A
- 35. Infrastructure as Code(IaC)is about treating infrastructure as a software system
- 36. IaC is theconcept of managing your operations environment in the same way you do applications or other code for general release
- 37. IaC itself isnot sufficient
- 38. IaC needs a DynamicInfrastructure Platform
- 39. Dynamic Infrastructure Platform Asystem that provides computing resources, particularly servers, storage, and networking, in a way that they can be programmatically allocated and managed.
- 40. Characteristics of dynamicinfrastructure platform Programmable: • a programming API • good support for scripting languages
- 41. Programmable: Simple Terraform scriptthat uses the DigitalOcean API Characteristics of dynamic infrastructure platform
- 42. On-Demand: • allows resourcesto be created and destroyed immediately • fulfil provisioning requests within minutes Characteristics of dynamic infrastructure platform
- 43. Self-Service: • ability totailor and customize resources specific to the needs • ease of use and flexibility Characteristics of dynamic infrastructure platform
- 44.
- 45. • Reuse • Automation •Version Control • Testing • Documentation • Enable collaboration IaC Benefits
- 46. Business Engineering Operations ProjectA Project B Project C Ping! Value Stream nirvana!nirvana! nirvana!
- 47.