DevOpsat5,016 FeetJ. Paul ReedPrincipal, Release Engineering ApproachesChief Delivery Officer, PraxisflowDevOps Days RockiesApril 23, 2015

J. Paul Reed• AKA the “Sober Build Engineer”

• @SoberBuildEng on

• Principal at Release Engineering Approaches

• Chief Delivery Officer at Praxisflow

• 15+ Years in Build/Release Engineering

Also Available on iTunes

@eciramella

@buildscientist

@cheeseplus

@sascha_d

@petecheslock

www.theshipshow.com

@ShipShowPodcast

@SonOfGarr @beerops

In This Photo...

• Actually-Sober

• Actually-Not a Build Engineer

Go Impalas!

MomOps

MomOps

Fort Collins/Loveland Airport, c. 2002

DevOps Unicorns

DevOps Unicorns?

DevOps Unicorns

DevOps

Which ToolsYou Use

Do Not Matter...

Dev

“Good practices” vs. Time*Not to Scale

All Source Deps in Repo

1980s & before Today

Tool Deps in Repo

All source in source repo

Source Deps in Repo

Feature Flags

Componentization(Microservices)

Continuous Deployment

Continuous Integration

Consistent Deployment Process

Automated Deployment Process

Build Env Under Config Mgmt

Dev Build Env under Config Mgmt

Build-before-checkin CultureDocumentation

Actionable Unit Tests

Unit Tests

Code Inspection

Accurate Documentation

Code Review

Consistent Coding Style

Versioning

Artifact Repositories

Ops

“Good practices” vs. Time*Not to Scale

Mountains of Shell Scripts

1980s & before Today

Snowflake Servers

syslogd to the Printer

CDs in Trays

Mountain of Perl Scripts

Infrastructure as Code

Continuous Integration

BOFHManaged Virtualization

Infrastructure Pipelines

Source Control

Documentation

Unit Testing for Infrastructure

Infrastructure Monitoring/“Insight”

Virtualization

Throwaway Servers

Accurate Documentation

Code Review

Versioning

Production Under Config Mgmt

Infra-as-a-Service

Ops

“Good practices” vs. Time*Still Not to Scale

Dev

Source

Control

Continuous

Integration

Artifact

Repo

Automated

Deploym

ents

Infra-as-a-

Service

Mountains of Shell Scripts

CDs in Trays

BOFH

Actionable Unit Tests

Code Inspection

All source in source repo

Code Review

Infrastructure

Monitoring/

“Insight”

Ops

“Good practices” vs. Time*Still Not to Scale

Dev

Source

Control

Continuous

Integration

Artifact

Repo

Automated

Deploym

ents

Infra-as-a-

Service

Mountains of Shell Scripts

CDs in Trays

BOFH

Actionable Unit Tests

Code Inspection

All source in source repo

Code Review

Infrastructure

Monitoring/

“Insight”

Which ToolsYou Use

Do Not Matter:“Center & to the Right” Matters

Groups of people create a culture through shared values and behaviors.

How we reward behaviors, how we treat those values as malleable or immutable affects how strong the organization’s culture is and howwell it is supported by the participants.

-Mandi Walls

Culture Is Not Important...

On “Company Culture”

“Move fast, break things.”*

On “Company Culture”

On “Company Culture”

“Context, not control.”

On “Company Culture”

On “Company Culture”

“A ‘Have Coffee’ culture”

On “Company Culture”

Our true culture is made primarily of the things no one will say...

Culture is about power dynamics, unspoken priorities and beliefs, mythologies, conflicts, enforcement of social norms, creation of in/out groups, and distribution of wealth and control inside companies.

Your Startup is Broken: Inside the Toxic Heart of Tech Culture

Culture Is Not Important, but

Cultural Alignmentis critical

A Little Light Reading

FeedbackLoops

http://itrevolution.com/the-three-ways-principles-underpinning-devops/

http://itrevolution.com/the-three-ways-principles-underpinning-devops/

http://itrevolution.com/the-three-ways-principles-underpinning-devops/

SystemsThinking

Map the System

Courtesy @lusis

A Blunt Definition

Operability

Memphis:

Memphis:IT’S RIGHT THERE

Beware the OperationalAssumptions You Make

InOur

Software

Resilience

Microservices

Maintainability

Operability?

InOur

Teams

Resilience

Independently EmpoweredTeams/Actors

Sustainability

Operability?

Something that is really great about Star Trek, is that when a character notices something is amiss, and they are the only one to see it, the rest of the crew doesn’t just dismiss their concerns offhand.

You aren’t saddled with an episode of the character trying to convince everyone else that what they saw/heard/felt was real. Everyone else believed them right away. They’ve probably already started running scans, and started trying to help their friend, instead of treating them like a child.

-Trouble With DevOps? Try TrekOps

My Home Airport

Stall + Spin Accident

The Physics Hadn’t Changed,

But the Environment Had...

The Physics Hadn’t Changed

But the Environment Had...

So My Heuristics Were Off!

DevOps Hadn’t Changed

But the Environment Had...

So My Heuristics Were Off!

An Awesome Lineup

Field Elevation: 5016 feet

@SoberBuildEngAnonymous feedback: sayat.me/jpaulreedJ. Paul

Reed www.release-approaches.comSimply Ship. Every Time.

Adoption of Agile & DevOps methodologies is a journey, and every person and organization’s journey is going to be different.

-J. Paul Reed

DevOps in Practice

J. Paul Reed

http://www.oreilly.com/webops-perf/free/devops-in-practice.csp