Transcription
DevOps: A HistoryNell Shamrell-Harrington@nellshamrellGeekWire CloudTech Summit
Who Am I?Nell Shamrell-HarringtonSr. Software Engineer at ChefCore maintainer of Habitat and Supermarket open source projectsCo-host of Food Fight podcastnshamrell@chef.io@nellshamrell
Why a talk aboutthe history of DevOps?
Doesn’t everybodyalready know this?
No
As DevOps has spreadthroughout the industry
DevOps has becomeovermarketedand hyped
Context has been lost
Context is crucial forboth understanding andapplying DevOps
Buzzwords!!!
Source: upgrad.com
Source: blog.modulus.io
Where is the signalin the noise?
To go forward,you must go back- Game of Thrones
The purpose of this talk is tohighlight the origin andcontext of these buzzwords
How to they are torelevant to us nowand into the future
Let’s start with a meta-buzzword!
Meta-buzzword:Scale
Meta-buzzword: Scale18th Century:Craft ProductionSource: “The Machine that Changed the World” by Womack, Jones, and Roos
Meta-buzzword: Scale1785: Honore Blancintroducesinterchangeablegun partsSource: “Implementing Lean Software Development” by Poppendieck
Meta-buzzword: Scale1908: Henry Fordproduces the Model TSource: “The Machine that Changed the World” by Womack, Jones, and Roos
Meta-buzzword: ScaleInterchangeable parts,interchangeable workersSource: “The Machine that Changed the World” by Womack, Jones, and Roos
Meta-buzzword: Scale“Standardization in itstrue sense is the unionof all the best points ofcommodities with the bestpoints of production ”- Henry FordSource: “Today And Tomorrow” by Henry Ford
Meta-buzzword: Scale“ to the end that the best commoditymay be producedin sufficient quantity and atthe least cost to the consumer”- Henry FordSource: “Today And Tomorrow” by Henry Ford
Meta-buzzword: Scale“Many people thought thatmachine production woulddestroy craftsmanship ”- Henry FordSource: “Today And Tomorrow” by Henry Ford
Meta-buzzword: Scale“Exactly the reverse has comeabout; we now need moreexpert machinists than wehave ever needed”- Henry FordSource: “Today And Tomorrow” by Henry Ford
Sound familiar?
Meta-buzzword: Scale“Each of the high performershad server/sysadmin ratiosgreater than 100:1 ”Source: “The Visible Ops Handbook” by Behr, Kim, and Spafford
Meta-buzzword: Scale“In contrast, analysts report thataverage server/sysadmin ratiosis between 15:1 and 25:1”Source: “The Visible Ops Handbook” by Behr, Kim, and Spafford
Back to the past!
Meta-buzzword: ScaleFord Mass ProductionSystem designed forhuge quantitiesof limited modelsSource: “The Toyota Way” by Jeffrey K. Liker
Meta-buzzword: Scale“Any customer can have acar painted any colorthat he wantsas long as it is black”- Henry FordSource: “My Life and Work” by Henry Ford
Meta-buzzword:Lean
Meta-buzzword: LeanLean was originallyused to characterizethe Japanese approachto automobile manufacturingSource: “Implementing Lean Software Development” by Poppendieck
Meta-buzzword: Lean1926: Toyoda AutomationLoom WorksSource: “The Toyota Way” by Jeffrey K. Liker
Buzzword:Jidoka
Buzzword: JidokaAutomation with ahuman touchSource: “The Toyota Way” by Jeffrey K. Liker
Sound familiar?
Buzzword: Jidoka“ ask yourself, does this alertrequire any immediateintervention? Alertsshould be actionable.”- Patrick DeboisSource: “Web Operations” by John Allspaw and Jesse Robbins
Buzzword: Jidoka“If an alert can be ignored ordoesn’t require humanintervention, the alert is awaste of energy”- Patrick DeboisSource: “Web Operations” by John Allspaw and Jesse Robbins
Back to the past!
Meta-buzzword: Lean1930’s: Toyotapivots from loomsto automobilesSource: “The Machine that Changed the World” by Womack, Jones, and Roos
Meta-buzzword: Lean1940’s: World War IISource: “The Toyota Way” by Jeffrey K. Liker
Meta-buzzword: LeanToyota Production SystemSource: “The Toyota Way” by Jeffrey K. Liker
Meta-buzzword: Lean“Flexibility requiredmarshaling theingenuity of workersto continuouslyimprove processes”Source: “The Toyota Way” by Jeffrey K. Liker
Buzzword:Kaizen
Buzzword: KaizenContinuous ImprovementSource: “The Toyota Way” by Jeffrey K. Liker
Buzzword:Kanban
Buzzword: KanbanKanban “pulls” from theprevious stepSource: “The Toyota Way” by Jeffrey K. Liker
Buzzword:Just In Time
Buzzword: Just In Time“ only what is needed,when it is needed, andin the amount needed”Source: “Just-in-Time” toyota-global.com
Sound familiar?
Buzzword: Just In Time“WIP in the silent killer”Source: “The Phoenix Project” by Kim, Behr, and Spafford
Buzzword: Just In Time“If no one has slack time, WIPjust gets stuck in the system.”Source: “The Phoenix Project” by Kim, Behr, and Spafford
Back to the past!
Meta-buzzword: LeanToyota revolutionizedmanufacturing throughlean productionSource: “The Toyota Way” by Jeffrey K. Liker
Meta-buzzword: Lean1970’s - 90’s:Software Engineeringrises to prominenceSource: “To Agility and Beyond” by Peter Varyhol
Buzzword:Waterfall
Buzzword: Waterfall1985: U.S. Department ofDefense adoptssoftware processSource: DOD-STD-2167
Buzzword: Waterfall1. Software requirements analysisSource: DOD-STD-2167
Buzzword: Waterfall1. Software requirements analysis2. Preliminary designSource: DOD-STD-2167
Buzzword: Waterfall1. Software requirements analysis2. Preliminary design3. Detailed designSource: DOD-STD-2167
Buzzword: Waterfall1.2.3.4.Software requirements analysisPreliminary designDetailed designCoding and unit testingSource: DOD-STD-2167
Buzzword: Waterfall1.2.3.4.5.Software requirements analysisPreliminary designDetailed designCoding and unit testingComputer Software Component(CSC) integration and testingSource: DOD-STD-2167
Buzzword: Waterfall1.2.3.4.5.Software requirements analysisPreliminary designDetailed designCoding and unit testingComputer Software Component(CSC) integration and testing6. Computer Software Component Interface(CSCI) testingSource: DOD-STD-2167
Buzzword:SCRUM
Buzzword: SCRUM1995: Sutherland andSchwaber present“The Scrum DevelopmentProcess”Source: “Scrum Development Process” by Ken Schwaber
Buzzword: SCRUM“The development process isregarded as unpredictableat the onset ”- Ken SchwaberSource: “Scrum Development Process” by Ken Schwaber
Buzzword: SCRUM“ and control mechanisms areput in place to manage theunpredictability”- Ken SchwaberSource: “Scrum Development Process” by Ken Schwaber
Buzzword: SCRUM“Scrum also defined time-boxediterative development cycleswhose goal was to deliverworking software”- Peter VaryholSource: “To Agility and Beyond” by Peter Varyhol
Buzzword:Agile
Buzzword: Agile1996: Extreme Programmingproject startedSource: extremeprogramming.org
Buzzword: Agile2000: Extreme Programmingleaders meet in ORSource: “Writing the Agile Manifesto” by Martin Fowler
Buzzword: Agile2001: Agile Manifesto WrittenSource: “Writing the Agile Manifesto” by Martin Fowler
Buzzword: Agile“Our highest priority is tosatisfy the customer throughearly and continuous deliveryof valuable software”Source: agilemanifesto.org/principles.html
Buzzword: Agile“Welcome changingrequirements, even late indevelopment. Agile processesharness change for thecustomer’s competitive advantage”Source: agilemanifesto.org/principles.html
Buzzword: Agile“Working software is theprimary measure of progress”Source: agilemanifesto.org/principles.html
Buzzword:DevOps
Buzzword: DevOps2007:Patrick Debois isworking in IT - has tostraddle the connectionbetween dev and opsSource: “The History of Devops” by Damon Edwards
Buzzword: DevOps2008:Patrick Debois presents“Agile Operation andInfrastructure: HowInfra-Agile Are You?”Source: “A Short History of DevOps” by Richard Rapaport
Buzzword: DevOps“Development and Infrastructurewould work in isolation and wouldintegrate just before the politicaldeadline There was no timeleft to fix things”Source: “Agile Operations and Infrastructure” by Patrick Debois
Buzzword: DevOps“Every sprint you would have a newworking release and it wouldconstantly improve.”Source: “Agile Operations and Infrastructure” by Patrick Debois
Buzzword: DevOps“The application went live Every release they would improveboth the software and the infrastructure”Source: “Agile Operations and Infrastructure” by Patrick Debois
Buzzword: DevOps Layers of Agile InfrastructureSource: “Agile Operations and Infrastructure” by Patrick Debois
Buzzword: DevOps Layers of Agile InfrastructureTechnicalSource: “Agile Operations and Infrastructure” by Patrick Debois
Buzzword: DevOps Layers of Agile InfrastructureTechnicalProjectSource: “Agile Operations and Infrastructure” by Patrick Debois
Buzzword: DevOps Layers of Agile InfrastructureTechnicalProjectOperationsSource: “Agile Operations and Infrastructure” by Patrick Debois
Buzzword: DevOps2009:John Allspaw andPaul Hammond present“10 Deploys per Day,Dev and Ops Cooperationat Flickr”Source: “A Short History of DevOps” by Richard Rapaport
Buzzword: DevOpsOps: “It’s not my machines,it’s your code!”Source: “10 Deploys per Day ” by John Allspaw and Paul Hammond
Buzzword: DevOpsOps: “It’s not my machines,it’s your code!”Dev: “It’s not my code, it’syour machines!”Source: “10 Deploys per Day ” by John Allspaw and Paul Hammond
Buzzword: DevOpsOps and Dev havethe same jobSource: “10 Deploys per Day ” by John Allspaw and Paul Hammond
Buzzword: DevOpsOps and Dev havethe same jobEnable the businessto functionSource: “10 Deploys per Day ” by John Allspaw and Paul Hammond
Buzzword: DevOpsAll businessesrequire changeSource: “10 Deploys per Day ” by John Allspaw and Paul Hammond
Buzzword: DevOpsAll businessesrequire changeChange involves riskSource: “10 Deploys per Day ” by John Allspaw and Paul Hammond
Buzzword: DevOpsDev and Ops mustown this risk throughculture and toolsSource: “10 Deploys per Day ” by John Allspaw and Paul Hammond
Buzzword: DevOps“Tools will not help youif you install them andstill have an argumentativeculture going on”Source: “10 Deploys per Day ” by John Allspaw and Paul Hammond
Buzzword: DevOps2009:First DevOpsDaysheld in Ghent, BelgiumSource: “A Short History of DevOps” by Richard Rapaport
Buzzword: DevOps2010:First DevOpsDaysheld in USASource: “A Short History of DevOps” by Richard Rapaport
Buzzword: DevOps2010:#devops takes off on TwitterSource: “A Short History of DevOps” by Richard Rapaport
Buzzword: DevOps2017:So much DevOps!
Buzzwordscome and go
The ideals of producingthe best product
In the most humaneand engaging wayfor employees
Have stayed the same
The implementationsof the ideals have evolved
And will continue to evolve
They must continueto be nurtured andcultivated
In businessand beyond
History carried thetorch this far
Now it’s your turn
Carry the ideals onward
Thank you
Who Am I?Nell Shamrell-HarringtonSr. Software Engineer at ChefCore maintainer of Habitat and Supermarket open source projectsCo-host of Food Fight podcastnshamrell@chef.io@nellshamrellAny Questions?
Source: “The Visible Ops Handbook” by Behr, Kim, and Spafford “In contrast, analysts report that average server/sysadmin ratios is between 15:1 and 25:1 ” Meta-buzzword: Scale Source: “The Visible Ops Handbook” by Behr, Kim, and Spafford. Back to the past! Ford Mass Production System designed for huge quantities of limited models Meta-buzzword: Scale Source: “The Toyota Way” by .
