Devops in with the old, in with the new

Embed Size (px)

Citation preview

  1. 1. Devops in with the old, in with the new Jan Collijs @visibilityspots
  2. 2. Jan Collijs2012 Linux & Open-Source consultant @ inuits.eu Focus on operations
  3. 3. A short story about a typical deployment process ...
  4. 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. 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. 6. and on the 11th day
  7. 7. We can solve this! Ops work doesn't start at deployment. It starts much earlierGet Devs and Ops to talk ASAP !
  8. 8. So what is Devops then?
  9. 9. It is A human problemA corporate culture problemYou cant directly change culture. But you can change behavior, and behavior becomes culture Lloyd Taylor VP Infrastructure, Ngmoco
  10. 10. Devops CultureAutomation(Lean)MeasurementSharing Damon Edwards and John Willis(DevopsCafe podcast)
  11. 11. Talk about requirements SecurityVersion ControlBackupsAutomated BuildsHigh availabilityUpgradabilityIntegrated BugtrackingContinuous IntegrationAutomated TestingAutomated Deployment on test platformsConfiguration Management Monitoring
  12. 12. Talk about goals Stable PlatformNew releasesNo DowntimeNew FeaturesScalable PlatformNew platformsNon Functional ReqNew architecturesFunctional Req
  13. 13. Step 1Don't call it a devops team
  14. 14. Step 2 Be PatientDevops is hardRome/Etsy was not build in 1 week
  15. 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. 16. Crossfunctional Team Build a project team with skills from all over DevelopmentContinuous IntegrationTestingInfrastructure (HA/ Scale/ Performance) DeploymentMeasurementSeat them together !Goal = Help improve the business
  17. 17. Enable Communication
  18. 18. Improve Communication Chatrooms (being online = being available) TopicVirtual watercoolerChatOpsVirtual and physical standups (hangout / jabber)Transfer knowledgeNot only inside the team
  19. 19. Start Hiring Internally / ExternallyGet experience on boardGet the team on the same page
  20. 20. No code ninjas
  21. 21. No superhero admins
  22. 22. One team => one goal !
  23. 23. Playtime!DevsOpsGetting along
  24. 24. Make a consencus Measure all the thingsNo manual changesNo quick winsVersion all the thingsAutomate all the things..Have fun
  25. 25. Build Trust Experiment devtestProdMeasure successMeasure failure
  26. 26. Give access Shared goal -> shared problem -> shared responsibilitiesEveryone is on callFull platform access LogsMetricsTools
  27. 27. Grow Take small stepsPrepare Do not spread the word to soon....Celebrate successShowcase successesCreate jealousy (in a healthy way)
  28. 28. Understand failureMTTR (mean time to repair)mine is shorter than Yours
  29. 29. Your machines as cattle
  30. 30. Treat your people as pets
  31. 31. Give them toys
  32. 32. Food
  33. 33. Beer
  34. 34. Friendship Hackathon days/weekendsTeach a collegue days (TTT's)Random lunch meetupsEat cakeInside and outside the officeDuring and after working hours
  35. 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. 36. Contact Jan Collijs [email protected] Further Reading @visibilityspots http://www.visibilityspots.com http://www.inuits.eu/Inuits Duboistraat 50 2060 Antwerpen Belgium +32 479 586488