Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Practical Methods for Adopting DevOps - Michael Stahnke

3 545 vues

Publié le

Michael Stahnke talks about "Practical Methods for Adopting DevOps"

Publié dans : Technologie
  • Soyez le premier à commenter

Practical Methods for Adopting DevOps - Michael Stahnke

  1. 1. Practical Methods for Adopting DevOps Michael Stahnke, Director of Engineering Services @stahnma
  2. 2. • Introduction • DevOps Overview • When It’s Bad • Making It Better – 5 Methods • Questions Next Week & PuppetConf Overview
  3. 3. Next Week & PuppetConfIntroduction • Server architecture • Infrastructure automation • Release management
  4. 4. It’s impossible to exceed expectations.
  5. 5. Nobody ever got a high-five for a server staying up.
  6. 6. Next Week & PuppetConfDevOps Culture • Lots of press, talks, hype • Echo chamber • Does it apply to all of us? • 10 deploys/day • Rockstar ninja pirates • Write your own tools • Awesome app developers • Startups
  7. 7. Next Week & PuppetConfSetting the Stage • Large company size with competing priorities • IT teams that don’t sit in the same building • Average time in role: 2-3 years • No dev … “application owners” • Everybody really “nice”
  8. 8. Next Week & PuppetConfSetting the Stage • Call the vendor for problems • Customize for us, our needs are unique • Success means everything stays the same • Just looking for approvals • No time to debate
  9. 9. Next Week & PuppetConfSetting the Stage • Enterprise-y: Tivoli, BMC, CA, IBM • Apps: Oracle RAC, Oracle EBS, Websphere AS, MQ Series, Weblogic, Legacy stuff • HP-UX, Solaris, AIX, RHEL, VMware Tool s
  10. 10. Next Week & PuppetConfInfrastructure Team • Small team – 4 of you quit; that’s 50% of the team • Information is tribal – What happens when the tribe leaves? • 16 hour days for some admins • Server team blamed for EVERYTHING This Silo? What Silo?
  11. 11. Next Week & PuppetConfInfrastructure Team • No transfers • Windows team doesn’t work with Unix team, who doesn’t talk to Storage team • Exiled to different buildings This Silo? What Silo?
  12. 12. Next Week & PuppetConfIs it all bad? • Industry experience • Be the best sysadmin • Open Source tooling • LDAP Motivations
  13. 13. Next Week & PuppetConfDatabases Rule the World • Variance • 25 db servers • 24 unique configurations • At least 6 cluster pairs
  14. 14. Reduce the standard deviation value. Then raise the mean.
  15. 15. Next Week & PuppetConf Method 1 Reduce variability.
  16. 16. Next Week & PuppetConf Method 1 Standardize & automate what’s variable or inconsistent to reduce deviation.
  17. 17. Do you want systems to have planned or unplanned downtime? Because you’re going to get one or the other.
  18. 18. Next Week & PuppetConf Results • Failing in known ways • Better uptime • Fewer configurations • Lots of tickets on disk management
  19. 19. Collaboration?
  20. 20. Next Week & PuppetConf Collaboration • Sudo for disk mgmt • Shared responsibility for outages • Proper classification (production, test, dev) • If I’m awake, you’re awake
  21. 21. Next Week & PuppetConfCollaboration • Share the pain • People who carry the pager will make better design decisions when not on- call
  22. 22. Next Week & PuppetConf Method 2 Stop. Collaborate. Listen. (Break down silos)
  23. 23. Next Week & PuppetConf Method 2 Integrate your Ops engineers early in the ALC and collaborate on interfaces & handoffs
  24. 24. Next Week & PuppetConfRoot Cause Analysis Meetings • What’s the root cause of the outage? • What’s the exact impact? • What do we do differently next time?
  25. 25. Next Week & PuppetConf Method 3 Shout your failures. (Honesty builds credibility)
  26. 26. Next Week & PuppetConf Method 3 Listen and learn about failures so they aren’t repeated.
  27. 27. Next Week & PuppetConfRoot Cause Analysis Meetings • Shout out your failure • Hand out a written report & timeline of what happened • Remediation plan • Meeting lasts 10 minutes
  28. 28. Next Week & PuppetConf Setbacks • Everything isn’t better overnight • Time passes, new issues • Lots of failures • Config Mgmt messes Don’t expect perfection
  29. 29. Next Week & PuppetConfExperiments • What can you try while you’re fixing process? • Scrum teams • SDLC • Inventory service • Puppet
  30. 30. Next Week & PuppetConf Method 4 Experimentation matters. (Failures are still valid data)
  31. 31. Next Week & PuppetConf Method 4 This means Ops engineers need dev/test environments for monitoring & tooling
  32. 32. Next Week & PuppetConfPeriodic Review • Find biggest pain points – optimize • Improving anything that isn’t the biggest bottleneck in a process is a wasted effort! • Drive value up the stack • Find metrics people understand • (Use Puppet)
  33. 33. The cost of retiring any technology is much higher than introducing it.
  34. 34. Next Week & PuppetConf Learning • Python, Ruby, Puppet, git, REST, APIs, Web Services, Go, Containers • Retrospectives • Daily standups • Lead by example
  35. 35. Are we satisfied with how this works, or are we trying to make it better?
  36. 36. Next Week & PuppetConfImprovements • Influence other teams • Automation help • Monitoring • Design • Requests to transfer to your team
  37. 37. Next Week & PuppetConf Method 5 Solve causes not symptoms. (Continuous improvement)
  38. 38. Next Week & PuppetConf Method 5 Focus Ops Engineers on proactive fixes to root causes, not fighting the symptoms
  39. 39. • Reduce variability. • Stop. Collaborate. Listen. • Shout your failures. • Experimentation matters. • Solve causes not symptoms. Next Week & PuppetConf Recap

×