As presented at Baltic Devops in Talllinn ,
Starting with devops is either the most trivial, or the hardest thing to do.
This talk will teach you a number of tricks on how to make life easier for your team. How to work together with your management and how to convince them devops is a relevant thing
Human Factors of XR: Using Human Factors to Design XR Systems
Adopting Devops , Stories from the trenches
1. Growing a devops cultureGrowing a devops culture
Stories from the TrenchesStories from the Trenches
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
........
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 on leadershipmust awaken to the challenge, must learn their responsibilities, and take on leadership
for change.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 machines andInstitute leadership The aim of supervision should be to help people and machines and
gadgets do a better job.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 adversarial relationships,and new levels of productivity. Such exhortations only create adversarial relationships,
as the bulk of the causes of low quality and low productivity belong to the system andas 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.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 to prideRemove barriers that rob people in management and in engineering of their right to pride
of workmanship.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.
10. 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
11. 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}
12. Who wants devops ?Who wants devops ?
● Grassroot, engineersGrassroot, engineers
•
Because they feel the pain and want toBecause they feel the pain and want to
improveimprove
● C-level managementC-level management
● VendorsVendors
13. Who wants devops ?Who wants devops ?
● Grassroot, engineersGrassroot, engineers
● C-level managementC-level management
•
Because they see the problems and need toBecause they see the problems and need to
improveimprove
● VendorsVendors
15. Who wants devops ?Who wants devops ?
● Grassroot, engineersGrassroot, engineers
● C-level managementC-level management
● Traditional VendorsTraditional Vendors
•
Because they want sell same old stuff with aBecause they want sell same old stuff with a
new tag, that won't help you.new tag, that won't help you.
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. 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%
18. 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 ?
19. 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 ?
23. 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
24. 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
27. 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 !
28. Build TrustBuild Trust
● ExperimentExperiment
•
DevDev
•
TestTest
● ProdProd
● Automate all theAutomate all the
thingsthings
● Measure successMeasure success
● Measure FailureMeasure Failure
31. Stop playing theatreStop playing theatre
● Security TheatreSecurity Theatre
● Procedure TheatreProcedure Theatre
32. 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
33. 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
34. 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
37. 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
38. " 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 easy deploymentthe time), having a reliable and easy deployment
should beshould 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/
43. Visualize Business MetricsVisualize Business Metrics
● $revenue$revenue
● #sales#sales
● signupssignups
● conversionsconversions
● Api callsApi calls
● Application useApplication use
44. SharingSharing
● Open SpaceOpen Space
● Open SourceOpen Source
● GithubGithub
● Talk about ExperiencesTalk about Experiences
● Publish the codePublish the code
47. 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