Your SlideShare is downloading. ×
Devops for  drupal
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Devops for drupal


Published on

My DrupalCon Munich introduction to Devops Talk

My DrupalCon Munich introduction to Devops Talk

Published in: Technology, Business

  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • Nr of users Nagios Plugins Prod_check
  • Vagrant etc
  • Transcript

    • 1. Whats this devops thing anyhow ? Kris Buytaert DrupalCon Munich , August 2012
    • 2. Kris Buytaert• I used to be a Dev,• Then Became an Op• Chief Trolling Officer and Open Source Consultant• Everything is an effing DNS Problem• Building Clouds since before the bookstore• Some books, some papers, some blogs• But mostly, trying to be good at my job• not related to @dries afaik
    • 3. Whats this devops thing about ?
    • 4. World , 200X-2009Patrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, JezzHumble, Lindsay Holmwood, John Allspaw, 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, Manilla, Sau Paulo, Tokyo Goteborg , October 2011 Austin , April 2012, Mountainview July 2012, Rome , October 2012 ....
    • 5. ● 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
    • 6. Devops, a definition:
    • 7. ● Adopt the new philosophy. We are in a new economic age. Western management must awaken to the challenge, must learn their responsibilities, and take on leadership for change.● Cease dependence on inspection to achieve quality. Eliminate the need for massive inspection by building quality into the product in the first place.● Improve constantly and forever the system of production and service, to improve quality and productivity, and thus constantly decrease costs.● Institute training on the job.● Institute leadership The aim of supervision should be to help people and machines and gadgets do a better job.● Drive out fear, so that everyone may work effectively for the company.● Break down barriers between departments. People in research, design, sales, and production must work as a team, in order to foresee problems of production and usage that may be encountered with the product or service.● Eliminate slogans, exhortations, and targets for the work force asking for zero defects and new levels of productivity. Such exhortations only create adversarial relationships, as the bulk of the causes of low quality and low productivity belong to the system and thus lie beyond the power of the work force. ● Eliminate management by objective. Eliminate management by numbers and numerical goals. Instead substitute with leadership. ● Remove barriers that rob the hourly worker of his right to pride of workmanship. The responsibility of supervisors must be changed from sheer numbers to quality. ● Remove barriers that rob people in management and in engineering of their right to pride of workmanship.● Institute a vigorous program of education and self-improvement.● Put everybody in the company to work to accomplish the transformation. The transformation is everybodys job.
    • 8. William Edwards Deming1986, Out of the Crisis.
    • 9. “DevOps is a cultural andprofessional movement” Adam Jacob
    • 10. CAMS● Culture● Automation● Measurement● Sharing Damon Edwards and John Willis
    • 11. 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 risk thanwe see in the Enterprise. This is true even whenyou factor in the greater flexibility and velocity ofstartups.Tim Bray , on his blog January 2010
    • 12. The real problem :● Friday evening at 16:59 “Put this Code Live, heres a tarball” NOW!● Backups ?● What database ?● Security ?● High Availability ?● Scalability ?● Who is on Call ?
    • 13. How did we get here ?
    • 14. A typical dev shop● The PM:•“Put this Code Live, heres a tarball” NOW!•Marketing Campain is launched•We need this yesterday•Its going on national radio at 5
    • 15. An oldschool ops shop● What dependencies ?● No machines available ?● What database ?● Security ?● High Availability ?● Scalability ?● My computer cant install this ?
    • 16. Devs vs Ops
    • 17. 10 days into production● 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 the fsck wrote this crap ?
    • 18. 11 days into production
    • 19. Is it really that bad ? How about Drupal ?A survey started a year ago.
    • 20. 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
    • 21. Talk about Non functional Reqs NOW!● Security● Backups● Upgradability● Deployment
    • 22. High Availabilty
    • 23. Scalability
    • 24. Monitor
    • 25. Breaking the SilosDevs Ops Getting Along
    • 26. 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
    • 27. 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
    • 28. How do we get there ?
    • 29. 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
    • 30. Drupalistas & Version Control
    • 31. Drupal & Continuous Integration
    • 32. Do YOU test your code ?
    • 33. Where do you develop ?● It works on my machine :(● What other platforms do you use :
    • 34. Sharing environments● Build identical environments● Share code● Shared ownership of content , code and configuration
    • 35. Vagrant● Abstraction layer for VirtualBox● Integrates well with Puppet/Chef● Project = ● Vagrantfile ● Manifests / Cookbooks● Portable, Small , Versionable● Use veewee to build your boxen
    • 36. do |config| # All Vagrant configuration is done here. The most common configuration # options are documented and commented below. For a complete reference, # please see the online documentation at config.vm.define :mongo1 do |mongo1_config| mongo1_config.ssh.max_tries = 100 = "MyCentOS2""") mongo1_config.vm.host_name = "mongo1" mongo1_config.vm.provision :puppet do |mongo1_puppet| mongo1_puppet.pp_path = "/tmp/vagrant-puppet" mongo1_puppet.manifests_path = "manifests" mongo1_puppet.module_path = "modules" mongo1_puppet.manifest_file = "site.pp" end end config.vm.define :mongo2 do |mongo2_config| mongo2_config.ssh.max_tries = 100 = "MyCentOS2""") mongo2_config.vm.host_name = "mongo2" mongo2_config.vm.provision :puppet do |mongo2_puppet| mongo2_puppet.pp_path = "/tmp/vagrant-puppet" mongo2_puppet.manifests_path = "manifests" mongo2_puppet.module_path = "modules" mongo2_puppet.manifest_file = "site.pp" end end
    • 37. Vagrant Rocks● Vagrant init● Vagrant up● Vagrant provision● Vagrant down● Vagrant destroy
    • 38. If my computer cant install yoursoftware, your software is broken. Luke Kanies, Fosdem 2007
    • 39. Infrastructure as Code● Automated Deployments● If my computer cant install it , the installer is borken● Reproducable● With configuration mgmt● Think :•Cfengine,Puppet, Chef● Put configs under version control
    • 40. Deployment● Database Imports are EVIL● Manual Installations are ● Error Prone How do you deploy ? ● Non Reproducible● 61% does it WRONG Do you Test Deployments ?
    • 41. 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 documentedby providing commands that we can copy and paste fromthe procedure 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
    • 42. If my computer cant deploy your site, it isnt worth deploying. Kris Buytaert, DrupalCon Munich 2012
    • 43. Challenges● What about the data ?● Content vs Config•Drupal provides no clear distinction● e.g a billing application•Table Creation•Provisioning (e.g. Rates, Call plan types)•Actual Data● D8 ?
    • 44. Devops a 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 ... .. failure is upon you ...
    • 45. Conclusions● Drupal gets it and is supportive● Conversation happens● Long Journey ahead● Heading in the right direction
    • 46. Surviving the test ! ● After 5+ years of preaching I`m not alone anymore ● Devops, a new Movement ! ● Join the movement ! • •Agile System Adminstration GoogleGroups
    • 47. Its not about the tools Its about changeIts about the people
    • 48. Open Up!Connecting Systems AND PEOPLE
    • 49. ContactKris BuytaertKris.Buytaert@inuits.euFurther Reading@krisbuytaert Inuits Duboistraat 50 2060 Antwerpen Belgium +32 475 961221