Advertisement
Advertisement

More Related Content

Advertisement
Advertisement

Development Doesn't Stop at the Last Commit

  1. Software developmentSoftware development does NOT stop at thedoes NOT stop at the last commitlast commit Kris Buytaert Open World Forum 2013, Paris @krisbuytaert
  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 @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 ● Evangelizing devopsEvangelizing devops
  3. What's this devops thingWhat's this devops thing anyhow ?anyhow ?
  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, 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 ........ Almost 20 events held in 2013.Almost 20 events held in 2013.
  5. devops, a definition:devops, a definition:
  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 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.
  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. Devops is a cultural andDevops is a cultural and professional movementprofessional movement Adam Jacob, OpscodeAdam Jacob, Opscode
  9. C(L)AMSC(L)AMS ● CultureCulture ● (Lean)(Lean) ● AutomationAutomation ● MeasurementMeasurement ● SharingSharing Damon Edwards and John WillisDamon Edwards and John Willis Gene KimGene Kim
  10. 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 safeIn a more safe ● Reliable fashionReliable fashion • Fully automatedFully automated ● More happyMore happy {customers,developers,managers,investors}{customers,developers,managers,investors}
  11. 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
  12. 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 ?
  13. Devs vs OpsDevs vs Ops
  14. Culture,Culture, automation,automation, Measturement,Measturement, sharingsharing
  15. Burn the SilosBurn the Silos
  16. Crossfunctional TeamCrossfunctional Team ● Project team with skills from all overProject 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
  17. One Team = One Goal !One Team = One Goal !
  18. Enable CommunicationEnable Communication
  19. Build TrustBuild Trust ● ExperimentExperiment • DevDev • TestTest ● ProdProd ● Automate all theAutomate all the thingsthings ● Measure successMeasure success ● Measure FailureMeasure Failure
  20. Lets Play TogetherLets Play Together Getting AlongGetting AlongOpsOpsDevsDevs
  21. Agile ?Agile ? ● Agile vs AgileAgile vs Agile ● Scrum vs KanbanScrum vs Kanban ● Definition of DoneDefinition of Done • Done means testedDone means tested • Done means in productionDone means in production • Done means monitored and in productionDone means monitored and in production
  22. A software project is not done untilA software project is not done until your last enduser is in his grave !your last enduser is in his grave ! Kris Buytaert, DOD Amsterdam 2013Kris Buytaert, DOD Amsterdam 2013
  23. Culture,Culture, Automation,Automation, Measurement,Measurement, SharingSharing
  24. 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 ?
  25. 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
  26. Test AutomationTest Automation ● Unit testsUnit tests ● Regression testsRegression tests ● SeleniumSelenium ● CucumberCucumber ● TDDTDD ● BDDBDD
  27. devops (<)> continuous delilverydevops (<)> continuous delilvery
  28. " 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/
  29. 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
  30. OrchestrationOrchestration ● On what servers is XYZ running ?On what servers is XYZ running ? ● Restart apache on all servers with fact XRestart apache on all servers with fact X ● Configure DBConfigure DB • then configure webthen configure web • then restart appthen restart app Over different hosts , automatedOver different hosts , automated ● Mcollective, Rundeck, Ansible ...Mcollective, Rundeck, Ansible ...
  31. Culture,Culture, Automation,Automation, Measurement :Measurement : measure all the thingsmeasure all the things SharingSharing
  32. 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 ●
  33. During developmentDuring development
  34. And runtimeAnd runtime Operating SystemOperating System ● diskdisk ● CpuCpu ● MemoryMemory ApplicationApplication ● #users#users ● #feature usage#feature usage ● response timeresponse timeMiddleWareMiddleWare ● TransactionsTransactions ● Queue lengthQueue length ● Api callsApi calls ● (Aborted) Connections(Aborted) Connections
  35. Math 101Math 101 ● f(x)f(x) ● f'(x)f'(x) ● f''(x)f''(x) ● ... statistics 101... statistics 101 ● Machine LearningMachine Learning
  36. Culture,Culture, Automation,Automation, Measurement,Measurement, SharingSharing
  37. DashboardsDashboards
  38. Visualize Business MetricsVisualize Business Metrics ● $revenue$revenue ● #sales#sales ● signupssignups ● conversionsconversions ● Api callsApi calls ● Application useApplication use
  39. SharingSharing ● Open SourceOpen Source ● Talk about ExperiencesTalk about Experiences ● Publish the codePublish the code ● No proprietary software was used in theseNo proprietary software was used in these slidesslides Don't get Locked In !Don't get Locked In !
  40. FoodFood
  41. It's not about the toolsIt's not about the tools
  42. ContactContact Kris BuytaertKris Buytaert Kris.Buytaert@inuits.beKris.Buytaert@inuits.be Further ReadingFurther Reading @krisbuytaert@krisbuytaert http://www.krisbuytaert.be/bhttp://www.krisbuytaert.be/b log/log/ http://www.inuits.be/http://www.inuits.be/ InuitsInuits Duboistraat 50Duboistraat 50 2060 Antwerpen2060 Antwerpen BelgiumBelgium 891.514.231891.514.231 +32 475 961221+32 475 961221
Advertisement