Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Devops Devops Devops, at Froscon

Devops, Devops , Devops, from Dev and Ops to Devops presented at Froscon in Sankt-Augusting (Germany) on August 21st 2011

  • Login to see the comments

Devops Devops Devops, at Froscon

  1. 1. Devops, Devops, Devops Kris Buytaert
  2. 2. Kris Buytaert● I used to be a Dev,● Then Became an Op● Senior Linux and Open Source Consultant● „Infrastructure Architect“● Building Clouds since 2004 th● Surviving the 10 floor test● Co-Author Virtualization with Xen● Guest Editor at● But mostly, a DevOp
  3. 3. Alternative Titles● Grumpy old Sysadmin● Devops, Devops, Devops th● Surviving the 10 floor test● Agile Administration● Devministration, your new Job Title
  4. 4. Devop, definition● 30 something● Senior Infrastructure guy● Development background● Open Source Expcerience● Mostly European (.be / .uk)● Likes Belgian Beer● Likes Sushi
  5. 5. Whats this Devops thing really about ?
  6. 6. World , 200X-2009Patrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, JezzHumble, Lindsay Holmwood, John Willis, Chris Read, Julian Simpson, and lots of others .. Gent , October 2009 Mountain View , June 2010 Hamburg , October 2010 Boston, March 2011 Mountain View, June 2011 Bangalore, Melbourne, Goteborg
  7. 7. ● Devops is a growing movement● We dont have all the answers yet● We are reaching out to different communities● We will point out problems we see..● Only the name is new While we are still working out the solutions
  8. 8. CAMS● Culture● Automation● Measurement● Sharing Damon Edwards and John Willis
  9. 9. Whats the problem ?The community of developers whose work yousee on the Web, who probably don’t know whatADO or UML or JPA even stand for, deploy bettersystems at less cost in less time at lower riskthan we see in the Enterprise. This is true evenwhen you factor in the greater flexibility andvelocity of startups.Tim Bray , on his blog January 2010
  10. 10. How did we get here ?
  11. 11. The Old Days● “Put this Code Live, heres a tarball” NOW!● What dependencies ?● No machines available ?● What database ?● Security ?● High Availability ?● Scalability ?● My computer cant install this ?
  12. 12. Devs vs Ops
  13. 13. 10 days into operation● What High Load ? What Memory usage ?● Are these Logs ? Or this is actualy customer data ?● How many users are there , should they launch 100 queries each ?? Oh were having 10K users● Why is debugging enabled ?● Who wrote this ?
  14. 14. 11 days into operations
  15. 15. We can solve this ! ● Some people think the Ops work starts on deployment • Ops = both system, app as platform ! ● It starts much earlier ● Get Devs and Ops to talk asap
  16. 16. Talk about Nonfunctional Reqs NOW!● Security● Backups● High Availability● Upgradability● Deployment● Monitoring● Scale
  17. 17. Breaking the SilosDevs Ops Getting Along
  18. 18. NirvanaAn “ecosystem” that supports continuous delivery, frominfrastructure, data and configuration management tobusiness.Through automation of the build, deployment, and testingprocess, and improved collaboration between developers,testers, and operations, delivery teams can get changesreleased in a matter of hours — sometimes even minutes–nomatter what the size of a project or the complexity of its codebase. Continuous Delivery , Jez Humble
  19. 19. How many times a day ?● 10 @ Flickr● Deployments used to be pain● Nobody dared to deploy a site● Practice makes perfect● Knowing you can vs constantly doing it
  20. 20. " Our job as engineers (and ops, dev-ops, QA,support, everyone in the company actually) is toenable the business goals. We strongly feel thatin order to do that you must have the ability todeploy code quickly and safely. Even if thebusiness goals are to deploy strongly QA’d codeonce a month at 3am (it’s not for us, we push allthe time), having a reliable and easydeployment should be non-negotiable."Etsy Blog upon releasing Deployinator
  21. 21. How do we get there ?
  22. 22. CI Tools● Hudson● Jenkins • A zillion plugins● Make your builds reproducible !
  23. 23. Todays Enviroments For Devs For Ops● Version Control ● Version Control● Automated Build ● Automated Build● Bugtracking ● Bugtracking● Continous integration ● Continous integration● Integrated testing ● Integrated testing● Automated ● Automated deployment deployment
  24. 24. Devministration ?● For Both Devs and Ops● Yes we write code also • Httpd.conf, squid.conf, my.cnf • Just crappy languages :) • Shell, perl, ruby, python, puppet● Everyone is a developer these days • Automate your infrastructure !● So those rules apply for Ops Too !
  25. 25. Going Live
  26. 26. Deploying● Automated Deployments● If my computer cant install it , the installer is borken● Reproducable● Think: • Kickstart, FAI, Preseeding, SystemImager Suite
  27. 27. Deploying an app● Code vs Config● Think: • Capistrano, Controltier, Fabric● Pulling stuff from version control • Is your repo accessible from production ?● Lots of ops people like stuf packaged • .rpm, .deb, not .tgz , not .war
  28. 28. Why ops like to package● Packages give you features • Consistency, security, dependencies● Uniquely identify where files come from • Package or cfg-mgmt● Source repo not always available • Firewall / Cloud etc ..● Weird deployment locations , no easy access● Little overhead when you automate● CONFIG does not belong in a package
  29. 29. Jordan Sissel is a Hero ! Use FPM
  30. 30. Looking for ?“As a system administrator, I can tell when softwarevendors hate me. It shows in their products.”“DONT make the administrative interface a GUI. Systemadministrators need a command-line tool for constructingrepeatable processes. Procedures are best documented byproviding commands that we can copy and paste from theprocedure document to the command line. We cannotachieve the same repeatability when the instructions are:"Checkmark the 3rd and 5th options, but not the 2ndoption, then click OK." Sysadmins do not want a GUI thatrequires 25 clicks for each new user.” Thomas A. Limoncelli in ACM Queue December 2010
  31. 31. Configuration Mgmt● Configure 1000 nodes,● Modify 2000 files,● Together● Think : • Cfengine,Puppet, Chef● Put configs under version control
  32. 32. Deployment isnt the End
  33. 33. Orchestration● Manage 1000 nodes,● Trigger • Upgrades • Config Runs • Service Changes● Think : • Mcollective • Noah • Rundeck
  34. 34. High Availabilty
  35. 35. Scalability
  36. 36. Monitor
  37. 37. But Monitoring Stinks !● #monitoringsucks trending●● 2007 Study :Nagios + Friends● 2011 Conclusion : Nagios/Icinga are the only automatable alternatives● Monitoring at Scale : new kids Graphite, flapjack, etc● What about Logging ? : Logstash, Graylog2
  38. 38. Its not about the tools Its about change Its about the people
  39. 39. The full monty● Behaviour and functional testing to test upgrades and new developments● Automated Testing based on Continuous Integration● Automated Test Deployments● Automated Production Deployments● Feedback Loops● Measurement !● Controlled Continuous Deployment
  40. 40. Surviving the test ! ● After 5+ years of preaching I`m not alone anymore ● Devops, a new Movement ! ● Join the movement ! • • Agile System Adminstration GoogleGroups
  41. 41. Devop, definition● There is no definition● It certainly isnt a person● No strict rules● No strict tools● Its not even new● If you arent doing it already ... ... you are doing it wrong
  42. 42. Survey for Drupal
  43. 43. ContactKris BuytaertKris.Buytaert@inuits.beFurther Reading@krisbuytaert Inuits Esquimaux t Hemeltje Kheops Business Gemeentepark 2 Center 2930 Brasschaat Avenque Georges 891.514.231 Lemaître 54 6041 Gosselies +32 473 441 636 889.780.406 +32 495 698 668
  44. 44. Images: