48
From devoops, to devops ING Loves IT April 2017 ,Bucharest Kris Buytaert @krisbuytaert

From devoops to devops

Embed Size (px)

Citation preview

Page 1: From devoops to devops

From devoops, to devopsING Loves IT

April 2017 ,Bucharest Kris Buytaert

@krisbuytaert

Page 2: From devoops to devops

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 Source Chief 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, ….

Page 3: From devoops to devops

What's this devops What's this devops thing anyhow ? thing anyhow ?

Page 4: From devoops to devops
Page 5: From devoops to devops
Page 6: From devoops to devops

C(L)AMSC(L)AMS● CultureCulture

● (Lean)(Lean)

● AutomationAutomation

● MeasurementMeasurement

● SharingSharing

Damon Edwards and John WillisDamon Edwards and John Willis

Gene KimGene Kim

Page 7: From devoops to devops

Culture,Culture,automation, automation,

Measturement,Measturement,

sharingsharing

Page 8: From devoops to devops

Historical Organisations 101Historical Organisations 101

Page 9: From devoops to devops

The walls of ConfusionThe walls of Confusion

Page 10: From devoops to devops

Opposing GoalsOpposing GoalsDevelopmentDevelopment

● 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

Page 11: From devoops to devops

Traditional OrganisationTraditional Organisation● BureacracyBureacracy

● RulesRules

● TraditionsTraditions

● Lack of FreedomLack of Freedom

● Lots of Managers Lots of Managers

● Exodus of EngineersExodus of Engineers

Page 12: From devoops to devops

Careers in TechCareers in 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, not Tech folks are forced into management, not supported to grow technicalysupported to grow technicaly

• ““Architects”Architects”

Page 13: From devoops to devops

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 ?

Page 14: From devoops to devops

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 ?

Page 15: From devoops to devops

Adopting a Devops:Adopting a Devops:• MindsetMindset• LifestyleLifestyle• VisionVision

Page 16: From devoops to devops

SpoilerSpoiler

Your real problem is most probably not technicalYour real problem is most probably not technical

Page 17: From devoops to devops

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%

Page 18: From devoops to devops

Wild project plans ! Wild project plans ! Can you make your change journey a traditional Can you make your change journey a traditional project with milestones and project with milestones and

• We are a new org We 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

Page 19: From devoops to devops

Do not call it a Do 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

Page 20: From devoops to devops

Do not call them Do 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 ?

Page 21: From devoops to devops

Crossfunctional TeamCrossfunctional Team● Build a project team with skills from all overBuild a project team with skills from all over

• DevelopmentDevelopment

• Continuous Integration Continuous Integration

• TestingTesting

• Infrastructure (HA/ Scale/ Performance)Infrastructure (HA/ Scale/ Performance)

• DeploymentDeployment

• MeasurementMeasurement

● Seat them together !Seat them together !

Page 22: From devoops to devops

Agile ?Agile ?● Waterfall Waterfall

● Watermill Watermill

● SAFESAFE

● ScrumScrum

● KanbanKanban

Page 23: From devoops to devops

Is your organisation agile, Is your organisation agile,

or just your silo ?or just your silo ?

Page 24: From devoops to devops

The BusinesThe Busines● Doesn't care how we Doesn't care how we

run ITrun IT

● Can't adapt their Can't adapt their processesprocesses

● Isn't involved in Isn't involved in building softwarebuilding software

● Doesnt survive if we Doesnt survive if we don't deliverdon't deliver

● Is waiting for their Is waiting for their featuresfeatures

● Is based on softwareIs based on software

Page 25: From devoops to devops

Pitfalls Merging TeamsPitfalls Merging 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 teams Don't try this on EOL teams

Page 26: From devoops to devops

Fire your ArchitectsFire your Architects

● If they haven't written If they haven't written a line of code in the a line of code in the past 3 monthspast 3 months

Page 27: From devoops to devops

Does your Finance Department Know ?Does your Finance Department Know ?

Page 28: From devoops to devops

The people in charge of software acquisition is The people in charge of software acquisition is notnot your purchasing or legal team, it's your your purchasing or legal team, it's your engineers.engineers.

And they probably don't need a budget, or a And they probably don't need a budget, or a different onedifferent one

Page 29: From devoops to devops

You Outsourced what ?You Outsourced what ?

● SLA SLA

● How can they take responsible ?How can they take responsible ?

● Who is going to point at who ? Who is going to point at who ?

Page 30: From devoops to devops

““Side Projects”Side Projects”● Such asSuch as

• Datacenter Migration , Network Upgrade, Datacenter Migration , Network Upgrade, Distribution UpgradeDistribution Upgrade

● Shared BacklogShared Backlog

Page 31: From devoops to devops

ITIL : correct ideas, ITIL : correct ideas, wrong placewrong place

● The last mileThe last mile

● The men who say no The men who say no

● Guardians of Production Guardians of Production

● Friday at 10 amFriday at 10 am

Page 32: From devoops to devops

Who has Security as part Who has Security as part of their Job ?of their Job ?

Page 33: From devoops to devops

Earlier in the processEarlier 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 …

Page 34: From devoops to devops

Culture, Culture,

Automation,Automation,Measurement,Measurement,

SharingSharing

Page 35: From devoops to devops

Automate all the thingsAutomate all the things● BuildBuild

• reproducable builds are undiscussablereproducable builds are undiscussable

● TestTest

• testing reduces risk testing reduces risk

• automate deployments of your test infra automate deployments of your test infra

● DeployDeploy

• Infrastructure as CodeInfrastructure as Code

• 100% automation 100% automation

• Can you rebuild your infrastructure ?Can you rebuild your infrastructure ?

Page 36: From devoops to devops

NirvanaNirvanaAn “ecosystem” that supports continuous delivery, from An “ecosystem” that supports continuous delivery, from infrastructure, data and configuration management to infrastructure, data and configuration management to business.business.

Through automation of the build, deployment, and testing Through 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 changes testers, and operations, delivery teams can get changes released in a matter of hours — sometimes even minutes–no released in a matter of hours — sometimes even minutes–no matter what the size of a project or the complexity of its code matter what the size of a project or the complexity of its code base.base.

Continuous Delivery , Jez HumbleContinuous Delivery , Jez Humble

Page 37: From devoops to devops

Jenkins Pipeline Jenkins Pipeline

Page 38: From devoops to devops
Page 39: From devoops to devops

Culture, Culture,

Automation,Automation,

Measurement :Measurement :

measure all the thingsmeasure all the thingsSharingSharing

Page 40: From devoops to devops

Monitoring is usually an Monitoring is usually an aftertoughtaftertought

ENOBUDGET, ENOTIMEENOBUDGET, ENOTIME

Page 41: From devoops to devops
Page 42: From devoops to devops

Self Service MetricsSelf Service Metrics

● Being able to add new metrics Being 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

Page 43: From devoops to devops

Culture, Culture,

Automation, Automation,

Measurement,Measurement,

SharingSharing

Page 44: From devoops to devops

DashboardsDashboards

Page 45: From devoops to devops

Visualize Business MetricsVisualize Business Metrics● $revenue$revenue

● #sales#sales

● signups signups

● conversionsconversions

● Api callsApi calls

● Application useApplication use

Page 46: From devoops to devops

● Devoops is about realizing your risk just became Devoops is about realizing your risk just became a failure.a failure.

● Devops is about reducing risk earlier in the Devops is about reducing risk earlier in the process.process.

Through Collaboration, Automation and Through Collaboration, Automation and Better Monitoring and metricsBetter Monitoring and metrics

Page 47: From devoops to devops

It's not about the tools It's not about the tools

It's about change It's about change

It's about the people It's about the people

Page 48: From devoops to devops

ContactContactKris Buytaert Kris Buytaert [email protected]@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 31BrasschaatBrasschaatBelgiumBelgium891.514.231891.514.231

+32 475 961221+32 475 961221