1. Let's bring the teamsLet's bring the teams
back togetherback together
Devops, adapt or fail
@krisbuytaert
2. Kris BuytaertKris Buytaert
•
Chief Trolling Officer and Open SourceChief Trolling Officer and Open Source
Consultant @inuits.euConsultant @inuits.eu
•
Everything is an effing DNS ProblemEverything is an effing DNS Problem
•
Building Clouds since before the bookstoreBuilding Clouds since before the bookstore
•
Some books, some papers, some blogsSome books, some papers, some blogs
•
DrupalCon #devops global trackchairDrupalCon #devops global trackchair
•
Core #devopsdays organiser since day 1Core #devopsdays organiser since day 1
10. ● Adopt the new philosophy. We are in a new economic age. Western managementAdopt the new philosophy. We are in a new economic age. Western management
must awaken to the challenge, must learn their responsibilities, and take onmust awaken to the challenge, must learn their responsibilities, and take on
leadership for change.leadership for change.
● Cease dependence on inspection to achieve quality. Eliminate the need for massiveCease dependence on inspection to achieve quality. Eliminate the need for massive
inspection by building quality into the product in the first place.inspection by building quality into the product in the first place.
● Improve constantly and forever the system of production and service, to improveImprove constantly and forever the system of production and service, to improve
quality and productivity, and thus constantly decrease costs.quality and productivity, and thus constantly decrease costs.
● Institute training on the job.Institute training on the job.
● Institute leadership The aim of supervision should be to help people and machinesInstitute leadership The aim of supervision should be to help people and machines
and gadgets do a better job.and gadgets do a better job.
● Drive out fear, so that everyone may work effectively for the company.Drive out fear, so that everyone may work effectively for the company.
● Break down barriers between departments. People in research, design, sales, andBreak down barriers between departments. People in research, design, sales, and
production must work as a team, in order to foresee problems of production andproduction must work as a team, in order to foresee problems of production and
usage that may be encountered with the product or service.usage that may be encountered with the product or service.
● Eliminate slogans, exhortations, and targets for the work force asking for zero defectsEliminate slogans, exhortations, and targets for the work force asking for zero defects
and new levels of productivity. Such exhortations only create adversarialand new levels of productivity. Such exhortations only create adversarial
relationships, as the bulk of the causes of low quality and low productivity belong torelationships, 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.the system and thus lie beyond the power of the work force.
●
Eliminate management by objective. Eliminate management by numbersEliminate management by objective. Eliminate management by numbers
and numerical goals. Instead substitute with leadership.and numerical goals. Instead substitute with leadership.
●
Remove barriers that rob the hourly worker of his right to pride ofRemove barriers that rob the hourly worker of his right to pride of
workmanship. The responsibility of supervisors must be changed fromworkmanship. The responsibility of supervisors must be changed from
sheer numbers to quality.sheer numbers to quality.
●
Remove barriers that rob people in management and in engineering ofRemove barriers that rob people in management and in engineering of
their right to pride of workmanship.their right to pride of workmanship.
● Institute a vigorous program of education and self-improvement.Institute a vigorous program of education and self-improvement.
● Put everybody in the company to work to accomplish the transformation. ThePut everybody in the company to work to accomplish the transformation. The
transformation is everybody's job.transformation is everybody's job.
12. World , 200X-2009World , 200X-2009
Patrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, JezzPatrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, Jezz
Humble, Lindsay Holmwood, John Willis, Chris Read, Julian Simpson, LukeHumble, Lindsay Holmwood, John Willis, Chris Read, Julian Simpson, Luke
Kanies, John Allspaw and lots of others ..Kanies, John Allspaw and lots of others ..
Gent , October 2009Gent , October 2009
Mountain View , June 2010Mountain View , June 2010
Hamburg , October 2010Hamburg , October 2010
Boston, March 2011Boston, March 2011
Mountain View, June 2011Mountain View, June 2011
Bangalore, Melbourne,Bangalore, Melbourne,
Goteborg , October 2011Goteborg , October 2011
........
10+ Events being planned for 2013.10+ Events being planned for 2013.
13. ““DevOps is a cultural andDevOps is a cultural and
professional movement”professional movement”
Adam JacobAdam Jacob
15. Why do we need devops ?Why do we need devops ?
16. A typical dev shopA typical dev shop
● The PM:The PM:
•““Put this Code Live, here's a tarball” NOW!Put this Code Live, here's a tarball” NOW!
•Marketing Campain is launchedMarketing Campain is launched
•We need this yesterdayWe need this yesterday
•It's going on national radio at 5It's going on national radio at 5
17. An oldschool ops shopAn oldschool ops shop
● What dependencies ?What dependencies ?
● No machines available ?No machines available ?
● What database ?What database ?
● Security ?Security ?
● High Availability ?High Availability ?
● Scalability ?Scalability ?
● My computer can't install this ?My computer can't install this ?
27. Automate all the thingsAutomate all the things
● BuildBuild
• reproducable builds are undiscussablereproducable builds are undiscussable
● TestTest
•
testing reduces risktesting reduces risk
•
automate deployments of your test infraautomate deployments of your test infra
● DeployDeploy
•
Infrastructure as CodeInfrastructure as Code
•
100% automation100% automation
•
Can you rebuild your infrastructure ?Can you rebuild your infrastructure ?
28. Do you do Continuous Integration ?Do you do Continuous Integration ?
29. Do YOU test your code ?Do YOU test your code ?
31. How many times a day ?How many times a day ?
● 10 @ Flickr10 @ Flickr
● Deployments used to be painDeployments used to be pain
● Nobody dared to deploy a siteNobody dared to deploy a site
● Practice makes perfectPractice makes perfect
● Knowing you can vs constantly doing itKnowing you can vs constantly doing it
32. Infrastructure as CodeInfrastructure as Code
● Treat configuration automation as codeTreat configuration automation as code
● Development best practicesDevelopment best practices
•
Model your infrastructureModel your infrastructure
•
Version your cookbooks / manifestsVersion your cookbooks / manifests
•
Test your cookbooks/ manifestsTest your cookbooks/ manifests
•
Dev/ test /uat / prod for your infraDev/ test /uat / prod for your infra
● Model your infrastructureModel your infrastructure
● A working service = automated ( Application Code +A working service = automated ( Application Code +
Infrastructure Code + Security + Monitoring )Infrastructure Code + Security + Monitoring )
● Think Puppet, Chef, Cfengine, ...Think Puppet, Chef, Cfengine, ...
33. If my computer can't install yourIf my computer can't install your
software, your software is broken.software, your software is broken.
Luke Kanies, Fosdem 2007Luke Kanies, Fosdem 2007
34. Deploying a Drupal SiteDeploying a Drupal Site
● Drush_makeDrush_make
● ProfilesProfiles
● Features ,strongarm , Custom codeFeatures ,strongarm , Custom code
•
Configuration as CodeConfiguration as Code
● What with external apps and libraries?What with external apps and libraries?
• Lucene – Solr – Tika – BI softwareLucene – Solr – Tika – BI software
● Test before you drive!Test before you drive!
35. If my computer can't deploy your site,If my computer can't deploy your site,
it isn't worth deploying.it isn't worth deploying.
Kris Buytaert, DrupalCon Munich 2012Kris Buytaert, DrupalCon Munich 2012
38. Self Service MetricsSelf Service Metrics
● Being able to add new metricsBeing able to add new metrics
● Build your own dashboardsBuild your own dashboards
● Look at metrics / logs on all platformsLook at metrics / logs on all platforms
● Learn from the platformLearn from the platform
41. ● Collect from anywhereCollect from anywhere
● FilterFilter
● Send anywhereSend anywhere
● QueingQueing
43. StatsdStatsd
● A network daemon that runs on a zillionA network daemon that runs on a zillion
platform and listens for statistics, like countersplatform and listens for statistics, like counters
and timers, sent over UDP and sendsand timers, sent over UDP and sends
aggregates to one or more pluggable backendaggregates to one or more pluggable backend
services (e.g., Graphite).services (e.g., Graphite).
52. ConclusionsConclusions
● Drupal gets it and is supportiveDrupal gets it and is supportive
● Conversation happensConversation happens
● Long Journey aheadLong Journey ahead
● Heading in the right directionHeading in the right direction