Devops, The future is here, it's just not evenly distributed

662 views

Published on

Slides for IT is Happening NOW event by Cevora

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
662
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Devops, The future is here, it's just not evenly distributed

  1. 1. Devops, the future is hereDevops, the future is here It's just not evenly distributed @KrisBuytaert
  2. 2. Kris BuytaertKris Buytaert ● I used to be a Dev,I used to be a Dev, ● Then Became an OpThen Became an Op ● Chief Trolling Officer and Open SourceChief Trolling Officer and Open Source Consultant @Consultant @inuits.euinuits.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 ● Evangelizing devopsEvangelizing devops
  3. 3. What's this Devops thing really about ?What's this Devops thing really about ?
  4. 4. 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, andHumble, Lindsay Holmwood, John Willis, Chris Read, Julian Simpson, and lots of others ..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 ........
  5. 5. devops, a definition:devops, a definition:
  6. 6. ● 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 numbers and numericalEliminate management by objective. Eliminate management by numbers and numerical goals. Instead substitute with leadership.goals. Instead substitute with leadership. •Remove barriers that rob the hourly worker of his right to pride of workmanship. TheRemove 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.responsibility of supervisors must be changed from sheer numbers to quality. •Remove barriers that rob people in management and in engineering of their right toRemove barriers that rob people in management and in engineering of their right to pride of workmanship.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.
  7. 7. William EdwardsWilliam Edwards DemingDeming 1986, Out of the Crisis.1986, Out of the Crisis. http://en.wikipedia.org/wiki/W._Edwards_Deminghttp://en.wikipedia.org/wiki/W._Edwards_Deming
  8. 8. C(L)AMSC(L)AMS ● CultureCulture ● (Lean)(Lean) ● AutomationAutomation ● MeasurementMeasurement ● SharingSharing Damon Edwards and John WillisDamon Edwards and John Willis Gene KimGene Kim
  9. 9. Whats in it for you ?Whats in it for you ? ● Faster time to marketFaster time to market • Features go live in hours vs yearsFeatures go live in hours vs years ● In a more safe (Secure)In a more safe (Secure) ● Reliable fashionReliable fashion • Fully automatedFully automated ● More happyMore happy {customers,developers,managers,investors}{customers,developers,managers,investors}
  10. 10. How did we get here ?How did we get here ?
  11. 11. The Old DaysThe Old Days ● ““Put this Code Live, here's a tarball” NOW!Put this Code Live, here's a tarball” NOW! ● 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 ?
  12. 12. Devs vs OpsDevs vs Ops
  13. 13. (Historically) Different Goals(Historically) Different Goals DevelopmentDevelopment ● New releasesNew releases ● New FeaturesNew Features ● New platformsNew platforms ● New architecturesNew architectures ● Functional ReqFunctional Req OperationsOperations ● Stable PlatformStable Platform ● No DowntimeNo Downtime ● Scalable PlatformScalable Platform ● Non Functional ReqNon Functional Req
  14. 14. We can solve this !We can solve this ! ● Some people thinkSome people think the Ops work startsthe Ops work starts on deploymenton deployment ● It starts much earlierIt starts much earlier ● Get Devs and Ops toGet Devs and Ops to talk asaptalk asap
  15. 15. Culture,Culture, automation,automation, Measturement,Measturement, sharingsharing
  16. 16. Step 0Step 0 ● Be PatientBe Patient ● Devops is hardDevops is hard ● Rome/Etsy was not build in 1 weekRome/Etsy was not build in 1 week
  17. 17. Burn the SilosBurn the Silos
  18. 18. Crossfunctional TeamCrossfunctional Team ● Build a project team with skills from all overBuild a project team with skills from all over • DevelopmentDevelopment • Continuous IntegrationContinuous Integration • TestingTesting • Infrastructure (HA/ Scale/ Performance)Infrastructure (HA/ Scale/ Performance) • DeploymentDeployment • MeasurementMeasurement ● Seat them together !Seat them together ! ● Goal = Help the businessGoal = Help the business
  19. 19. Enable CommunicationEnable Communication
  20. 20. Improve CommunicationImprove Communication ● Chatrooms <- force people to be onlineChatrooms <- force people to be online • TopicTopic • Virtual WatercoolerVirtual Watercooler • ChatOpsChatOps ● Virtual and Physical StandupsVirtual and Physical Standups ● Hangout / JabberHangout / Jabber
  21. 21. No New Silos !No New Silos ! Don't call it a devops teamDon't call it a devops team
  22. 22. Build TrustBuild Trust ● ExperimentExperiment • DevDev • TestTest ● ProdProd ● Automate all theAutomate all the thingsthings ● Measure successMeasure success ● Measure FailureMeasure Failure
  23. 23. Give AccessGive Access ● Shared goal -> Shared Problem -> SharedShared goal -> Shared Problem -> Shared responsibilitiesresponsibilities ● Everyone is on callEveryone is on call ● Full platform accessFull platform access • LogsLogs • MetricsMetrics • ToolsTools ● Do you let a blind buy paint your house ?Do you let a blind buy paint your house ?
  24. 24. Grow UpGrow Up Getting AlongGetting AlongOpsOpsDevsDevs
  25. 25. • Take 1 small stepTake 1 small step • PreparePrepare Do not spread the word to soon....Do not spread the word to soon.... • You won't be ready anyhowYou won't be ready anyhow • Celebrate SuccessCelebrate Success • Showcase successesShowcase successes • Create JealousyCreate Jealousy GrowGrow
  26. 26. BondBond ● Hack DaysHack Days ● Teach a collegue daysTeach a collegue days ● Ramdon Lunch meetupsRamdon Lunch meetups ● Eat CakeEat Cake ● Both inside and outside the officeBoth inside and outside the office
  27. 27. What tool?What tool?
  28. 28. Culture,Culture, Automation,Automation, Measurement,Measurement, SharingSharing
  29. 29. 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 ?
  30. 30. NirvanaNirvana An “ecosystem” that supports continuous delivery, fromAn “ecosystem” that supports continuous delivery, from infrastructure, data and configuration management toinfrastructure, data and configuration management to business.business. Through automation of the build, deployment, and testingThrough automation of the build, deployment, and testing process, and improved collaboration between developers,process, and improved collaboration between developers, testers, and operations, delivery teams can get changestesters, and operations, delivery teams can get changes released in a matter of hours — sometimes even minutes–noreleased in a matter of hours — sometimes even minutes–no matter what the size of a project or the complexity of its codematter what the size of a project or the complexity of its code base.base. Continuous Delivery , Jez HumbleContinuous Delivery , Jez Humble
  31. 31. How do we get there ?How do we get there ?
  32. 32. Use Version ControlUse Version Control No ExcusesNo Excuses Also for scripts/config/cookbooks,manifests,etcAlso for scripts/config/cookbooks,manifests,etc
  33. 33. Continuous IntegrationContinuous Integration ● BuildsBuilds ● Nightly BuildsNightly Builds ● Builds with testsBuilds with tests ● Nightly Builds with testsNightly Builds with tests ● Frequent integrationFrequent integration ● Continuous IntegrationContinuous Integration
  34. 34. CI ToolsCI Tools ● HudsonHudson ● JenkinsJenkins •A zillion pluginsA zillion plugins ● Make your builds reproducible !Make your builds reproducible ! ● Test your (Puppet/Chef/CFengine)Test your (Puppet/Chef/CFengine)
  35. 35. Build PipelinesBuild Pipelines
  36. 36. Test AutomationTest Automation ● Unit testsUnit tests ● Regression testsRegression tests ● SeleniumSelenium ● CucumberCucumber ● TDDTDD ● BDDBDD
  37. 37. 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
  38. 38. " Our job as engineers (and ops, dev-ops, QA," Our job as engineers (and ops, dev-ops, QA, support, everyone in the company actually) is tosupport, everyone in the company actually) is to enable the business goals. We strongly feel thatenable the business goals. We strongly feel that in order to do that you must havein order to do that you must have the ability tothe ability to deploy code quickly and safelydeploy code quickly and safely. Even if the. Even if the business goals are to deploy strongly QA’d codebusiness goals are to deploy strongly QA’d code once a month at 3am (it’s not for us, we push allonce a month at 3am (it’s not for us, we push all the time), having a reliable and easythe time), having a reliable and easy deployment should bedeployment should be non-negotiablenon-negotiable."." Etsy Blog upon releasing DeployinatorEtsy Blog upon releasing Deployinator http://codeascraft.etsy.com/2010/05/20/quantum-of-deployment/http://codeascraft.etsy.com/2010/05/20/quantum-of-deployment/
  39. 39. 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, ... ● IAC -ne scriptingIAC -ne scripting
  40. 40. Deployment isn't the EndDeployment isn't the End
  41. 41. Culture,Culture, Automation,Automation, Measurement :Measurement : measure all the thingsmeasure all the things SharingSharing
  42. 42. Why #monitoringsucksWhy #monitoringsucks Monitoring is AWESOME. Metrics are AWESOME. I love it. Here's what I don't love:Monitoring is AWESOME. Metrics are AWESOME. I love it. Here's what I don't love: ● Having my hands tied with the model of host and service bindings.Having my hands tied with the model of host and service bindings. ● Having to set up "fake" hosts just to group arbitrary metrics togetherHaving to set up "fake" hosts just to group arbitrary metrics together ● Having to either collect metrics twice - once for alerting and another for trendingHaving to either collect metrics twice - once for alerting and another for trending ● Only being able to see my metrics in 5 minute intervalsOnly being able to see my metrics in 5 minute intervals ● Having to chose between shitty interface but great monitoring or shitty monitoringHaving to chose between shitty interface but great monitoring or shitty monitoring but great interfacebut great interface ● Dealing with a monitoring system that thinks IT is the system of truth for myDealing with a monitoring system that thinks IT is the system of truth for my environmentenvironment ● Not actually having any real choicesNot actually having any real choices John Vincent (@lusis) on his blog http://lusislog.blogspot.com/2011/06/why-John Vincent (@lusis) on his blog http://lusislog.blogspot.com/2011/06/why- monitoring-sucks.htmlmonitoring-sucks.html
  43. 43. GraphiteGraphite ● Graphing at ScaleGraphing at Scale ● Graphing at EaseGraphing at Ease ● Any metric is a graphAny metric is a graph ● echo "somestring $somevalue $timestamp" |echo "somestring $somevalue $timestamp" | nc <%= graphitehost %> 2003nc <%= graphitehost %> 2003
  44. 44. LogstashLogstash ● Not your average centralized logging toolNot your average centralized logging tool ● Elasticsearch backedElasticsearch backed ● ShipperShipper ● IndexerIndexer ● WebWeb
  45. 45. 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 LogfilesLearn from the Logfiles ● Learn from the platformLearn from the platform ●
  46. 46. Math 101Math 101 ● f(x)f(x) ● f'(x)f'(x) ● f''(x)f''(x) ● ... statistics 101... statistics 101
  47. 47. Monitoring & MetricsMonitoring & Metrics • Oculus , Skyline, Riemann, Esper,Oculus , Skyline, Riemann, Esper, • FlapJack (2nd incarnation)FlapJack (2nd incarnation) • BPM & MonitoringBPM & Monitoring • Creating Information out of this dataCreating Information out of this data • Big dataBig data • Machine LearningMachine Learning
  48. 48. Culture,Culture, Automation,Automation, Measurement,Measurement, SharingSharing
  49. 49. DashboardsDashboards
  50. 50. Visualize Business MetricsVisualize Business Metrics ● $revenue$revenue ● #sales#sales ● signupssignups ● conversionsconversions ● Api callsApi calls ● Application useApplication use
  51. 51. SharingSharing ● Open SpaceOpen Space ● Open SourceOpen Source ● GithubGithub ● Talk about ExperiencesTalk about Experiences ● Publish the codePublish the code
  52. 52. FoodFood
  53. 53. Quiz Time :Quiz Time : Which tool did I forget ?Which tool did I forget ?
  54. 54. YouYou
  55. 55. It's not about the toolsIt's not about the tools It's about changeIt's about change It's about the peopleIt's about the people
  56. 56. HomeworkHomework
  57. 57. ContactContact Kris BuytaertKris Buytaert Kris.Buytaert@inuits.beKris.Buytaert@inuits.be Further ReadingFurther Reading @krisbuytaert@krisbuytaert http://www.krisbuytaert.be/blog/http://www.krisbuytaert.be/blog/ http://www.inuits.be/http://www.inuits.be/ InuitsInuits Essensesteenweg 31Essensesteenweg 31 BrasschaatBrasschaat BelgiumBelgium 891.514.231891.514.231 +32 475 961221+32 475 961221
  58. 58. Images:Images: http://www.flickr.com/photos/huffstutterrobertl/4135257384/http://www.flickr.com/photos/huffstutterrobertl/4135257384/ http://www.flickr.com/photos/brighton/2153602543/http://www.flickr.com/photos/brighton/2153602543/ http://www.flickr.com/photos/gchorus/2074271352/http://www.flickr.com/photos/gchorus/2074271352/ http://www.flickr.com/photos/49024304@N00/2951673691/sizes/l/http://www.flickr.com/photos/49024304@N00/2951673691/sizes/l/ http://www.flickr.com/photos/30302096@N06/2953698548/http://www.flickr.com/photos/30302096@N06/2953698548/ http://www.flickr.com/photos/jamescridland/613445810/http://www.flickr.com/photos/jamescridland/613445810/ http://www.flickr.com/photos/johnmcga/4468003947/http://www.flickr.com/photos/johnmcga/4468003947/

×