Infrastructure as Code

Transcript

1. What is IaC? Let’s start with the pets vs cattle analogy 2
2. With thousands of servers and services we can’t think of them as our pets (i.e. each being unique) Anti-Patterns: Handcrafted GUI-driven Ticket-based Reserved/Siloed Scale-up Proprietary
3. Servers as cattle: instead think of servers as replaceable and a commodity API-driven Self-service Automated Scale-out Composable components Open source
4. DevOps is integrating IT Operations and Development Developers Operations
5. DevOps CALMS Culture Measurement Sharing Automation Lean
6. IT Infrastructure should be treated like code • Automated with self service reusable modules • Remove • Speed, safe, predictable & verifiable outcomes • Remove manual, error prone steps • Manage change throughout lifecycle with version control • Plus provide documentation and validation through test deployments
7. IT Administrators/Operations will Shift Left • Version control • Changes in environment are represented by code changes • Documentation of environment through code, code comments, diagrams • Use of modules (functions) Developers Operations
8. How will the IT admin role change? • Admins will need to code • Not just CLI or scripting • Understand the developer process • Agile sprints, code pipeline • Be able to continuously deploy • Small, incremental changes
9. No Snowflakes! No server or configuration should be unique
10. How does the developer role change? • Developers need to understand ITSM • Operational processes, client and service management • Understand infrastructure • Networking segmentation, firewall rules, patching process, etc… • Be part of monitoring process • Be part of the lifecycle of the code
11. Enable the reconstruction of the business from nothing but a source code repository, an application data backup, and cloud service