Understanding DevOps

​DevOps, or "Agile Infrastructure", is a philosophy that aims to bridge the gap between development and operations using Agile techniques. It stresses collaboration, communication, and multi-disciplinary approaches across traditional organizational boundaries to ensure software is providing maximum value to the business.​

Transcript

1. J U S T I N K U L E S Z A
2. DEVOPS D E V O P S
3. DEVOPS What does DevOps try to solve? T H E P R O B L E M DEVOPS
4. DEVOPS “There’s a tacit assumption that projects will run late, and when they're delivered (if they’re ever delivered), they will underperform, and not deliver well against investment. It's a wonder any of us have a job at all!” S T E P H E N N E L S O N - S M I T H
5. DEVOPS What is different about DevOps? T H E S O LU T I O N DEVOPS
6. DEVOPS “Bridging the gap between projects and operations by using Agile techniques both in development, project management and system administration.” PAT R I C K D U B O I S
7. DEVOPS Broadly defined, DevOps is a philosophy or cultural approach that promotes better communication between two teams. T H E B A S I C S
8. DEVOPS Narrowly defined, DevOp is a job description for an employee who possesses the skills to work as a both a developer and a systems engineer. T H E B A S I C S
9. DEVOPS Communication. Collaboration. Multi-disciplinary approach. Understanding of the domain. Sensitivity and passion for the business. KEY PRINCIPLES
10. DEVOPS Battleground for development, operations, and QA. T H E T R A D I T I O N A L W AY: DEVOPS
11. DEVOPS Siloization. Lack of understanding. No shared goals. Different backgrounds and technical skills.
 TRADITIONAL THINKING
12. DEVOPS “Lob it over the wall” mentality. “It works on my machine” Changes are dangerous and time-consuming. Deployment is fraught with peril. TRADITIONAL PROBLEMS
13. DEVOPS A TRADITIONAL EXAMPLE DEVOPS
14. DEVOPS 1 DEVELOPMENT The developers team writes a ruby application on Windows using preferred tools, and gems which rely on native libraries.
15. DEVOPS 2 HANDOFF The ruby application is delivered to the operations team who plan to run the application in production on a Linux server which runs on metal.
16. DEVOPS 3 PROVISIONING The operations team provisions a server, and tries to get the application running using available libraries.
17. DEVOPS 4 PROBLEMS QA finds issues and bugs that were introduced because of missing libraries, different library versions, and environment configuration differences.
18. DEVOPS 5 BATTLE Development and operations flip issues back and forth, blaming each other for the problems: “It works on my machine.”
19. DEVOPS Breaking down barriers, building bridges, and stressing collaboration. T H E D E V O P S W AY: DEVOPS
20. DEVOPS Combines elements of Dev, Ops, and QA. Started as “Agile Infrastructure”. Much in common with agile software development, and the “Agile Manifesto” DEVOPS THINKING
21. DEVOPS Cooperation. Communication Short feedback loops. Teaching and learning. Paradigms to support and enable this. DEVOPS STRATEGIES
22. DEVOPS A DEVOPS EXAMPLE DEVOPS
23. DEVOPS 1 DEVELOPMENT The development team writes a ruby application on Windows, but using a Linux virtual machine, managed with Vagrant and Chef, as their platform for building the application and testing it.
24. DEVOPS 2 HANDOFF The operations team takes the Chef configuration used by the Developers to provision a new virtual server on AWS, making the new system nearly identical.
25. DEVOPS 3 DEPLOYMENT The application is continuously deployed via a post-receive git hook, and the QA team is able to quickly review new features, and provide feedback to the development team.
26. DEVOPS 4 LAUNCH When the application is ready for launch, new production virtual machines are provisioned alongside the existing systems, using the Chef configuration to ensure everything is identical.
27. DEVOPS 5 NEW FEATURES The application runs smoothly, and new features can be developed confidently using the established infrastructure and workflows.
28. DEVOPS T O O L S A N D P R A C T I C E S PA R A D I G M S
29. DEVOPS Effortless create/destroy environments as needed. Easy testing, portability, accessibility, etc. Examples: AWS, Rackspace, VMWare ESXi, etc. VIRTUALIZATION
30. DEVOPS Repeatability without human errors. Consistency, efficiency, security, etc. Examples: Vagrant, git hooks, make variants, etc. AUTOMATION
31. DEVOPS Confidence that the system will perform correctly. Reduce effects of ‘infrastructure by coincidence’ —it works, but we cannot prove why. Examples: Test kitchen, serverspec, etc. TESTING
32. DEVOPS Describe intended state of systems programmatically. ‘Infrastructure as Code’: managing systems as you would manage programs. Examples: Chef, Puppet, Ansible, etc. CODING
33. DEVOPS Code describes the state of a managed system. No forgotten documentation or unknown state. Examples: Chef, Puppet, Ansible, etc. DOCUMENTATION
34. DEVOPS U S I N G C H E F T O P R O V I S I O N A V I R T U A L S E R V E R E X A M P L E
35. DEVOPS B E N E F I T S
36. DEVOPS Increased confidence. Less risk and fear. Faster development and deployment. Greater reliability and quality. More effective systems. WHY DEVOPS?
38. DEVOPS The Phoenix Project
 Gene Kim, Kevin Behr and George Spafford DevOps Days
 http://www.devopsdays.org/ Dev2Ops
 http://dev2ops.org/ Patrick Dubois
 http://www.jedi.be/blog/ S O U R C E S