10 Do’s for DevOps!

© Electric Cloud | electric-cloud.com
10 Do’s For DevOps
Key technical practices to transform your whole organization.

Speakers
Gene Kim
DevOps Thought Leader
Strategic Advisor Electric Cloud
@realgenekim
Anders Wallgren
CTO
Electric Cloud
@anders_wallgren
/ @electriccloud - #ecwebinar
Join the conversation! #ecwebinar

Agenda
Why talk about technical practices for DevOps?
Gene and Anders’ 10 Do’s
Summary and Q&A

Why Are We Here?
DevOps Performers Ship Better Software Faster.
46x
More Software
Deployments
2555x
Less Lead Time
Code to Deploy
2604x
Faster Recovery
7x
Less Likely for
Changes to Fail
Source: 2018 DORA Accelerate: State of DevOps Report

Why Focus on Technical Practices?

Let’s Dive In!
10 Technical Practices for DevOps

DO: Make Stuff Available through Self-Service
“Leverage what your teams are already
doing and turn it into a service for others”
All the Things!
Environments, Pipelines, Infrastructure,
Configuration, Automation, …
1

DO: Make Stuff Available through Self-Service
Invest in creating a reusable wrapper layer
Consistency > Beauty! Don’t fear wrapping
and promoting legacy scripts.
Support all types of end users.
CLI, API, UI
Build For Reuse.
1

DO: Continuously Integrate and Deploy
We want developers’ best and most
strenuous efforts focused on solving
the business problem. Not screwing
around with infrastructure.
2

DO: Continuously Integrate and Deploy
Source: Damon Edwards (@damonedwards)
• Maintain a code repository
• Automate the build
• Make the build self-testing
• Everyone commits code every day
• Every commit should be build
• Keep the build fast
• Test in a clone of production
• Make latest builds easy to get
• Report latest build results to all
• Automate deployments
Lead Time = 9 months!
Source: Martin Fowler
2

DO: Take a Code Native Approach
• Pipeline as Product
§ Version control everything
§ Create templates
§ Declarative vs Imperative
• Model everything
§ Abstract and decouple application components from
Environment/Config, processes and point tools
§ Use parameters and shared components
§ Automate approval gates
§ Enable self-service consumption (see previous!)
• Collaborate & Test
§ Share code
§ Test, refactor, incrementally improve over time
3

DO: Trunk Based Development
Source: Paul Hammant: https://paulhammant.com/2013/12/04/what_is_your_branching_model/
4

Google Developer Scale
4

COMMIT PIPELINE [N]
DEV BUILD TEST
DO: Support Cloud Native Alongside Traditional
COMMIT PIPELINE [1]
DEV BUILD TEST
RELEASE PIPELINE [“N”]
INTEGRATION PRE-PROD PROD
Provision
Configure
Smoke, Other Tests
. . .
OPTIONAL ACCEPTANCE
Deploy (1…N)
Provision
Configure
Smoke, Other Tests
. . .
OPTIONAL APPROVAL
Deploy (1…N)
OPTIONAL ACCEPTANCEBuild
Unit / Other Tests
. . .
Publish Artifact
OPTIONAL APPROVAL
Provision
Configure
Functional, Other Tests
. . .
OPTIONAL APPROVAL
De-provision
Deploy
OPTIONAL ACCEPTANCE
Provision
Configure
Smoke, Other Tests
. . .
De-provision
Deploy (1…N)
OPTIONAL ACCEPTANCE
OPTIONAL APPROVAL
à Addressing Technology Impedance Mismatch
à Addressing Release Cadence Mismatch
5

DO: Promote Loosely Coupled Architectures
6
By creating loosely-coupled
architectures and designing team
boundaries to enable developer
productivity and safety, we can
improve deployment outcomes.

Loosely Coupled Allows Teams To...
Make large scale
changes to the
system without
waiting for other
teams
Reduce the coordination
with others required to
finish work
Deploy and Release
on-demand,
independent of
other services
Do majority of testing
on-demand
Perform deployments
without (or minimal)
downtime
Source: Puppet/DORA: 2017 State Of DevOps Report: https://puppet.com/resources/whitepaper/state-of-devops-report
6

High (linear)
Low
Med
Source: Puppet Labs 2015 State Of DevOps: https://puppetlabs.com/2015-devops-report
deploys/day
# of developers
6

DO: Let Teams Use Their Favorite Tools
• Don’t require conformity!
• Create abstractions and integrations
• Promote Empowered “Guild” Culture
• Build Library of Architectures, Tools,
and Service APIs
7

DO: Pervasive Production Telemetry
“If it moves, we graph it.
Even if it doesn’t move, we
graph it, just in case it
makes a run for it.”
- Ian Malpass, Etsy
2011
200,000
2015
800,000
8

8

Source: Mike Brittain, Tracking Every Release (@mikebrittain)
8

Uh oh…
8

Fix deployed, 8 min later
8

Next deployment begins
8

DO: Make Value Visible – Put it All in the Pipeline!
9

• Translate sticky-notes/whiteboard into a
Release Pipeline – it becomes an “executable”
Value Stream.
• Tribal knowledge becomes documented and
actionable.
• Everyone converges on this model as a shared
artifact for collaboration, control and visibility
across the entire process.
DO: Make Value Visible – Put it All in the Pipeline!
9

Delivery
Team
Version
Control
Build Test Release
Stage
Prod
Pipeline Orchestration
DO: Treat Security the Same as Quality
(credit: botchagalupe)
10

From… To…
Complexity Simplicity
Our work is boring, dominated by
waiting, burnout
Our work has focus, flow, and
learning
Process and compliance Innovation and Achievement
Safety I: who caused the problem? Safety II: what caused the problem?
Silo-centric Customer-centric
10

Summary: Reduce the Friction to “Doing the DevOps”!

Electric Cloud University (powered by DOI)
• Subscription-Based Training and Certification, in partnership w/DOI
• Practitioner-focused content to help accelerate success
• Mix of DevOps and Electric Cloud Product Topics
• Delivered Online and Onsite, LMS to track progress

Introducing “Upskilling: Enterprise DevOps Skills Report”

Q&A

Thank you

10 Do’s for DevOps!

Recommended

Recommended

More Related Content

What's hot

What's hot (18)

Similar to 10 Do’s for DevOps!

Similar to 10 Do’s for DevOps! (20)

More from DevOps.com

More from DevOps.com (20)

Recently uploaded

Recently uploaded (20)

10 Do’s for DevOps!