Devops in with the old, in with the new
- 1. Devops in with the old, in with the new Jan Collijs @visibilityspots
- 2. Jan Collijs ● 2012 – Linux & Open-Source consultant @ inuits.eu • Focus on operations
- 3. A short story about a typical deployment process ...
- 4. One day before release ● “Put this code live, here's a tarball, kthxbye!” “What dependencies has it? Where do I put it? What database? Does it need to be highly available? What traffic are you expecting?” ● “Not much, just install it..” “Okay :-/”
- 5. 10 days into operation ● “The servers are slow!” Why is our load so high? Why is all the memory used? Where does this thing write its logs? Why is that web page generating 100 queries? Debugging is still enabled? Who wrote this $#!* ?!
- 6. … and on the 11th day
- 7. We can solve this! ● Ops work doesn't start at deployment. It starts much earlier ● Get Devs and Ops to talk ASAP !
- 8. So what is Devops then?
- 9. It is • A human problem • A corporate culture problem “You can’t directly change culture. But you can change behavior, and behavior becomes culture” – Lloyd Taylor VP Infrastructure, Ngmoco
- 10. Devops ● Culture ● Automation ● (Lean) ● Measurement ● Sharing Damon Edwards and John Willis (DevopsCafe podcast)
- 11. Talk about requirements Security ● Version Control Backups ● Automated Builds High availability ● Upgradability Integrated Bugtracking ● Continuous Integration ● Automated Testing ● Automated Deployment on test platforms Configuration Management Monitoring
- 12. Talk about goals Stable Platform ● New releases No Downtime ● New Features Scalable Platform ● New platforms Non Functional Req ● New architectures ● Functional Req
- 13. Step 1 Don't call it a devops team
- 14. Step 2 • Be Patient • Devops is hard • Rome/Etsy was not build in 1 week
- 15. Listen, analyse ● What are devs nagging about • • ● Slow builds ? No enviroments ? What are ops nagging about • • ● Deployement proces ? No logs ? What is mgmt nagging about • Quality / Feedback ?
- 16. Crossfunctional Team ● Build a project team with skills from all over • Development • Continuous Integration • Testing • Infrastructure (HA/ Scale/ Performance) • Deployment • Measurement ● Seat them together ! ● Goal = Help improve the business
- 18. Improve Communication ● Chatrooms (being online = being available) • Topic • Virtual watercooler • ChatOps ● Virtual and physical standups (hangout / jabber) ● Transfer knowledge ● Not only inside the team
- 19. Start “Hiring” ● Internally / Externally ● Get experience on board ● Get the team on the same page
- 20. No code ninjas
- 22. One team => one goal !
- 24. Make a consencus ● Measure all the things ● No manual changes ● No quick wins ● Version all the things ● Automate all the things ● .. ● Have fun
- 26. Give access ● Shared goal -> shared problem -> shared responsibilities ● Everyone is on call ● Full platform access • Logs • Metrics • Tools
- 27. Grow • Take small steps • Prepare Do not spread the word to soon.... • Celebrate success • Showcase successes • Create jealousy (in a healthy way)
- 28. Understand failure MTTR (mean time to repair) • • mine is shorter than Yours
- 29. Your machines as cattle
- 30. Treat your people as pets
- 31. Give them toys
- 32. Food
- 33. Beer
- 34. Friendship ● Hackathon days/weekends ● Teach a collegue days (TTT's) ● Random lunch meetups ● Eat cake ● Inside and outside the office ● During and after working hours
- 35. Devops is like security It's not a product that you can buy It's a lifestyle It's a continuous improvement process
- 36. Contact Jan Collijs jan.collijs@inuits.eu Further Reading @visibilityspots http://www.visibilityspots.com http://www.inuits.eu/ Inuits Duboistraat 50 2060 Antwerpen Belgium +32 479 586488