DevOpsPorto Meetup19: Infrastructure as code - a DevOps Enabling Tool by Diana Martins

With the appearance of DevOps, a product’s lifecycle stops being about separate stages conducted by independent teams. It transitioned to a continuous process carried out by teams sharing knowledge, thoughts, opinions, and tools. IaC tools allow infrastructure deployment and configuration management through code, proving themselves as a strong link element between devs and ops.

Transcript

1. INFRASTRUCTURE AS CODE A DevOps enabling tool Diana Martins - dsm@eurotux.com
2. MOVING BUSINESS FORWARD www.eurotux.com INFRASTRUCTURE AS CODE A DevOps enabling tool Diana Martins - dsm@eurotux.com
3. 3 SCHEDULE Infrastructure as Code 2 3 4 5 1 DEVOPS: THE PHILOSOPHY INFRASTRUCTURE AS CODE CHALLENGES PRINCIPLES TRADE-OFFS TOOLS WHAT DO WE NEED? 6 7
4. 4 DEVOPS The philosophy
5. 5 DEVOPS The philosophy
6. 6 THE NEW NORMAL Developers and ops engineers share knowledge and work together in a product’s lifecycle. OPERATIONS ‣ System administrators; ‣ DBAs; ‣ Release managers; ‣ Security; ‣ Monitoring; ‣ Maintain. DEVELOPERS ‣ Gather requirements; ‣ Write code; ‣ Write automated tests; ‣ Manual testing; ‣ Refactor; ‣ Create. DEVOPS The philosophy
7. 7 DEVOPS The philosophy Practice that assumes the joint participation of ops engineers and developers in a product’s lifecycle since the design, passing through the development, until production and support processes.
8. 8 INFRASTRUCTURE AS CODE The breakthrough
9. 9 INFRASTRUCTURE AS CODE The breakthrough Software development techniques, practices, and tools applied to the creation of reusable, easily maintainable, extensible, and testable infrastructure. Dynamic infrastructure
10. 10 DYNAMIC INFRASTRUCUTURE: CHALLENGES Infrastructure as Code ‣ Server sprawl; ‣ Configuration drift; ‣ Snowflake servers; ‣ Fragile infrastructure; ‣ Automation fear; ‣ Erosion.
11. 11 PRINCIPLES Infrastructure as Code ‣ Systems are: ‣ Easily reproducible; ‣ Disposable; ‣ Consistent; ‣ Processes can be repeated; ‣ Design is always changing.
12. ADVANTAGES ‣  Infrastructure versioning; ‣  Process automation; ‣  Self-documented infrastructure and processes; ‣  Processes’ and systems’ testability. DISADVANTAGES ‣  Can bring disruptive changes to processes; ‣  Demands processes’ standardization and exhaustive description before execution; ‣  Wrong configurations are spread across every machine; ‣  Marginalizes hotfixes. TRADE-OFFS Infrastructure as Code 12
13. 13 INFRASTRUCTURE AS CODE Tools
14. 14 INFRASTRUCTURE AS CODE The breakthrough Infrastructure deployment Configuration management
15. 15 INFRASTRUCTURE DEPLOYMENT Infrastructure as Code ‣ Code infrastructure where the application runs: ‣  Servers; ‣  Network; ‣  Users; ‣  Security. ‣ Document; ‣ Repeat.
16. 16 INFRASTRUCTURE DEPLOYMENT Tools Azure Resource Manager
17. 17 CONFIGURATION MANAGEMENT Infrastructure as Code ‣ Rapidly transform a server: ‣ Install requirements; ‣ Easy reconfiguration; ‣ Avoids dependency problems; ‣ Installation and configuration processes are stored as code; ‣ Cures deployment pains allowing: ‣ Blue/green deployments; ‣ Rolling deployments. Push Pull
18. PUSH PULL CONFIGURATION MANAGEMENT Tools 18
19. 19 WHAT DO WE NEED?
20. 20 LOSE THE FEAR!
21. eurotux.com linkedin.com/company/eurotux-sa facebook.com/eurotux twitter.com/eurotux youtube.com/eurotuxsa Portugal Rua Irmãs Missionárias do Espírito Santo, 27 - 4715-340 Braga, Portugal info@eurotux.com +351 253 680 300 Moçambique Avenida 24 de Julho n.º 2041, 1º andar Maputo - Moçambique info@eurotux.co.mz +258 21 420 687 Thank you! Diana Martins dsm@eurotux.com