homeops - reasoning about devops at home

121

Click here to load reader

Upload: boyd-hemphill

Post on 16-Apr-2017

2.839 views

Category:

Technology


1 download

TRANSCRIPT

Page 1: HomeOps - Reasoning About DevOps at Home

HOMEOPSDevOps in Your Everyday Life

Boyd Hemphill - Technology Evangelist - @behemphi

Page 2: HomeOps - Reasoning About DevOps at Home
Page 3: HomeOps - Reasoning About DevOps at Home

@behemphi

GOALS

Provide a basis for understanding DevOps

Page 4: HomeOps - Reasoning About DevOps at Home

@behemphi

GOALS

Provide a basis for understanding DevOps

Understand Continuous Delivery (CD) is one DevOps model

Page 5: HomeOps - Reasoning About DevOps at Home

@behemphi

GOALS

Provide a basis for understanding DevOps

Understand Continuous Delivery (CD) is one DevOps model

Provide a way to reason about DevOps and CD practically

Page 6: HomeOps - Reasoning About DevOps at Home
Page 7: HomeOps - Reasoning About DevOps at Home

WHO AM I

Technologist

Page 8: HomeOps - Reasoning About DevOps at Home

WHO AM I

Technologist

Community Builder

Page 9: HomeOps - Reasoning About DevOps at Home

WHO AM I

Technologist

Community Builder

Extroverted Nerd

Page 10: HomeOps - Reasoning About DevOps at Home

WHO AM I

Technologist

Community Builder

Extroverted Nerd

Evangelist

Page 11: HomeOps - Reasoning About DevOps at Home
Page 12: HomeOps - Reasoning About DevOps at Home

@behemphi

WHAT ENGINE AM I STACKING?

Docker Docker Docker

Page 13: HomeOps - Reasoning About DevOps at Home

@behemphi

WHAT ENGINE AM I STACKING?

Docker Docker Docker

Orchestration, Service Discovery, Community

Page 14: HomeOps - Reasoning About DevOps at Home

@behemphi

WHAT ENGINE AM I STACKING?

Docker Docker Docker

Orchestration, Service Discovery, Community

Like what you hear? Contact us: http://stackengine.com

Page 15: HomeOps - Reasoning About DevOps at Home
Page 16: HomeOps - Reasoning About DevOps at Home

WHO ARE YOU

Have heard of DevOps?

Page 17: HomeOps - Reasoning About DevOps at Home

WHO ARE YOU

Have heard of Docker?

Using Continuous Integration?

Page 18: HomeOps - Reasoning About DevOps at Home

WHO ARE YOU

Have heard of DevOps?

Practicing Continous Integration?

Continuous Deployment to UAT or Production?

Page 19: HomeOps - Reasoning About DevOps at Home
Page 20: HomeOps - Reasoning About DevOps at Home

WHAT IS DEVOPS

Read the Freakin’ Manual

Page 21: HomeOps - Reasoning About DevOps at Home

WHAT IS DEVOPS

Read the Freakin’ Manual

Continuous Integration

Page 22: HomeOps - Reasoning About DevOps at Home

WHAT IS DEVOPS

Read the Freakin’ Manual

Continuous Integration

Continuous Delivery

Page 23: HomeOps - Reasoning About DevOps at Home

WHAT IS DEVOPS

Read the Freakin’ Manual

Continuous Integration

Continuous Delivery

Chef/Puppet/Ansible

Page 24: HomeOps - Reasoning About DevOps at Home

WHAT IS DEVOPS

Read the Freakin’ Manual

Continuous Integration

Continuous Delivery

Chef/Puppet/Ansible

Infrastructure as Code

Page 25: HomeOps - Reasoning About DevOps at Home

WHAT IS DEVOPS

Read the Freakin’ Manual

Continuous Integration

Continuous Delivery

Chef/Puppet/Ansible

Infrastructure as Code

Culture

Page 26: HomeOps - Reasoning About DevOps at Home

WHAT IS DEVOPS

Read the Freakin’ Manual

Continuous Integration

Continuous Delivery

Chef/Puppet/Ansible

Infrastructure as Code

Culture

Wall of Confusion

Page 27: HomeOps - Reasoning About DevOps at Home

“DevOps is the way in which a technology

organization embeds itself in a business to the

benefit of that business.”

Page 28: HomeOps - Reasoning About DevOps at Home
Page 29: HomeOps - Reasoning About DevOps at Home

FRAMEWORK FOR REASONING

Philosophy

Page 30: HomeOps - Reasoning About DevOps at Home

FRAMEWORK FOR REASONING

Philosophy

Model

Page 31: HomeOps - Reasoning About DevOps at Home

FRAMEWORK FOR REASONING

Philosophy

Model

Implementation

Page 32: HomeOps - Reasoning About DevOps at Home

FRAMEWORK FOR REASONING

Philosophy

Model

Implementation

Tools

Page 33: HomeOps - Reasoning About DevOps at Home

“Don’t be a Tool”

Page 34: HomeOps - Reasoning About DevOps at Home
Page 35: HomeOps - Reasoning About DevOps at Home

@behemphi

MOTIVATION

Maximize Family Time

Page 36: HomeOps - Reasoning About DevOps at Home

@behemphi

MOTIVATION

Maximize Family Time

Minimize Stress

Page 37: HomeOps - Reasoning About DevOps at Home

@behemphi

MOTIVATION

Maximize Family Time

Minimize Stress

Not: Save water/energy

Page 38: HomeOps - Reasoning About DevOps at Home

@behemphi

MOTIVATION

Maximize Family Time

Minimize Stress

Not: Save water/energy

Not: Cost of materials

Page 39: HomeOps - Reasoning About DevOps at Home
Page 40: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSPREMISE

A load of laundry per day will give us free Sundays

Page 41: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSPREMISE

A load of laundry per day will give us free Sundays

We will have more opportunity for family fun

Page 42: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSPREMISE

A load of laundry per day will give us free Sundays

We will have more opportunity for family fun

Stress around laundry will decrease

Page 43: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSLESSONS LEARNED

Needed to think differently about when to do a load. (batch size)

Page 44: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSLESSONS LEARNED

Needed to think differently about when to do a load. (batch size)

Needed to think differently about special situations (trips)

Page 45: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSLESSONS LEARNED

Needed to think differently about when to do a load. (batch size)

Needed to think differently about special situations (trips)

We have way too many clothes

Page 46: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSEVOLVED

Often more than one load per day

Page 47: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSEVOLVED

Often more than one load per day

Often a very small load on a day

Page 48: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSEVOLVED

Often more than one load per day

Often a very small load on a day

Easier to share work

Page 49: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSDEVOPS

Adoption of CD is first about how you view batch size

Page 50: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSDEVOPS

Adoption of CD is first about how you view batch size

Missing a Sunday of laundry was terrible, missing a day is a non-event

Page 51: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSDEVOPS

Adoption of CD is first about how you view batch size

Missing a Sunday of laundry was terrible, missing a day is a non-event

Tools only matter after you have an operational model

Page 52: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSDEVOPS

Adoption of CD is first about how you view batch size

Missing a Sunday of laundry was terrible, missing a day is a non-event

Tools only matter after you have an operational model (low water, low energy washer/dryer help control cost)

There was a stunning amount of spare capacity in our laundry system. You can see it in the SDLC

Page 53: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSREAL WORLD

Instituted weekly show-and-tell sessions with the PM

Page 54: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSREAL WORLD

Instituted weekly show-and-tell sessions with the PM

Automated developer environments

Page 55: HomeOps - Reasoning About DevOps at Home

@behemphi

LAUNDRY-OPSREAL WORLD

Instituted weekly show-and-tell sessions with the PM

Automated developer environments

All commits go to prod from day one

Page 56: HomeOps - Reasoning About DevOps at Home
Page 57: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSPREMISE

Clothes are cash tied up in our closet

Page 58: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSPREMISE

Clothes are cash tied up in our closet

Features are cash tied up in source control

Page 59: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSPREMISE

Clothes are cash tied up in our closet

Features are cash tied up in source control

Features are a competitive advantage

Page 60: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSLESSONS LEARNED

Our closets were overflowing (> $15k in clothing in our house!)

Page 61: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSLESSONS LEARNED

Our closets were overflowing (> $15k in clothing in our house!)

Fast growing kids shouldn’t have two weeks worth of clothes

Page 62: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSLESSONS LEARNED

Our closets were overflowing (> $15k in clothing in our house!)

Fast growing kids shouldn’t have two weeks worth of clothes

We have bought about 2/3 less clothing this year

Page 63: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSEVOLUTION

More room in our closets means ability to store stuff at home (not renting storage space)

Page 64: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSEVOLUTION

More room in our closets means ability to store stuff at home (not renting storage space)

Think about clothing purchases (when/why) differently. More likely to buy one thing on sale.

Page 65: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSDEVOPS

6 people~ $1m per year. Quarterly Release -> $250k in source control

Page 66: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSDEVOPS

6 people~ $1m per year. Quarterly Release -> $250k in source control

If features get to market faster, they can be exploited faster (new sales, up sales, better cash flow in/out)

Page 67: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSDEVOPS

6 people~ $1m per year. Quarterly Release -> $250k in source control

If features get to market faster, they can be exploited faster (new sales, up sales, better cash flow in/out)

You won’t take the risk with your laundry/closet.

Page 68: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSREAL WORLD

PM wanted AM involved, AM brought customer

Page 69: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSREAL WORLD

PM wanted AM involved, AM brought customer

Customers were thrilled

Page 70: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSREAL WORLD

PM wanted AM involved, AM brought customer

Customers were thrilled

Site launch was non-event

Page 71: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSREAL WORLD

PM wanted AM involved, AM brought customer

Customers were thrilled

Site launch was non-event

Updates became trivial

Page 72: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSREAL WORLD

PM wanted AM involved, AM brought customer

Customers were thrilled

Site launch was non-event

Updates became trivial

More business won by AMs

Page 73: HomeOps - Reasoning About DevOps at Home

@behemphi

CLOSET-OPSREAL WORLD

PM wanted AM involved, AM brought customer

Customers were thrilled

Site launch was non-event

Updates became trivial

More business won by AMs

More repeat business on existing accounts

Page 74: HomeOps - Reasoning About DevOps at Home
Page 75: HomeOps - Reasoning About DevOps at Home

@behemphi

SUCK-OPSPREMISE

Automating vacuuming would put time back in each day

Page 76: HomeOps - Reasoning About DevOps at Home

@behemphi

SUCK-OPSPREMISE

Automating vacuuming would put time back in each day

Daily vacuuming would decrease allergy issues in the house

Page 77: HomeOps - Reasoning About DevOps at Home

@behemphi

SUCK-OPSEVOLUTION

Expected to want to further automate but have not

Page 78: HomeOps - Reasoning About DevOps at Home

@behemphi

SUCK-OPSEVOLUTION

Expected to want to further automate but have not

Kids often take care of this.

Page 79: HomeOps - Reasoning About DevOps at Home

@behemphi

SUCK-OPSLESSONS LEARNED

There is little enough pain in moving the towers and vacuum.

Page 80: HomeOps - Reasoning About DevOps at Home

@behemphi

SUCK-OPSLESSONS LEARNED

There is little enough pain in moving the towers and vacuum.

Sometimes quality can be achieved by repetition rather than explicit effort. (Fight forward)

Still need our old vacuum for special situations

Page 81: HomeOps - Reasoning About DevOps at Home

@behemphi

SUCK-OPSDEVOPS

Our house is single story, and all wood/tile. Perfect situation for this tool

Page 82: HomeOps - Reasoning About DevOps at Home

@behemphi

SUCK-OPSDEVOPS

Our house is single story, and all wood/tile. Perfect situation for this tool

Our kids are good about picking up the floor (culture)

Page 83: HomeOps - Reasoning About DevOps at Home

@behemphi

SUCK-OPSDEVOPS

Our house is single story, and all wood/tile. Perfect situation for this tool

Our kids are good about picking up the floor (culture)

The tool is usable by all of us. Removes need for low value skill.

Page 84: HomeOps - Reasoning About DevOps at Home

@behemphi

SUCK-OPSDEVOPS

Our house is single story, and all wood/tile. Perfect situation for this tool

Our kids are good about picking up the floor (culture)

The tool is usable by all of us. Removes need for low value skill.

The tool is important, but it is the process that actually matters

Page 85: HomeOps - Reasoning About DevOps at Home

@behemphi

SUCK-OPSREAL WORLD

Moving from a home grown system to a tool (Chef), allowed a 5 person company to service 70 customers, 200 machines

Page 86: HomeOps - Reasoning About DevOps at Home

@behemphi

SUCK-OPSREAL WORLD

Moving from a home grown system to a tool (Chef), allowed a 5 person company to service 70 customers, 200 machines

The reason Chef was the right tool was not Chef, it was our single tenant architecture.

Page 87: HomeOps - Reasoning About DevOps at Home

@behemphi

SUCK-OPSREAL WORLD

Automating the dev environment fostered collaboration

Site launch and update a non-event due to repetition

Saved 8 hours per dev per week.

Page 88: HomeOps - Reasoning About DevOps at Home
Page 89: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSPREMISE

Lessons from Laundry should apply to painting the interior of our house

Page 90: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSPREMISE

Lessons from Laundry should apply to painting the interior of our house

Lower stress of home improvement

Page 91: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSPREMISE

Lessons from Laundry should apply to painting the interior of our house

Lower stress of home improvement

Increase innovation (try various colors and techniques)

Page 92: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSEVOLUTION

Started with outcome goals (e.g paint this wall)

Page 93: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSEVOLUTION

Started with outcome goals (e.g paint this wall)

Ended with time based goals (e.g. I have 3 hours on Thursday)

Page 94: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSLESSONS LEARNED

Set-up/Tear-down costs (time) were expected to be very high. Only about 25% of expected value. (Kids help!)

Page 95: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSLESSONS LEARNED

Set-up/Tear-down costs (time) were expected to be very high. Only about 25% of expected value. (Kids help!)

Need to be okay living in “undone” house (culture)

Page 96: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSLESSONS LEARNED

Set-up/Tear-down costs (time) were expected to be very high. Only about 25% of expected value. (Kids help!)

Need to be okay living in “undone” house (culture)

Time vs. feature based batching substantially lowered stress.

Page 97: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSDEVOPS

Setup cost akin to inserting a feature flag in the code.

Page 98: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSDEVOPS

Setup cost akin to inserting a feature flag in the code.

Friends curiosity about progress translates to transparency of change

Page 99: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSDEVOPS

Setup cost akin to inserting a feature flag in the code.

Friends curiosity about progress translates to transparency of change

Overall increase in time offset by our willingness to paint again soon

Page 100: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSDEVOPS

Setup cost akin to inserting a feature flag in the code.

Friends curiosity about progress translates to transparency of change

Overall increase in time offset by our willingness to paint again soon

Find wife painting while dinner was cooking akin to enabling others to do high value work.

Page 101: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSREAL WORLD

The culture of an organization must support change

Page 102: HomeOps - Reasoning About DevOps at Home

@behemphi

PAINT-OPSREAL WORLD

The culture of an organization must support change

Some times showing the customer the unfinished product is awesome

Page 103: HomeOps - Reasoning About DevOps at Home
Page 104: HomeOps - Reasoning About DevOps at Home

@behemphi

LEGO-OPSPREMISE

My sons and I could not build a 4ft, 20k piece Lego Pyramid in 5 hours.

By organizing the project so that anyone could contribute, we would get done.

Page 105: HomeOps - Reasoning About DevOps at Home

@behemphi

LEGO-OPSEVOLUTION

Project has been attempted for 4 years.

Successful at 3ft last year and 4ft this year

We will go for 5ft next year.

Page 106: HomeOps - Reasoning About DevOps at Home

@behemphi

LEGO-OPSLESSONS LEARNED

Regularity of methodology is critical

Something as simple as blue and white stripes can have a huge effect on quality.

Evolving work roles is critical

Engaging everyone is key to success

Allowing children to become managers is surprisingly effective. Its about personality, not age.

Page 107: HomeOps - Reasoning About DevOps at Home

@behemphi

LEGO-OPSDEVOPS

Model for open source software.

Quality is critical at every stage of the project.

Level of buy-in on quality with each helper determines role (e.g. 3yr old collects the right bricks but does not build)

Identifying and elevating people who own the process and its evolution drives success

Page 108: HomeOps - Reasoning About DevOps at Home

@behemphi

LEGO-OPSREAL WORLD

Ensure quality processes are in place before starting is critical to the success

Ensure processes for building and deploying software are in place is critical to success

Engineers who do not own the customer experience are not worth keeping.

Automating quality and build from day one allowed a team of three to accomplish what a team of 12 could not.

Page 109: HomeOps - Reasoning About DevOps at Home
Page 110: HomeOps - Reasoning About DevOps at Home

@behemphi

ECONOMICS

P = R - C

Page 111: HomeOps - Reasoning About DevOps at Home

@behemphi

ECONOMICS

P = R - C

C = 0 => :-(

Page 112: HomeOps - Reasoning About DevOps at Home

@behemphi

ECONOMICS

P = R - C

C = 0 => :-(

R has no limit!

Page 113: HomeOps - Reasoning About DevOps at Home

@behemphi

ECONOMICS

P = R - C

C = 0 => :-(

R has no limit!

Does your proposed change impact R?

Page 114: HomeOps - Reasoning About DevOps at Home

@behemphi

GOALS

What is the Goal of your Company?

Page 115: HomeOps - Reasoning About DevOps at Home

@behemphi

GOALS

What is the Goal of your Company?

The goal of your company is to make money now and in the future.

Page 116: HomeOps - Reasoning About DevOps at Home

@behemphi

GOALS

What is the Goal of your Company?

The goal of your company is to make money now and in the future.

If you cannot tie your action and its measures to that goal …

Page 117: HomeOps - Reasoning About DevOps at Home

@behemphi

MEASURES

Measurement is hard

Page 118: HomeOps - Reasoning About DevOps at Home

@behemphi

MEASURES

Measurement is hard

Do it anyway

Page 119: HomeOps - Reasoning About DevOps at Home
Page 120: HomeOps - Reasoning About DevOps at Home

@behemphi

BEEROPS

Austin DevOps - Monthly, Evening

goo.gl/UmLDu0

Agile Austin DevOps SIG - Monthly, Lunch

goo.gl/P8rFQ3

Cloud Austin - Monthly, Evening

goo.gl/61UwIr

DevOps Days Austin - Conference, Early August

goo.gl/r46T8A

Container Days Austin - Conference, Late March

goo.gl/aFrtwB

Page 121: HomeOps - Reasoning About DevOps at Home

@behemphi

COLOPHON

The Phoenix Project* - Kim

goo.gl/Bu4N1H

The Goal* - Goldratt (Audible)

goo.gl/UtPYTU

Start with Why* - Sinek

goo.gl/5nusW6

Lean Enterprise - Humble

goo.gl/fA9oVp

Continuous Delivery - Humble & Farley

goo.gl/X83qoQ

Slides and Blog -

http://goo.gl/4F8fDO