+ All Categories
Home > Technology > Cloudy with a chance of devops (UMN)

Cloudy with a chance of devops (UMN)

Date post: 14-Apr-2017
Category:
Upload: bridgetkromhout
View: 168 times
Download: 2 times
Share this document with a friend
43
@bridgetkromhout Cloudy with a chance of DevOps
Transcript
Page 1: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Cloudy with a chance of DevOps

Page 2: Cloudy with a chance of devops (UMN)

@bridgetkromhout

lives: Minneapolis,

Minnesota

works: Pivotal

podcasts: Arrested DevOps

organizes: devopsdays

Bridget Kromhout

Page 3: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Page 4: Cloudy with a chance of devops (UMN)

@bridgetkromhout

xkcd.com/208/

Page 5: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Docker in Production: Reality, Not Hype

Page 6: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Traded oncall… …for more travel (Similar effect on sleep)

Page 7: Cloudy with a chance of devops (UMN)

@bridgetkromhout

“In the last week there were 67 deploys of 496 changes by 18 people”

Image credit: visual_dichotomy on Flickr

Page 8: Cloudy with a chance of devops (UMN)

@bridgetkromhout

quoted in “10+ Deploys Per Day: Dev and Ops Cooperation at Flickr” at Velocity 2009

John Allspaw & Paul Hammond

“In the last week there were 67 deploys of 496 changes by 18 people”

Flickr Dev Blog, December 17th 2008

Image credit: visual_dichotomy on Flickr

Page 9: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Why don’t we all move that fast today?

Page 10: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Environments: how long to spin up a new one or copy an existing one?

Why don’t we all move that fast today?

Page 11: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Environments: how long to spin up a new one or copy an existing one?

Deploys: how often? how long do they take? How often do they go wrong?

Why don’t we all move that fast today?

Page 12: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Failure: what does recovery look like?

Environments: how long to spin up a new one or copy an existing one?

Deploys: how often? how long do they take? How often do they go wrong?

Why don’t we all move that fast today?

Page 13: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Not the goal: “automate all the things”

Page 14: Cloudy with a chance of devops (UMN)

@bridgetkromhout

The goal: shorter time from idea to value

Image credit: leadliasionImage credit: thebigword

Page 15: Cloudy with a chance of devops (UMN)

@bridgetkromhout

How do we get to

the goal?

Page 16: Cloudy with a chance of devops (UMN)

@bridgetkromhout

How do we get to

the goal?

Page 17: Cloudy with a chance of devops (UMN)

@bridgetkromhout

The Wall of Confusion

Page 18: Cloudy with a chance of devops (UMN)

@bridgetkromhout

The Wall of Confusion

yolo nope

Page 19: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Page 20: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Page 21: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Deconstructing a Python/Django monolith into Dockerized Go microservices

(as was the style at the time)

How to win at buzzword bingo:

Page 22: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Two-Pizza teams

Page 23: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Image credit: James Ernest

Page 24: Cloudy with a chance of devops (UMN)

@bridgetkromhout Image credit: Wikipedia

“Any organization that designs a system… will produce a design

whose structure is a copy of the organization's

communication structure.”

Mel Conway

Page 25: Cloudy with a chance of devops (UMN)

@bridgetkromhout

“Effective devops tools enable automation

without isolating humans from the automation

process”

Jennifer Davis

Page 26: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Common Ground and Coordination in Joint Activity Klein, Feltovich, Bradshaw, Woods (2004)

Page 27: Cloudy with a chance of devops (UMN)

@bridgetkromhout

non-violent communication & emotional literacy

Page 28: Cloudy with a chance of devops (UMN)

@bridgetkromhout

“Understanding is a

three-edged sword”

Page 29: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Page 30: Cloudy with a chance of devops (UMN)

@bridgetkromhout

distributed systems free-association game

Image credit: Kyle Kingsbury, Jepsen project

Page 31: Cloudy with a chance of devops (UMN)

@bridgetkromhout

CA

CP AP

AvailabilityConsistency

Partition Tolerance

“a partition is a time bound

on communication.”Eric Brewer

Page 32: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Page 33: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Legacy: because nothing is ever temporary

Page 34: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Visvesvaraya Museum, Bengaluru

IBM 1401 (in use until 1989)

Page 35: Cloudy with a chance of devops (UMN)

@bridgetkromhout

“It’s not necessary to change.

Survival is not mandatory.”

—W. Edwards Deming

Page 36: Cloudy with a chance of devops (UMN)

@bridgetkromhout

navigating choices

Page 37: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Inaction is still a choice

Page 38: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Process: scar tissue from past

failure

Page 39: Cloudy with a chance of devops (UMN)

@bridgetkromhout

12-factor kitten

Page 40: Cloudy with a chance of devops (UMN)

@bridgetkromhout

The Wall of Confusion (here there be White Walkers)

Page 41: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Page 42: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Page 43: Cloudy with a chance of devops (UMN)

@bridgetkromhout

Thank you!


Recommended