Jesse Robbins Keynote - Hacking Culture @ Cloud Expo Europe 2013

Jesse RobbinsCofounder, Opscode@jesserobbinsjesse@opscode.comHacking Culture@ CloudExpoEurope

Web / Cloud Operations is the ability to consistently create anddeploy reliable software to an unreliable platform that scales horizontally.http://radar.oreilly.com/2007/10/operations-is-a-competitive-ad.html 3

The right culture is arequirement for survival & success.

♥DevOpsCulture and

Google, Amazon, Microsoft, etc...built their own automation &deployment tools to support this

but it was “secret sauce”

Cloud Infrastructure Automation

20,000+ Users1,000+ ContributorsThousands of Companiesreaching over a billion people

Fundamental Attributes of Successful Cultures1) Infrastructure as Code2) Application as Services3) Dev + Ops + All as Teams

Fundamental Attributes of Successful Cultures1) Infrastructure as Code2) Application as Services3) Dev + Ops + All as Teams Massive improvement in “Time to Value”

Common Attributes of Successful CulturesInfrastructure Application Dev / Ops / All as Code as Services as Teams‣ Full Stack Automation ‣ Service Orientation ‣ Shared Metrics /‣ Commodity Hardware ‣ Lightweight Protocols Monitoring and/or Cloud Infra ‣ Versioned APIs ‣ Incident Management‣ Reliability in software ‣ Software Resiliency ‣ Service Owners On-call stack (Design for Failure) ‣ Tight integration ‣ Database/Storage ‣ Continuous Integration‣ Datacenter or Cloud ‣ Continuous Abstraction Infrastructure APIs Deployment ‣ Complexity pushed up‣ Core Infra Services the stack ‣ SRE/SRO ‣ Infrastructure as ‣ Deep Instrumentation ‣ GameDay Product ‣ App as Customer

The path organizations take... Full Continuous Infrastructure Application Deployment Automation Configuration Common ManagementDiscovery and Management Automation Tasks: Visibility Scripts, OS Compliance, Updates & Patches

back at the office,this may sound familiar...

misalignedincentives

Dear Jesse,I work for a big company. I tried to talk to people about this awesome stuff and they told me it would never work here. What do I do now?Sincerely, Most of us

Change takes time (sorry about that)

You cannot change everyone or everything at once.

Choose your battles, or better yet, don’t battle at all...

Jesse’s Rule: Don’t Fight Stupid,Make More Awesome!

Changing Culture:1. Start small, build trust & safety2. Create Champions3. Use metrics to build confidence4. Celebrate successes5. Exploit Compelling Events 25

Example: GameDaySlide Courtesy of John Allspaw - http://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-ﬂickrhttp://www.ﬂickr.com/photos/dnorman/2678090600

deﬁne:GameDay An exercise designed to increase Resilience through large-scale fault injection across critical systems. Part of a larger discipline called Resilience Engineering. See also: Chaos Monkey

25% Pyromaniac75% Paranoid

GameDay increases Resilience in 3 ways Preparation ‣ Identification and mitigation of risks and impact from failure ‣ Reduces frequency of failure (MTBF) ‣ Reduces duration of recovery (MTTR) Participation ‣ Builds confidence & competence responding to failure and under stress. ‣ Strengthens individual and cultural ability to anticipate, mitigate, respond to, and recover from failures of all types. Exercises ‣ Trigger and expose “latent defects” ‣ Choose when discover them, instead of letting that be determined by the next real disaster.

start small... http://www.flickr.com/photos/oakleyoriginals/5674150237

build on trust & safety...http://www.flickr.com/photos/skevbo/4864249944

Create Champions... http://www.flickr.com/photos/maunzy/5099921731

Use metrics to build confidence...http://tacomafiredepartment.blogspot.com/2010/05/west-slope-training-burn.html

use metrics to build confidence

Celebrate successes

Exploit Compelling Eventshttp://www.flickr.com/photos/peregrinari/3801964067

Hacks:Starting Small1. Small isn’t a threat & is easy to ignore2. Just call it an experiment 39

Hacks:Creating Champions1. Get executive sponsors, starting with your boss.2. Give everyone else the credit.3. Give “Special Status”4. Have people with “Special Status” talk about the new awesome. 40

Hacks: Metrics1. Find KPI that supports change2. Track and use it ruthlessly - first to show value, later cost of not making the change by laggards3. Tell your story with data 41

Hacks: Celebrating successes1. Tell a powerful story2. Always positive about people and how they overcame a problem.3. Never about people who created the problem.4. Leave room for people to come to your side. (don’t fight stupid ;-) 42

Hacks:Compelling Events1. Just wait, it will come2. Can be created by things like compliance, scaling, cloud migrations3. Not “I told you so” - but “what do we do now” 43

Common Attributes of Successful CulturesInfrastructure Application Dev / Ops / All as Code as Services as Teams‣ Full Stack Automation ‣ Service Orientation ‣ Shared Metrics /‣ Commodity Hardware ‣ Lightweight Protocols Monitoring and/or Cloud Infra ‣ Versioned APIs ‣ Incident Management‣ Reliability in software ‣ Software Resiliency ‣ Service Owners On-call stack (Design for Failure) ‣ Tight integration ‣ Database/Storage ‣ Continuous Integration‣ Datacenter or Cloud ‣ Continuous Abstraction Infrastructure APIs Deployment ‣ Complexity pushed up‣ Core Infra Services the stack ‣ SRE/SRO ‣ Infrastructure as ‣ Deep Instrumentation ‣ GameDay Product ‣ App as Customer

Jesse Robbins@jesserobbinsjesse@opscode.comWe’re in UK Now! Contact Andy Hawkins andy@opscode.com

https://twitter.com	74
http://eventifier.co	10
http://kred.com	4
http://twitter.com	1

Jesse Robbins Keynote - Hacking Culture @ Cloud Expo Europe 2013

by Jesse Robbins on Jan 29, 2013

Accessibility

Categories

Upload Details

Usage Rights

4 Embeds 89

Statistics

Jesse Robbins Keynote - Hacking Culture @ Cloud Expo Europe 2013 Presentation Transcript