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

Puppet and Devops for Automation

Puppet and Devops for Automation

What do the results of the 2015 Devops Report mean for organizations trying to transform their IT to adapt to the changing landscape? How can Puppet help?

Eric Sorenson

February 10, 2016
Tweet

More Decks by Eric Sorenson

Other Decks in Technology

Transcript

  1. DevOps & 

    Puppet for Automation
    Eric Sorenson - Sr Technical Product Manager
    Twitter: @ahpook
    Slides by Alanna Brown - @alannapb
    #DigTC2016

    View Slide

  2. One notable difference this year
    was an increase in DevOps
    departments. This year, 19 percent
    of respondents were part of a DevOps
    department, up from 16 percent
    last year.
    This year, 4,976 respondents completed the 2015 State of DevOps Survey. Compared to last year, we saw similar
    distributions across geographies, company size, industries and size of infrastructure.
    See page 29 for more about women in tech.
    Company Size
    Industries
    Gender
    Geography
    Size of Infrastructure
    by Number of Servers
    Departments
    Puppet Labs 2015 State of DevOps Report | In partnership with IT Revolution | Sponsored by PwC 7

    View Slide

  3. View Slide

  4. People don’t buy what you do,
    they buy why you do it.
    Simon Sinek
    http://bit.ly/sinektedtalk

    View Slide

  5. Conflicting Incentives
    Business Delivering value to customers
    Dev teams Delivering new features
    Ops teams Ensuring stability of systems
    Quality teams Ensuring quality of software releases

    View Slide

  6. Aligned Incentives
    Why you exist as a business
    Business
    Ops
    teams
    Quality
    teams
    Dev
    teams

    View Slide

  7. Reliability
    Agility
    Opposing Forces

    View Slide

  8. High-performing IT orgs are more agile
    30x
    More frequent
    deployments
    200x
    Faster lead times than
    their peers
    Source: Puppet Labs 2015 State of DevOps Report

    View Slide

  9. High-performing IT orgs are more reliable
    60x
    Change success
    rate
    168x
    Faster mean time to
    recover (MTTR)
    Source: Puppet Labs 2015 State of DevOps Report

    View Slide

  10. High-performing IT orgs are winning
    1.5x
    More likely to exceed
    profitability, market
    share & productivity
    goals
    50%
    Higher market
    capitalization growth
    over 3 years.*
    Source: Puppet Labs 2015 State of DevOps Report

    View Slide

  11. Learning is not compulsory,
    but neither is survival.
    W Edwards Deming
    http://bit.ly/deming14pts

    View Slide

  12. Identify the
    Desired State

    View Slide

  13. Organization
    Low trust culture ! High trust culture
    Siloed teams ! Cross-functional teams
    Lack of alignment ! Aligned around
    business goals

    View Slide

  14. Processes
    Lots of manual work ! Mostly automated work
    Long cycle times ! Short cycle times
    Poor visibility ! Fast feedback & insight

    View Slide

  15. People
    High burnout ! High job satisfaction
    Monoculture ! Diversity of people and
    ideas
    Checking boxes ! Creative innovation

    View Slide

  16. “Trying to effect process, people, technology and
    cultural changes across the entire application
    portfolio, in a globally dispersed team and with a lot of
    associated technical debt, is an epic challenge.”
    Jonathan Fletcher
    Enterprise Architect and Lead for Technology,
    Platform and DevOps at Hiscox
    http://bit.ly/devopshiscox

    View Slide

  17. Hiscox: Results
    • Reduced cost per release on one application
    by 97%
    • Reduced time per release by 89%
    • Reduced staff required to release by 75%
    • Automated testing reduced multiple man days
    of effort down to an overnight hands-free
    process

    View Slide

  18. Team Structure Matters

    View Slide

  19. Typical Enterprise Org Structure
    IT Operations
    NOC
    Commercial Banking
    Business Units
    Credit Cards
    Mortgages
    Investment Banking
    Systems Engineers
    Network Engineers
    Storage Admins
    DBAs
    Infosec
    Dev teams reside in BU

    View Slide

  20. Roles & Responsibilities
    Roles Responsibilities
    “The Business” Understand market trends and identify customer needs
    IT Manager Build trust with counterparts on other teams; create culture of learning
    and continuous improvement; delegate authority; remove roadblocks
    Dev Manager Build trust with Ops counterpart; bring Ops into the planning process
    early
    Systems Engineer Automate the things that are painful; help devs get feedback
    QE Provide input into scale and performance; provide feedback on staging
    environments
    Devs Plan for deployment as you’re planning new features; get feedback from
    ops and work with them on deployment process

    View Slide

  21. Pattern 1: Smooth Operations
    Dev Ops
    Recommended Reading: http://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-
    flourish/

    View Slide

  22. Pattern 2: Cross-functional team
    Characteristics
    • Consists of devs, testers, ops, product
    owner, etc.
    • Focused on delivering a single
    application
    • Self-sufficient
    • Optimized for throughput

    View Slide

  23. Pattern 3: DevOps Team
    Dev Ops
    DevOps
    Characteristics
    • Consists ideally of devs with systems
    experience, or sysadmins with
    programming experience
    • Focused on automating pain points
    • Responsible for building a platform that
    allows devs to self-service
    • Provides a toolchain to enable devs to
    build, test and deploy their systems
    • Coaches other teams

    View Slide

  24. Diversify Your Team
    Teams with more women have
    higher:
    • Financial performance
    • Stock market performance
    • Hedge fund returns
    • Collective intelligence

    View Slide

  25. Version
    Control
    Configuration
    Management
    Continuous
    Integration
    Deployment
    Tools
    Monitoring
    BMC / CA
    And others…
    DevOps Toolchain

    View Slide

  26. Infrastructure as Code
    Infrastructure as Code
    Version
    Control
    Peer
    Review
    Continuous Delivery
    Collaboration Iteration
    Fast Feedback Visibility

    View Slide

  27. Continuous Delivery
    Version
    Control
    Continuous
    Integration
    Continuous
    Delivery
    Continuous
    Deployment

    View Slide

  28. Define Test Enforce Report
    Define the desired state using a
    powerful, declarative language.
    The Puppet Approach
    Test using unit and integration tools
    plus "no-op" simulation runs
    Enforce with battle-tested
    agent software on all OS'es
    Report using Puppet Enterprise
    web console and Event Inspector

    View Slide

  29. Node
    Management
    Purpose-built applications focused on solving IT automation challenges in
    new, innovative ways
    Configuration
    Management
    Application
    Orchestration
    Code
    Management
    Open Source Components - Puppet Enterprise Core - Agent Technology
    And over 3,000 more integrations, extensions, and other content
    Puppet Enterprise
    Puppet Apps

    View Slide

  30. https://en.wikipedia.org/wiki/Rainbow

    View Slide

  31. Resources and Questions
    • The 2015 State of DevOps Report 

    https://puppetlabs.com/2015-devops-report
    • Learning Puppet VM - http://learn.puppetlabs.com
    • The Phoenix Project by Gene Kim
    • Continuous Delivery by Jez Humble
    • PuppetConf 2016: http://puppetconf.com/

    View Slide