Slides for the #digantcafe meetup at Digipolis , September 2015

1. Devops 101Devops 101
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

3. What's this Devops thing really about ?What's this Devops thing really about ?

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
5th aniversary last year in Gent5th aniversary last year in Gent
........

5. Devops , a definitionDevops , a definition
● 25-40 year old25-40 year old
● Experienced linux engineerExperienced linux engineer
● Knows how to write codeKnows how to write code
● Sits between the developers and operationsSits between the developers and operations
engineersengineers
● Drinks BeerDrinks Beer
● Eats SushiEats Sushi
● Lives in Belgium or the UKLives in Belgium or the UK

6. Devops is notDevops is not
● A new roleA new role
● A new job descriptionA new job description
● A new teamA new team
● A new functionA new function
● NewNew

7. devops, a definition:devops, a definition:

8. ● 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.

9. 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

10. ““DevOps is a cultural andDevOps is a cultural and
professional movement”professional movement”
Adam JacobAdam Jacob

11. #devops=~C(L)AMS#devops=~C(L)AMS
● CultureCulture
● (Lean)(Lean)
● AutomationAutomation
● Monitoring and MeasurementMonitoring and Measurement
● SharingSharing
Damon Edwards and John WillisDamon Edwards and John Willis
Gene KimGene Kim

12. Why #devops ?Why #devops ?

13. Devs vs OpsDevs vs Ops

14. HistoricallyDifferent GoalsHistoricallyDifferent 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

15. 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,ops,managers,investors}{customers,developers,ops,managers,investors}

16. Why do you want ?Why do you want ?
● Broken culture #needsfixingBroken culture #needsfixing
● Business pressure,Business pressure,
•
SlowSlow
•
Low quality releasesLow quality releases
● Unmanageable infrastructureUnmanageable infrastructure
● Too fast growthToo fast growth

17. Culture,Culture,
automation,automation,
Measturement,Measturement,
sharingsharing

18. 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%

19. Your goals ?Your goals ?
● Have you even set goals ?Have you even set goals ?
● CD vs CD ?CD vs CD ?
● Is your infra in place ?Is your infra in place ?
● Is your team ready ?Is your team ready ?

20. Analyze ThisAnalyze This
● What are devs nagging aboutWhat are devs nagging about
•
Slow builds ?Slow builds ?
•
No enviroments ?No enviroments ?
● What are ops nagging aboutWhat are ops nagging about
•
Bad artefacts ?Bad artefacts ?
•
No logs ?No logs ?
● What is mgmt nagging aboutWhat is mgmt nagging about
•
Quality / Feedback ?Quality / Feedback ?

21. SpoilerSpoiler
Your real problem is most probably not technicalYour real problem is most probably not technical

22. Are you speaking the sameAre you speaking the same
language ?language ?
● Configuration management vs configurationConfiguration management vs configuration
managementmanagement
● What is Operations ?What is Operations ?
● What is #devops ?What is #devops ?

23. A reaction to ?A reaction to ?
● ITILITIL
•
For imposing irrelevant proceduresFor imposing irrelevant procedures
•
And Blocking innovationAnd Blocking innovation
● AgileAgile
•
For not including operations in the discussionFor not including operations in the discussion

24. Agile ?Agile ?
● WaterfallWaterfall
● WatermillWatermill
● ScrumScrum
● KanbanKanban
● SAFESAFE

25. HowtoHowto

26. Do not call it aDo not call it a
#devopsteam#devopsteam
● It's not a job title.It's not a job title.
● Ops isn't actually opsOps isn't actually ops
● It's not the team in charge of deliveryIt's not the team in charge of delivery
● Yet another silo between devs and opsYet another silo between devs and ops

27. 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

28. Devops is a “reorg”Devops is a “reorg”

29. Shared BacklogShared Backlog
● CHALLENGE : Getting Non FunctionalCHALLENGE : Getting Non Functional
Requirements in the development backlogRequirements in the development backlog
•
On team levelOn team level
•
On management levelOn management level
•
On business user levelOn business user level
● Put the Product Owner on CallPut the Product Owner on Call

30. Enable CommunicationEnable Communication

31. Start “Hiring”Start “Hiring”
● Internally / ExternallyInternally / Externally
● Get experience on boardGet experience on board
● Get BuyIn inside the teamGet BuyIn inside the team
● Don't hesitate to also Fire !Don't hesitate to also Fire !

32. Build TrustBuild Trust
● ExperimentExperiment
•
DevDev
•
TestTest
● ProdProd
● Automate all theAutomate all the
thingsthings
● Measure successMeasure success
● Measure FailureMeasure Failure

33. With great power ...With great power ...
Your code will go to production..Your code will go to production..
You will be able to fix it ..You will be able to fix it ..
You will have access to the logsYou will have access to the logs
Access to the metrics...Access to the metrics...

35. Your machines as CattleYour machines as Cattle

36. Treat your people as petsTreat your people as pets

37. Stop playing theatreStop playing theatre
● Security TheatreSecurity Theatre
● Procedure TheatreProcedure Theatre

38. BondBond
● Internal DevopsdaysInternal Devopsdays
● Internal Open Source DaysInternal Open Source Days
● 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

39. Myths ?Myths ?
● You can only change small orgsYou can only change small orgs
● You can't change a large organisationYou can't change a large organisation
It dependsIt depends

40. It's about the tools !It's about the tools !
•
The wrong tools will block youThe wrong tools will block you
•
The right tools will enhance your cultureThe right tools will enhance your culture
● It's not about the toolsIt's not about the tools

41. Culture,Culture,
Automation,Automation,
Measurement,Measurement,
SharingSharing

42. 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 ?

43. Automation supports responsabilityAutomation supports responsability
● Version all the thingsVersion all the things
•
git blamegit blame
•
don't blamedon't blame
•
Failure is an optionFailure is an option
● No manual changesNo manual changes
•
Enforce fast automated pipelinesEnforce fast automated pipelines
•
Manuall changes will be automaticallyManuall changes will be automatically
revertedreverted

44. Automate all the thingsAutomate all the things
● Host ProvisioningHost Provisioning
● DB deploymentDB deployment
● Application Server deploymentApplication Server deployment
● UsersUsers
● BackupsBackups
● Application DeploymentApplication Deployment
● Firewall changesFirewall changes
● Loadbalancer configLoadbalancer config

45. Idempodent InfrastructureIdempodent Infrastructure
● Configuration management ensures stateConfiguration management ensures state
● Periodically,Periodically,
● ConstantlyConstantly
● Manual changes are revertedManual changes are reverted

46. devops (<)> continuous delilverydevops (<)> continuous delilvery

48. 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

49. Delivery vs DeploymentDelivery vs Deployment
● Test MaturityTest Maturity
•
Are you comfortable with your testAre you comfortable with your test
coverage ?coverage ?
● Development MaturityDevelopment Maturity
•
Feature FlagsFeature Flags
•
Deployed code <> Enabled FeatureDeployed code <> Enabled Feature

50. " 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/

51. What about Legacy ?What about Legacy ?
● Ignore itIgnore it
● Refactor it (Estonia !)Refactor it (Estonia !)
● Why do you call it legacy ?Why do you call it legacy ?
● Technical DebtTechnical Debt
● Pay back with InterrestPay back with Interrest

52. Culture,Culture,
Automation,Automation,
Measurement :Measurement :
measure all the thingsmeasure all the things
SharingSharing

54. #monitoringlove#monitoringlove
•
•
Ulf Mansson #devopsdays Rome 2011Ulf Mansson #devopsdays Rome 2011
•
A new era of toolingA new era of tooling
•
#monitoringlove hacksessions @inuits#monitoringlove hacksessions @inuits
•
#monitorama#monitorama

55. Automation ofAutomation of
#monitoring#monitoring
brought backbrought back
thethe #love#love

56. Monitoring++Monitoring++
•
Learn from LogsLearn from Logs
•
Measure all the ThingsMeasure all the Things
•
Lean from your dataLean from your data
•
Predictive analysisPredictive analysis
•

57. Culture,Culture,
Automation,Automation,
Measurement,Measurement,
SharingSharing

58. DashboardsDashboards

59. Visualize Business MetricsVisualize Business Metrics
● $revenue$revenue
● #sales#sales
● signupssignups
● conversionsconversions
● Api callsApi calls
● Application useApplication use

60. Share ResponsabilityShare Responsability
● Devs OnCallDevs OnCall
● Product Owners OnCallProduct Owners OnCall
● You build it , you run it. (Werner Vogels)You build it , you run it. (Werner Vogels)

61. SharingSharing
● Open SpaceOpen Space
● Open SourceOpen Source
● GithubGithub
● Talk about ExperiencesTalk about Experiences
● Publish the codePublish the code

62. FoodFood

64. Devops is like securityDevops is like security
It's not a product that you can buyIt's not a product that you can buy
It's a lifestyleIt's a lifestyle
It's a continuous improvement processIt's a continuous improvement process

65. ContactContact
Kris Buytaert kris. buytaert@inuits.euKris Buytaert kris. buytaert@inuits.eu
Further ReadingFurther Reading
@krisbuytaert@krisbuytaert
http://www.krisbuytaert.be/blog/http://www.krisbuytaert.be/blog/
http://www.inuits.eu/http://www.inuits.eu/
InuitsInuits
Heidestraat 257Heidestraat 257
2070 Zwijndrecht2070 Zwijndrecht
BelgiumBelgium
891.514.231891.514.231
+32 475 961221+32 475 961221