Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

DevOps in the Wild

8.353 visualizaciones

Publicado el

From the Eduserv Symposium 2013 (http://www.eduserv.org.uk/newsandevents/events/2013/symposium) -- blog post with links to the suggested resources at http://blog.geekmanager.co.uk

Publicado en: Tecnología

DevOps in the Wild

  1. 1. DEVOPS INTHE WILDMERI WILLIAMSCHROMEROSE LTD@GEEK_MANAGER
  2. 2. LET’S STARTWITH A STORY
  3. 3. 8 YEARS AGO…I took over as Tech Lead for a product ata large company.It was a financial product within thelargest SAP installation in the world.(yeah, I know, YUCK)
  4. 4. AT THE TIME…There were over 100 tickets open.Only possible to release new code toproduction every three months.Half the tickets were related to the last 3releases.
  5. 5. I FELT A BIT LIKE THIS…
  6. 6. WHAT DID OPS THINKOF DEV?
  7. 7. WHAT DID DEV THINKOF OPS?
  8. 8. BOTH SIDES WERE ALITTLE BIT RIGHT …AND A LOT WRONG(BUT APPARENTLY I WAS THE FIRST ONEEVER TO ASK BOTH SIDES)
  9. 9. WHAT DID WE DO?On Dev side, we upped our game:• Introduced TDD and comprehensive testsOn the Ops side, we learnt to trust:• After first quarterly release that introduced no newissues (and closed 20+ tickets), agreed to monthlyreleasesMost of all, we learnt to COMMUNICATE and plannedTOGETHER.
  10. 10. WE FELT LIKE THIS
  11. 11. SINCE THEN, DEVOPSHAS BECOME A HOTTOPICBUT I’D ARGUE THAT NOW, IT’S ASURVIVAL SKILL
  12. 12. SOME DEFINITIONSDEVELOPMENT = the building of theproductOPERATIONS = the running of the productDEVOPS = philosophy of communicationand collaboration between these twoimportant specialties
  13. 13. FIRST, SOME ANTI-PATTERNSAN EXCELLENT LIST FROM DEVOPSGUYS
  14. 14. TRAPS TO AVOID• Mandating a DevOps “process”• Assuming Agile == DevOps (though they aregood partners in crime)• Rebranding Dev or Ops or any other team as“DevOps”• Starting a separate “DevOps group” (anothersilo…)• Enabling/allowing a hostile takeover
  15. 15. MORE TRAPS TO AVOID• Believing DevOps is a meaningless buzzword• Believing DevOps is a silver bullet (this shit ishard, yo)• Assuming DevOps means Devs Managing Production• Assuming DevOps is Dev-Driven ReleaseManagement• Excuses like wrong people / wrong time / “we’respecial”
  16. 16. THAT WASDEPRESSING,HUH?DON’T WORRY, THERE’S GOOD NEWS TOO
  17. 17. SO WHATDOES WORK?
  18. 18. CAMSCulture AutomationMeasurement SharingPer John Willis: http://www.opscode.com/blog/2010/07/16/what-devops-means-to-me/
  19. 19. CULTUREStart with people.Value Dev AND Ops.Openly. Encouragecollaboration.Focus on fast ANDstable.
  20. 20. AUTOMATIONINVEST in automatingeverything you can.Configuration, provisioning, releasedeployment, monitoring,orchestration, testing, systems integrationtesting, etc
  21. 21. MEASUREMENT
  22. 22. SHARING
  23. 23. GDS ARE IMPRESSIVEIN THIS REGARDDevOps philosophy + continuous delivery +monitoring + automation =
  24. 24. AND DON’T FORGET THEGDS BADGER OF DEPLOY
  25. 25. FURTHER READINGThe original DevOpsGuys post about anti-patterns:http://blog.devopsguys.com/2013/02/20/twelve-devops-anti-patterns/Niek Bartholomeus’ excellent presentation about introducing devops to a moretraditional environment:https://speakerdeck.com/niekbartho/devops-for-dinosaursThe DevOps section of GDS’ Digital Service Manual:https://www.gov.uk/service-manual/operations/devops.htmlAnna Kennedy put together a brilliant list of resources after DevOpsDays:http://annaken.blogspot.co.uk/2013/03/devops-community-resources.htmlDevOps Weekly newsletter: http://devopsweekly.com/
  26. 26. PS: REMEMBER TO LOVEYOUR SYSADMINS

×