Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Is there a future for devops ?

1,639 views

Published on

Slides for my 2018 devopsdays Zurich Keynote

Published in: Technology

Is there a future for devops ?

  1. 1. Is there a future for devops ? Kris Buytaert @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 ● CTO and Open Source Consultant @CTO and Open Source Consultant @inuits.euinuits.eu ● Everything is a freaking DNS ProblemEverything is a freaking DNS Problem ● Evangelizing devopsEvangelizing devops ● Organiser of #devopsdays, #cfgmgmtcamp,Organiser of #devopsdays, #cfgmgmtcamp, #loadays, ….#loadays, ….
  3. 3. C(L)AMSC(L)AMS ● CultureCulture ● (Lean)(Lean) ● AutomationAutomation ● MeasurementMeasurement ● SharingSharing Damon Edwards and John WillisDamon Edwards and John Willis
  4. 4. A global movement to improve the quality of softwareA global movement to improve the quality of software delivery leveraging Open Source experience, starteddelivery leveraging Open Source experience, started in Gent in 2009in Gent in 2009
  5. 5. World DominationWorld Domination ● 2010 Sydney , MountainView, Hamburg, Sao2010 Sydney , MountainView, Hamburg, Sao PauloPaulo ● 2011 Boston, MountainView, Goteborg,2011 Boston, MountainView, Goteborg, ● 2012 Austin, Tokyo , MountainView, Rome2012 Austin, Tokyo , MountainView, Rome ● 2013 London (2x) Paris, Amsterdam2013 London (2x) Paris, Amsterdam
  6. 6. Future #devopsdaysFuture #devopsdays ● 175 events and counting175 events and counting ● 450+ organisers450+ organisers ● 50+ events in 201850+ events in 2018 ● Other eventsOther events with #devopswith #devops tracktrack
  7. 7. Why we study history ?Why we study history ? ● BecauseBecause I`m a grumpy old frustrated developerI`m a grumpy old frustrated developer sysadminsysadmin ● Because IBecause I`m an old opiniated guy`m an old opiniated guy ● Because history repeatsBecause history repeats ● We need to learn from our mistakesWe need to learn from our mistakes
  8. 8. Topic Evolution : CultureTopic Evolution : Culture ● Agile, Kanban, LeanAgile, Kanban, Lean ● Startups as examplesStartups as examples ● Success StoriesSuccess Stories ● UnicornsUnicorns ● Poster ChildsPoster Childs ● Agile, Fake Agile, Less, Safe,Agile, Fake Agile, Less, Safe, ● Enterprises as examples => NoEnterprises as examples => No examplesexamples ● How to include managementHow to include management ● FailureFailure ● BurnoutBurnout
  9. 9. Topic Evolution : AutomationTopic Evolution : Automation ● Cfengine, Puppet, ChefCfengine, Puppet, Chef ● Mcollective, Noah, RundeckMcollective, Noah, Rundeck ● Hudson, JenkinsHudson, Jenkins ● EC2, OpenStack, Cloudstack,EC2, OpenStack, Cloudstack, Eucalyptus,OpenNebula,Eucalyptus,OpenNebula, openQRMopenQRM ● Bash in Yaml “Basic”Bash in Yaml “Basic” ● Ansible, Rundeck, ChoriaAnsible, Rundeck, Choria ● Jenkins, GitlabCI, CircleCI,Jenkins, GitlabCI, CircleCI, TravisCITravisCI ● EC2, GCE, Azure, OpenStack,EC2, GCE, Azure, OpenStack,
  10. 10. Topic Evolution : AutomationTopic Evolution : Automation ● Xen, KVM, openVZ, lxcXen, KVM, openVZ, lxc ● VagrantVagrant ● Linux-HA, CoroSyncLinux-HA, CoroSync ● Ceph, Gluster, DRBD,Ceph, Gluster, DRBD, ● Docker , Docker, Docker,Docker , Docker, Docker, Docker, Moby, Rkt, lxc, cri-oDocker, Moby, Rkt, lxc, cri-o ● Docker , Docker, DockerDocker , Docker, Docker ● Swarm, Mesos, KubernetesSwarm, Mesos, Kubernetes ● NFSNFS
  11. 11. Topic Evolution : AutomationTopic Evolution : Automation ● Rspec, Cucumber, SeleniumRspec, Cucumber, Selenium ● TDDTDD ● cvs, svn, gitcvs, svn, git ● Release mgmtRelease mgmt ● Rspec, fitnesseRspec, fitnesse ● Security TestingSecurity Testing ● GitGit ● GitGit
  12. 12. Topic Evolution : MonitoringTopic Evolution : Monitoring ● NagiosNagios ● CactiCacti ● MuninMunin ● RRDRRD ● Zenoss, ZabbixZenoss, Zabbix ● #monitoringsucks#monitoringsucks ● IcingaIcinga ● ELKELK ● Graphite + GrafanaGraphite + Grafana ● CollectdCollectd ● PrometheusPrometheus ● #monitoringlove#monitoringlove
  13. 13. Tools will not fix your broken cultureTools will not fix your broken culture Tooling hype is not helpingTooling hype is not helping
  14. 14. Culture vs ToolsCulture vs Tools
  15. 15. The vendors struggleThe vendors struggle Selling “devops”Selling “devops” ● Is hardIs hard ● Is selling CultureIs selling Culture ● Is selling changeIs selling change ● Doesn't scaleDoesn't scale ● Doesn't get renewalsDoesn't get renewals You can't buyYou can't buy DevOps, but you mayDevOps, but you may need to sell it.need to sell it. Ken MugrageKen Mugrage
  16. 16. Why would thereWhy would there notnot be a future ?be a future ?
  17. 17. Because the IT industry isBecause the IT industry is awesome at ruining greatawesome at ruining great ideasideas
  18. 18. Is ITIL dead ?Is ITIL dead ? ● The last mileThe last mile ● The men who say noThe men who say no ● Guardians ofGuardians of ProductionProduction ● Friday at 10 amFriday at 10 am ● Reducing risk upfrontReducing risk upfront ● Machines makeMachines make decisionsdecisions ● Lower downtimeLower downtime ● ConstantlyConstantly ● Learn the LanguageLearn the Language ● Automate the stepsAutomate the steps ● Speed up 1000xSpeed up 1000x
  19. 19. Agile is dead ?Agile is dead ? ● WaterfallWaterfall ● WatermillWatermill ● Jira & StandupsJira & Standups ● SAFESAFE
  20. 20. Agile is dead ?Agile is dead ? ● People over ProcessPeople over Process ● Empowering TeamsEmpowering Teams ● LessLess ● ScrumScrum ● KanbanKanban
  21. 21. Is Open Source dead ?Is Open Source dead ? ● Open vs OpenOpen vs Open ● Open CoreOpen Core ● OpenStack (Money and Politics)OpenStack (Money and Politics) ● Marketing ScamsMarketing Scams
  22. 22. Who killed #devops ?Who killed #devops ?
  23. 23. We Broke the ToolsWe Broke the Tools ● 7 tools for your devops stack7 tools for your devops stack ● Puppet vs Chef vs AnsiblePuppet vs Chef vs Ansible ● Docker , the Ultimate “Devops” ToolDocker , the Ultimate “Devops” Tool ● Implement all the tools ..Implement all the tools ..
  24. 24. Recruiters Killed #devopsRecruiters Killed #devops ● It's not a job title.It's not a job title. ● Is it a developer ?Is it a developer ? ● Is it an ops engineer ?Is it an ops engineer ? ● Is it a system engineer writing code ?Is it a system engineer writing code ? ● Is it a developer running operations ?Is it a developer running operations ? ● My “Pimp” tells me I`m a #devops EngineerMy “Pimp” tells me I`m a #devops Engineer
  25. 25. #devopsteam#devopsteam ● It's not the team running toolingIt's not the team running tooling ● It's not the team in charge of deliveryIt's not the team in charge of delivery ● It's not yet another silo between devs and opsIt's not yet another silo between devs and ops
  26. 26. There is no such thingThere is no such thing ● Who is certified ?Who is certified ? ● By who ?By who ?
  27. 27. Certification killed everythingCertification killed everything ● ITIL => misses the goalITIL => misses the goal ● Scrum => makes it a procedureScrum => makes it a procedure ● Devops => the biggest scam of them allDevops => the biggest scam of them all ● For the cause of education ?For the cause of education ? ● Devops “insert your tool here” Certifcation ?Devops “insert your tool here” Certifcation ? ● Certification = Vendors milking usersCertification = Vendors milking users
  28. 28. Sales/Marketing peopleSales/Marketing people broke devopsbroke devops ● Devops ToolsDevops Tools ● Devops Certified ToolsDevops Certified Tools ● The Ultimate Devops ToolThe Ultimate Devops Tool ● Lots of people trying to make dishonest moneyLots of people trying to make dishonest money on a grass root movementon a grass root movement
  29. 29. Change Management &Change Management & ResistanceResistance ● 20 – 60 – 2020 – 60 – 20 ● 20% Early adopters , find your peers20% Early adopters , find your peers ● 60% Will wait , but adopt slowly60% Will wait , but adopt slowly ● 20%20%
  30. 30. #enterprise devops#enterprise devops ● ““You can only change small organisations”You can only change small organisations” ● ““You can't change a large organisation”You can't change a large organisation” ● ““You need to do things different“You need to do things different“ ● There is much more to changeThere is much more to change ● It takes longerIt takes longer ● The resistance is biggerThe resistance is bigger ● ““The antibodies kick in”The antibodies kick in”
  31. 31. #enterprise devops#enterprise devops ● Naming things is hardNaming things is hard – Naming things confused peopleNaming things confused people – Vendors have ruined the termVendors have ruined the term – Huge effort to explain realityHuge effort to explain reality ● Set your goals and name themSet your goals and name them – Common nameCommon name ● Don’t call it Spotify Model eitherDon’t call it Spotify Model either
  32. 32. YOLO EngineeringYOLO Engineering ● StartupStartup ● VCVC ● Exit StrategyExit Strategy ● Actual BusinessActual Business ● Real CustomersReal Customers ● SurvivalSurvival
  33. 33. 9 years later9 years later
  34. 34. Dev OoopsDev Ooops #container edition#container edition ● ““Put this Code Live, here's a DockerPut this Code Live, here's a Docker Image ”Image ” ● No machines available ?No machines available ? ● What database ? Where to storeWhat database ? Where to store the data ?the data ? ● Security ? What distro is this even ?Security ? What distro is this even ? Bad Cows ?Bad Cows ? ● How do we monitor his ?How do we monitor his ? ● Backups ?Backups ? ● How did you build this ?How did you build this ?
  35. 35. Yes, there is a future ..Yes, there is a future ..
  36. 36. But it’s not an easy one ...But it’s not an easy one ...
  37. 37. Teaching peopleTeaching people
  38. 38. A long JourneyA long Journey ● We are nowhere close to being finished..We are nowhere close to being finished.. – 2-5 year journeys are not uncommon for large2-5 year journeys are not uncommon for large orgsorgs – 2-3 waves of people are not uncommon2-3 waves of people are not uncommon – Burnout & Being fired is not uncommonBurnout & Being fired is not uncommon
  39. 39. The journey continuesThe journey continues ● Young organisations become oldYoung organisations become old ● New people onboardNew people onboard ● New technologies need to be embracedNew technologies need to be embraced
  40. 40. Our roleOur role tomorrowtomorrow todaytoday ● Teacher (for both collegues and suppliers)Teacher (for both collegues and suppliers) ● StudentStudent ● Math ExpertMath Expert ● DeveloperDeveloper ● TroubleshooterTroubleshooter ● EvangelistEvangelist ● ShrinkShrink ● Bridge BuilderBridge Builder
  41. 41. Every 18 months, automate yourselve out of yourEvery 18 months, automate yourselve out of your jobjob Someone at Google, longtime agoSomeone at Google, longtime ago
  42. 42. 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
  43. 43. Time to stand up againstTime to stand up against ● Broken CertificationBroken Certification ● Broken hiring processesBroken hiring processes ● Broken OutsourcingBroken Outsourcing ● Accepting work with no realistic budgetsAccepting work with no realistic budgets
  44. 44. Devops is here to stay,Devops is here to stay, New tools and technologies will appearNew tools and technologies will appear But collaboration will remain aBut collaboration will remain a requirementrequirement
  45. 45. The future is here,The future is here, it's still not evenly distributedit's still not evenly distributed Yet,Yet, and may never beand may never be
  46. 46. 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 Essensteenweg 31Essensteenweg 31 BrasschaatBrasschaat BelgiumBelgium 891.514.231891.514.231 +32 475 961221+32 475 961221

×