Downloaded 12 times
Uploaded byKris Buytaert
From devoops to devops
This document discusses the concepts of devops and how to transition an organization to a devops model. Some key points: - Devops aims to break down silos between development and operations through culture, automation, measurement, and sharing. - Traditional organizations have opposing goals between dev and ops that cause issues. Devops promotes a cross-functional team approach. - Automating builds, testing, deployments, infrastructure management reduces risk and improves collaboration. - Monitoring and metrics should be built in from the start so teams can learn from data and continuously improve. - Culture change can be difficult but focusing on mindset, collaboration and incremental goals can help transition teams.
More Related Content
From devoops to devops
- 1. From devoops, todevops ING Loves IT April 2017 ,Bucharest Kris Buytaert @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 @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 ● Organiser of #devopsdays, #cfgmgmtcamp,Organiser of #devopsdays, #cfgmgmtcamp, #loadays, ….#loadays, ….
- 3. What's this devopsWhat'sthis devops thing anyhow ?thing anyhow ?
- 6. C(L)AMSC(L)AMS ● CultureCulture ● (Lean)(Lean) ●AutomationAutomation ● MeasurementMeasurement ● SharingSharing Damon Edwards and John WillisDamon Edwards and John Willis Gene KimGene Kim
- 7.
- 8. Historical Organisations 101HistoricalOrganisations 101
- 9. The walls ofConfusionThe walls of Confusion
- 10. Opposing GoalsOpposing 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
- 11. Traditional OrganisationTraditional Organisation ●BureacracyBureacracy ● RulesRules ● TraditionsTraditions ● Lack of FreedomLack of Freedom ● Lots of ManagersLots of Managers ● Exodus of EngineersExodus of Engineers
- 12. Careers in TechCareersin Tech • People trying to make themselves relevantPeople trying to make themselves relevant • Peter principle:Peter principle: Promoted beyond their competencePromoted beyond their competence • Tech folks are forced into management, notTech folks are forced into management, not supported to grow technicalysupported to grow technicaly • ““Architects”Architects”
- 13. So what's devoops?So what's devoops ? ● ““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 ?
- 14. These DaysThese Days ●““Put this Code Live, here's a Docker Container ”Put this Code Live, here's a Docker Container ” ● No machines available ?No machines available ? ● What database ? Where to store the data ?What database ? Where to store 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 ?
- 15. Adopting a Devops:Adoptinga Devops: • MindsetMindset • LifestyleLifestyle • VisionVision
- 16. SpoilerSpoiler Your real problemis most probably not technicalYour real problem is most probably not technical
- 17. Change Management &ChangeManagement & 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%
- 18. Wild project plans!Wild project plans ! Can you make your change journey a traditionalCan you make your change journey a traditional project with milestones andproject with milestones and • We are a new orgWe are a new org • Bold move, or Just luck ?Bold move, or Just luck ? • Old Management Style to install a new CultureOld Management Style to install a new Culture
- 19. Do not callit aDo not call it a #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
- 20. Do not callthemDo not call them #devops engineers#devops engineers ● 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 ?
- 21. 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 !
- 22. Agile ?Agile ? ●WaterfallWaterfall ● WatermillWatermill ● SAFESAFE ● ScrumScrum ● KanbanKanban
- 23. Is your organisationagile,Is your organisation agile, or just your silo ?or just your silo ?
- 24. The BusinesThe Busines ●Doesn't care how weDoesn't care how we run ITrun IT ● Can't adapt theirCan't adapt their processesprocesses ● Isn't involved inIsn't involved in building softwarebuilding software ● Doesnt survive if weDoesnt survive if we don't deliverdon't deliver ● Is waiting for theirIs waiting for their featuresfeatures ● Is based on softwareIs based on software
- 25. Pitfalls Merging TeamsPitfallsMerging Teams ● Don't keep their managersDon't keep their managers • Failed scrumFailed scrum • 6 months later 1 less manager6 months later 1 less manager ● Management needs to go Agile tooManagement needs to go Agile too • Side Management of Senior managementSide Management of Senior management ● Don't try this on EOL teamsDon't try this on EOL teams
- 26. Fire your ArchitectsFireyour Architects ● If they haven't writtenIf they haven't written a line of code in thea line of code in the past 3 monthspast 3 months
- 27. Does your FinanceDepartment Know ?Does your Finance Department Know ?
- 28. The people incharge of software acquisition isThe people in charge of software acquisition is notnot your purchasing or legal team, it's youryour purchasing or legal team, it's your engineers.engineers. And they probably don't need a budget, or aAnd they probably don't need a budget, or a different onedifferent one
- 29. You Outsourced what?You Outsourced what ? ● SLASLA ● How can they take responsible ?How can they take responsible ? ● Who is going to point at who ?Who is going to point at who ?
- 30. ““Side Projects”Side Projects” ●Such asSuch as • Datacenter Migration , Network Upgrade,Datacenter Migration , Network Upgrade, Distribution UpgradeDistribution Upgrade ● Shared BacklogShared Backlog
- 31. ITIL : correctideas,ITIL : correct ideas, wrong placewrong place ● The last mileThe last mile ● The men who say noThe men who say no ● Guardians of ProductionGuardians of Production ● Friday at 10 amFriday at 10 am ●
- 32. Who has Securityas partWho has Security as part of their Job ?of their Job ?
- 33. Earlier in theprocessEarlier in the process ● Start as a teamStart as a team • Security Build inSecurity Build in • No upfront architectsNo upfront architects • No change managers afterwardsNo change managers afterwards ● Get Involved people from day0Get Involved people from day0 ● Prevent the OOPS …Prevent the OOPS … ●
- 34.
- 35. Automate all thethingsAutomate 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 ?
- 36. NirvanaNirvana An “ecosystem” thatsupports 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
- 37.
- 39. Culture,Culture, Automation,Automation, Measurement :Measurement : measureall the thingsmeasure all the things SharingSharing
- 40. Monitoring is usuallyanMonitoring is usually an aftertoughtaftertought ENOBUDGET, ENOTIMEENOBUDGET, ENOTIME
- 42. Self Service MetricsSelfService 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 ●
- 43.
- 44.
- 45. Visualize Business MetricsVisualizeBusiness Metrics ● $revenue$revenue ● #sales#sales ● signupssignups ● conversionsconversions ● Api callsApi calls ● Application useApplication use
- 46. ● Devoops isabout realizing your risk just becameDevoops is about realizing your risk just became a failure.a failure. ● Devops is about reducing risk earlier in theDevops is about reducing risk earlier in the process.process. Through Collaboration, Automation andThrough Collaboration, Automation and Better Monitoring and metricsBetter Monitoring and metrics
- 47. It's not aboutthe toolsIt's not about the tools It's about changeIt's about change It's about the peopleIt's about the people
- 48. ContactContact Kris BuytaertKris BuytaertKris.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