Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Devops: The continuing evolution of operations

Devops: The continuing evolution of operations

Keynote talk from Agile Portugal 2018. A trip through the history of how Devops became a think, what devops really is, and where it might be going.

Gareth Rushgrove

May 25, 2018
Tweet

More Decks by Gareth Rushgrove

Other Decks in Technology

Transcript

  1. Devops
    The continuing
    evolution of operations
    Gareth Rushgrove

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  17. Where did it come from?

    View full-size slide

  18. Operations as the new secret
    sauce (2006)

    View full-size slide

  19. Agile Infrastructure at Agile
    Toronto (2008)

    View full-size slide

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

    View full-size slide

  21. 10 deploys per day (2009)

    View full-size slide

  22. Devopsdays Ghent (2009)

    View full-size slide

  23. Devopsdays per year

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  26. Devops Enterprise Summit (2014)

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  30. Monitoring sucks/love (2011)

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  38. Coevolution of tools
    and practice

    View full-size slide

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

    View full-size slide

  40. 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)

    View full-size slide

  41. 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)

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  51. Microservices
    Would you start with one team
    building multiple services?

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  55. Devops next?

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  62. Recommended reading

    View full-size slide

  63. Just getting started

    View full-size slide

  64. Learning more

    View full-size slide

  65. Moving the industry forward

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide