Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Loading in …3
×
1 of 47

Jesse Robbins Keynote - Hacking Culture @ Cloud Expo Europe 2013

27

Share

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Jesse Robbins Keynote - Hacking Culture @ Cloud Expo Europe 2013

  1. Jesse Robbins Cofounder, Opscode @jesserobbins jesse@opscode.com Hacking Culture @ CloudExpoEurope
  2. Copyright © 2010 Opscode, Inc - All Rights Reserved 2
  3. Web / Cloud Operations is the ability to consistently create and deploy reliable software to an unreliable platform that scales horizontally. http://radar.oreilly.com/2007/10/operations-is-a-competitive-ad.html 3
  4. The right culture is a requirement for survival & success.
  5. ♥ DevOps Culture and
  6. Google, Amazon, Microsoft, etc... built their own automation & deployment tools to support this
  7. but it was “secret sauce”
  8. everyone else was here ... inexperienced & poorly equipped for the world they must now operate in. Copyright © 2010 Opscode, Inc - All Rights Reserved 8
  9. Cloud Infrastructure Automation
  10. 20,000+ Users 1,000+ Contributors Thousands of Companies reaching over a billion people
  11. Fundamental Attributes of Successful Cultures 1) Infrastructure as Code 2) Application as Services 3) Dev + Ops + All as Teams
  12. Fundamental Attributes of Successful Cultures 1) Infrastructure as Code 2) Application as Services 3) Dev + Ops + All as Teams Massive improvement in “Time to Value”
  13. Common Attributes of Successful Cultures Infrastructure 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
  14. Common Attributes of Successful Cultures Infrastructure 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
  15. The path organizations take... Full Continuous Infrastructure Application Deployment Automation Configuration Common Management Discovery and Management Automation Tasks: Visibility Scripts, OS Compliance, Updates & Patches
  16. back at the office, this may sound familiar...
  17. misaligned incentives
  18. 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
  19. Change takes time (sorry about that)
  20. You cannot change everyone or everything at once.
  21. Choose your battles, or better yet, don’t battle at all...
  22. Jesse’s Rule: Don’t Fight Stupid, Make More Awesome!
  23. Changing Culture: 1. Start small, build trust & safety 2. Create Champions 3. Use metrics to build confidence 4. Celebrate successes 5. Exploit Compelling Events 25
  24. Changing Culture: 1. Start small, build trust & safety 2. Create Champions 3. Use metrics to build confidence 4. Celebrate successes 5. Exploit Compelling Events 26
  25. Example: GameDay Slide Courtesy of John Allspaw - http://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr http://www.flickr.com/photos/dnorman/2678090600
  26. define: 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
  27. 25% Pyromaniac 75% Paranoid
  28. 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.
  29. start small... http://www.flickr.com/photos/oakleyoriginals/5674150237
  30. build on trust & safety... http://www.flickr.com/photos/skevbo/4864249944
  31. Create Champions... http://www.flickr.com/photos/maunzy/5099921731
  32. Use metrics to build confidence... http://tacomafiredepartment.blogspot.com/2010/05/west-slope-training-burn.html
  33. use metrics to build confidence
  34. Celebrate successes
  35. Exploit Compelling Events http://www.flickr.com/photos/peregrinari/3801964067
  36. Changing Culture: 1. Start small, build trust & safety 2. Create Champions 3. Use metrics to build confidence 4. Celebrate successes 5. Exploit Compelling Events 38
  37. Hacks:Starting Small 1. Small isn’t a threat & is easy to ignore 2. Just call it an experiment 39
  38. Hacks:Creating Champions 1. 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
  39. Hacks: Metrics 1. Find KPI that supports change 2. Track and use it ruthlessly - first to show value, later cost of not making the change by laggards 3. Tell your story with data 41
  40. Hacks: Celebrating successes 1. Tell a powerful story 2. 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
  41. Hacks:Compelling Events 1. Just wait, it will come 2. Can be created by things like compliance, scaling, cloud migrations 3. Not “I told you so” - but “what do we do now” 43
  42. Jesse’s Rule: Don’t Fight Stupid, Make More Awesome!
  43. Common Attributes of Successful Cultures Infrastructure 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
  44. Jesse’s Rule: Don’t Fight Stupid, Make More Awesome!
  45. Jesse Robbins @jesserobbins jesse@opscode.com We’re in UK Now! Contact Andy Hawkins andy@opscode.com

×