Downloaded 52 times
Uploaded byKris Buytaert
Devops for drupal
Kris Buytaert gave a talk on DevOps at DrupalCon Munich in 2012. He discussed how the silos between development and operations created problems, and how the DevOps movement aims to break down those barriers through automation, collaboration, and continuous delivery. DevOps is not defined by specific tools but by cultural and process changes like integrating operations work into the entire software lifecycle from early on. The talk covered challenges like managing data and environments across different stages and how tools like Vagrant and configuration management can help address them.
More Related Content
Devops for drupal
- 1. What's this devopsthing 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 @inuits.eu • 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. What's this devopsthing about ?
- 4. World , 200X-2009 PatrickDebois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, Jezz Humble, 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 don't 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.
- 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 everybody's job.
- 8. William Edwards Deming 1986, Out of the Crisis. http://en.wikipedia.org/wiki/W._Edwards_Deming
- 9. “DevOps is acultural and professional movement” Adam Jacob
- 10. CAMS ● Culture ● Automation ● Measurement ● Sharing Damon Edwards and John Willis
- 11. What's the problem? The community of developers whose work you see on the Web, who probably don’t know what ADO or UML or JPA even stand for, deploy better systems at less cost in less time at lower risk than we see in the Enterprise. This is true even when you factor in the greater flexibility and velocity of startups. Tim Bray , on his blog January 2010
- 12. The real problem: ● Friday evening at 16:59 “Put this Code Live, here's a tarball” NOW! ● Backups ? ● What database ? ● Security ? ● High Availability ? ● Scalability ? ● Who is on Call ?
- 13. How did weget here ?
- 14. A typical devshop ● The PM: •“Put this Code Live, here's a tarball” NOW! •Marketing Campain is launched •We need this yesterday •It's going on national radio at 5
- 15. An oldschool opsshop ● What dependencies ? ● No machines available ? ● What database ? ● Security ? ● High Availability ? ● Scalability ? ● My computer can't install this ?
- 16.
- 17. 10 days intoproduction ● 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 we're having 10K users ● Why is debugging enabled ? ● Who the fsck wrote this crap ?
- 18. 11 days intoproduction
- 19. Is it reallythat bad ? How about Drupal ? A survey started a year ago.
- 20. We can solvethis ! ● 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.
- 23.
- 24.
- 25. Breaking the Silos Devs Ops Getting Along
- 26. Nirvana An “ecosystem” thatsupports continuous delivery, from infrastructure, data and configuration management to business. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers, and operations, delivery teams can get changes released in a matter of hours — sometimes even minutes–no matter what the size of a project or the complexity of its code base. Continuous Delivery , Jez Humble
- 27. How many timesa 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 weget 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
- 34. Drupal & Continuous Integration
- 35. Do YOU testyour code ?
- 37. Where do youdevelop ? ● It works on my machine :( ● What other platforms do you use :
- 38. Sharing environments ● Build identical environments ● Share code ● Shared ownership of content , code and configuration
- 39. Vagrant ● Abstraction layer for VirtualBox ● Integrates well with Puppet/Chef ● Project = ● Vagrantfile ● Manifests / Cookbooks ● Portable, Small , Versionable ● Use veewee to build your boxen
- 40. Vagrantfile Vagrant::Config.run 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 vagrantup.com. config.vm.define :mongo1 do |mongo1_config| mongo1_config.ssh.max_tries = 100 mongo1_config.vm.box = "MyCentOS2" mongo1_config.vm.network("192.168.99.101") 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 mongo2_config.vm.box = "MyCentOS2" mongo2_config.vm.network("192.168.99.102") 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
- 41. Vagrant Rocks ● Vagrant init ● Vagrant up ● Vagrant provision ● Vagrant down ● Vagrant destroy
- 42. If my computercan't install your software, your software is broken. Luke Kanies, Fosdem 2007
- 43. Infrastructure as Code ● Automated Deployments ● If my computer can't install it , the installer is borken ● Reproducable ● With configuration mgmt ● Think : •Cfengine,Puppet, Chef ● Put configs under version control
- 44. Deployment ● Database Imports are EVIL ● Manual Installations are ● Error Prone How do you deploy ? ● Non Reproducible ● 61% does it WRONG Do you Test Deployments ?
- 45. Looking for ? “Asa system administrator, I can tell when software vendors hate me. It shows in their products.” “DON'T make the administrative interface a GUI. System administrators need a command-line tool for constructing repeatable processes. Procedures are best documented by providing commands that we can copy and paste from the procedure document to the command line. We cannot achieve the same repeatability when the instructions are: "Checkmark the 3rd and 5th options, but not the 2nd option, then click OK." Sysadmins do not want a GUI that requires 25 clicks for each new user.” Thomas A. Limoncelli in ACM Queue December 2010 http://queue.acm.org/detail.cfm?id=1921361
- 46. If my computercan't deploy your site, it isn't worth deploying. Kris Buytaert, DrupalCon Munich 2012
- 47. 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 ?
- 48. Devops a definition ● There is no definition ● It certainly isn't a person ● No strict rules ● No strict tools ● It's not even new ● If you aren't doing it already ... .. failure is upon you ...
- 49. Conclusions ● Drupal gets it and is supportive ● Conversation happens ● Long Journey ahead ● Heading in the right direction
- 50. Surviving the test! ● After 5+ years of preaching I`m not alone anymore ● Devops, a new Movement ! ● Join the movement ! •Devopsdays.org •Agile System Adminstration GoogleGroups
- 51. It's not aboutthe tools It's about change It's about the people
- 52. Open Up! Connecting Systems AND PEOPLE
- 53. Contact Kris Buytaert [email protected] Further Reading @krisbuytaert http://www.krisbuytaert.be/blog/ http://www.inuits.eu/ Inuits Duboistraat 50 2060 Antwerpen Belgium +32 475 961221