Devops: The continuing evolution of operations

Slide 1

Slide 1 text

Devops The continuing evolution of operations Gareth Rushgrove

Slide 2

Slide 2 text

Gareth Rushgrove Product Manager at Docker Curator Devops Weekly Previously software engineer and occasional systems administrator

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

- What is Devops? - Where did it come from? - Devops then, now and next - Coevolution of tools and practice

Slide 5

Slide 5 text

What is Devops? (And why should I care?)

Slide 6

Slide 6 text

Agile; a reminder We are uncovering better ways of developing software by doing it and helping others do it. Agile Manifesto

Slide 7

Slide 7 text

What is software development? The process of conceiving, specifying, designing, programming, documenting, testing, and fixing involved in creating and maintaining software applications

Slide 8

Slide 8 text

A very broad problem domain There is a lot more to running services than just software development

Slide 9

Slide 9 text

What is operations? The sum of all of the skills, knowledge and values that your company has built up around the practice of shipping and maintaining quality systems Charity Majors

Slide 10

Slide 10 text

Anti-patterns Siloed teams Long cycle times Poor visibility Manual processes

Slide 11

Slide 11 text

Patterns Siloed teams Long cycle times Poor visibility Manual processes Cross-functional teams Short cycle times Fast feedback Automated processes

Slide 12

Slide 12 text

Team topologies anti-types Dev Ops Dev Ops Devops Devops Topologies, Matthew Skelton Anti-type A Dev and ops silos Anti-type B Devops team silo

Slide 13

Slide 13 text

Anti-type A Dev and ops silos Anti-type B Devops team silo Team topologies anti-types Dev Ops Dev Ops Devops Devops Topologies, Matthew Skelton

Slide 14

Slide 14 text

Team topologies Dev Ops Dev Ops Devops Devops Topologies, Matthew Skelton Type 1 Dev and ops collaboration Type 6 Devops evangelism team

Slide 15

Slide 15 text

Faster 30x more frequent deployments 200x faster lead times than their peers State of DevOps report 2015

Slide 16

Slide 16 text

Safer 60x change success rate 168x faster mean time to recovery State of DevOps report 2015

Slide 17

Slide 17 text

Devops is simply a banner Devops is... an umbrella concept that refers to anything that smoothes out the interaction between development and operations. Damon Edwards

Slide 18

Slide 18 text

Where did it come from?

Slide 19

Slide 19 text

Operations as the new secret sauce (2006)

Slide 20

Slide 20 text

Agile Infrastructure at Agile Toronto (2008)

Slide 21

Slide 21 text

Agile Systems Administration mailing list (2009) 2009 the year of Agile Sysadmins? Patrick Debois

Slide 22

Slide 22 text

10 deploys per day (2009)

Slide 23

Slide 23 text

Devopsdays Ghent (2009)

Slide 24

Slide 24 text

Devopsdays per year

Slide 25

Slide 25 text

What does devops mean to me? A cultural and professional movement Adam Jacobs (2010)

Slide 26

Slide 26 text

What does devops mean to me? Culture Automation Measurement Sharing John Willis + Damon Edwards (2010)

Slide 27

Slide 27 text

Devops Enterprise Summit (2014)

Slide 28

Slide 28 text

Really it’s all about Sharing Devops came out of mailing list conversations, early Twitter, blogging, small groups of passionate folks meeting in person and the explosion of technical conferences.

Slide 29

Slide 29 text

Devops then

Slide 30

Slide 30 text

Infrastructure as code - Applying software engineering practices to servers - Version control for operations - Configuration management - Unit testing for infrastructure

Slide 31

Slide 31 text

Automated deployment - Building trust in deploying software - Evolving concept of deployment pipeline - Continuous delivery and continuous deployment

Slide 32

Slide 32 text

Monitoring sucks/love (2011)

Slide 33

Slide 33 text

All still as relevant today Infrastructure as code, deployment and monitoring are foundational technical concepts to devops, even if the technologies and best practices are always changing

Slide 34

Slide 34 text

Devops now

Slide 35

Slide 35 text

Platforms - Industrialising automation best practices - Raising the level of abstraction - An API for operations

Slide 36

Slide 36 text

Site Reliability Engineering SRE embodies the philosophies of devops, but provides a prescriptive set of practices

Slide 37

Slide 37 text

Tenets of SRE - Ensure a durable focus on engineering - Maximise change velocity within a given error budget - Monitoring - Emergency response - Change management - Demand forecasting and capacity planning - Provisioning - Efficiency and performance

Slide 38

Slide 38 text

Observability - Monitoring - Alerting/visualization - Distributed systems tracing infrastructure - Log aggregation/analytics Four pillars of the Twitter Observability Engineering team

Slide 39

Slide 39 text

Serverless The server as we know it is dying [mic drop] Kevin Downs, New Relic

Slide 40

Slide 40 text

A new role for ops? - Automation - Cost optimisation - Disaster recovery - Monitoring - Security - Troubleshooting Kevin Downs, New Relic

Slide 41

Slide 41 text

Coevolution of tools and practice

Slide 42

Slide 42 text

Stumbling upon research Devop practitioners are constantly rediscovering and validating findings from applied psychology, management systems and other fields. Often without realising.

Slide 43

Slide 43 text

Hidden Cost of Team Cognition The need for coordination drives the need for communication amongst team members J. MacMillan, E. E. Entin, D. Serfaty (2004)

Slide 44

Slide 44 text

Hidden Cost of Team Cognition Reduction in communication overhead can be created in multiple ways, such as by restructuring the team to reduce the need for coordination… J. MacMillan, E. E. Entin, D. Serfaty (2004)

Slide 45

Slide 45 text

Hidden Cost of Team Cognition ...or by activities that increase mutual awareness and shared mental models amongst team members. J. MacMillan, E. E. Entin, D. Serfaty (2004)

Slide 46

Slide 46 text

Devops? Many successful devops practices emphasise building shared mental models across teams and disciplines, reducing the overhead of communication.

Slide 47

Slide 47 text

Sociotechnical systems Sociotechnical Systems suggest that all human systems include both a “technical system” and a “social system”

Slide 48

Slide 48 text

Sociotechnical systems It is possible for the system to optimize on the technology, giving priority to technical solutions and compelling the social system to adapt to it...

Slide 49

Slide 49 text

Sociotechnical systems … or to optimize on the social system, giving priority to existing social patterns and procedures and compelling the technology to fill in what gaps remain.

Slide 50

Slide 50 text

Sociotechnical systems Better outcomes are usually obtained by a reciprocal process of joint optimization, through which both the technical and social systems change to some degree in response to each other.

Slide 51

Slide 51 text

Devops? This is why devops doesn’t just talk about the tools, because in isolation that’s not the best way to change the status quo.

Slide 52

Slide 52 text

Microservices There are two essential strategies to manage [growing software]: a team can keep everything together (create a monolith) or a team can divide a project into smaller pieces (create microservices) Hunter Loftis, Heroku

Slide 53

Slide 53 text

Microservices There are two essential strategies to manage a growing team: keep everyone together or divide into smaller sub-teams Me, paraphrasing Hunter

Slide 54

Slide 54 text

Microservices Would you start with one team building multiple services?

Slide 55

Slide 55 text

Microservices Or start with identifying the domain model and splitting the team up around that model?

Slide 56

Slide 56 text

Cloud You build it, you run it. Werner Vogels, AWS CTO

Slide 57

Slide 57 text

Cloud Would you make different technology decisions if you’re on-call when things go wrong?

Slide 58

Slide 58 text

Devops next?

Slide 59

Slide 59 text

Service Management - We ignore too much of the past when embracing the new - Traditional ITSM still has areas to explore for devops - Asset management? - CMDB? - Contextual knowledge management? - And new domains in which to solve known problems - Configuration management for Serverless? - Multi-cloud service validation?

Slide 60

Slide 60 text

Support - Ops tools have evolved hugely over the last 10 years - Can we say the same thing about support tooling? - Too often devops practices applied only to deployment - Little crossover between those introducing devops and their colleagues in support - Shout-out to Jon Hall talking about Swarming

Slide 61

Slide 61 text

Operations machines What does operations mean when machine learning leads to more autonomous infrastructure?

Slide 62

Slide 62 text

A different banner? The need to share experiences of how we improve operations will exist beyond the banner of “devops”

Slide 63

Slide 63 text

Constant coevolution What new tools will unlock new ways of working?

Slide 64

Slide 64 text

Constant coevolution What new processes will be required to support new tools?

Slide 65

Slide 65 text

Slide 66

Slide 66 text

Just getting started

Slide 67

Slide 67 text

Learning more

Slide 68

Slide 68 text

Moving the industry forward

Slide 69

Slide 69 text

Conclusions

Slide 70

Slide 70 text

Avoid tribalism - Banners are useful catalysts for new topics - But to the practitioner, the word “devops” isn’t important - Neither is the word “agile” - Neither is the next word we band around

Slide 71

Slide 71 text

The importance of diversity - The first 3 devopsdays had 1 women speaker out of 30 - Devopsdays Minneapolis 2017 had 10 women speakers - Devops as a movement would not exist today without embracing diversity - Shout-out to Bridget Kromhout, Nicole Forsgren, Dominica DeGrandis, Jennifer Davis, Mandi Walls, Sarah Wells, Cindy Sridharan, Julia Evans, Robyn Bergeron and many more

Slide 72

Slide 72 text

Always ask “How do we run this?” What devops means to me is to constantly be asking “how do we run this?” and strive to improve the answer to that question over time

Slide 73

Slide 73 text

Thank you