Infrastructure as Code
0 likes284 views
The document discusses infrastructure automation inspired by software development practices, specifically focusing on 'infrastructure as code.' It covers challenges such as server sprawl and configuration drift, as well as principles like reproducibility, disposability, and consistent processes. Key practices include using definition files, version control, continuous testing, and specific tools for infrastructure definition.
![[01] Infrastructure as Code: Managing Servers in the Cloud, Kief Morris, Sep 2015
[02] Amazon Web Services AWS LiveLessons
[03] Infrastructure As Code, Martin Fowler, Mar 2016](https://image.slidesharecdn.com/infrastructureascode-170406024751/85/Infrastructure-as-Code-26-320.jpg)
Infrastructure as Code
- 1. Infrastructure automation based on practices from software development Infrastructure as Code (Overview) leandro.rosa { @hpe.com, @gmail.com } @leandro_r0sa
- 2. Topics – Challenges with Dynamic Infrastructure – What Is Infrastructure as Code? – Principles of Infrastructure as Code – Practices
- 8. What is Infrastructure as Code?
- 9. Infrastructure automation based on practices from software development
- 10. Consistent, repeatable routines for provisioning and changing systems and their configuration
- 11. Principles of Infrastructure as Code
- 12. Systems Can Be Easily Reproduced Systems Are Disposable Systems Are Consistent Processes Are Repeatable Design Is Always Changing
- 13. “Treat your servers like cattle, not pets”
- 14. Practices
- 15. Use Definition Files Self-Documented Systems and Processes Version All the Things Continuously Test Systems and Processes Small Changes Rather Than Batches Keep Services Available Continuously
- 16. Use Definition Files Scriptable Interface Unattended Execution Externalized Configuration Idempotent Pre-checks Post-checks Visible failure Parameterized
- 17. Configuration Definition Files Type Focus Tools Server configuration What goes onto a server CFEngine Puppet Chef Ansible* Infrastructure definition High-level infrastructure elements and relationships AWS Cloud Formation HashiCorp Terraform OpenStack Heat Chef Provisioning Ansible* *Mixed concerns
- 18. Example: Definition of “Provisioning” 1. Assigning resources to the element 2. Instantiating the element 3. Installing software onto the element 4. Configuring the element 5. Registering the element with infrastructure services
- 19. Example: Terraform configuration file
- 20. Using Infrastructure Definition Tools $ terraform apply -var environment=qa web_server.tf
- 21. Example: Passing configuration to Chef from Terraform
- 22. Example: Creating Resources with AWS CloudFormation
- 25. References
- 26. [01] Infrastructure as Code: Managing Servers in the Cloud, Kief Morris, Sep 2015 [02] Amazon Web Services AWS LiveLessons [03] Infrastructure As Code, Martin Fowler, Mar 2016
- 27. Thank you