From Dev/ops to devops: What a difference one character makes

17,331 views
15,398 views

Published on

These are the slides presented at both T-dose and Devoxx 2010 by Kris Buytaert and Patrick Debois.

From Dev/ops to devops: What a difference one character makes

  1. From Dev/Ops to devops
  2. Patrick Debois Patrick.Debois@jedi.be @patrickdebois http://jedi.be/blog Kris Buytaert Kris.Buytaert@inuits.be @krisbuytaert http://krisbuytaert.be/blog
  3. There was this great IT company
  4. Full of IT-professionals
  5. But when a new release was at hand
  6. Things changed DEVS OPS
  7. “please deploy this warfile now”
  8. “we need more detail”
  9. “just do it, it’s important”
  10. “we still need more info”
  11. I’m superior! Operations is so slow We create real value Devs don’t know production We protect real value I’m superior!
  12. silence And after a few rounds
  13. The business was horrified
  14. Dev/Ops
  15. Dev/Ops
  16. Why can’t we just get along?
  17. Infrastructure used to be hard(ware)
  18. operations could only jump not fly
  19. therefore operations avoided change
  20. But then came virtualization
  21. The cloud showed us how to scale
  22. Infrastructure as code CFEngine Puppet Chef
  23. # tomcat.pp class tomcat { ! package { ! ! "java-1.6.0-sun-compat": ! ! ! ensure => "installed"; ! ! "tomcat6": ! ! ! require => [Package["java-1.6.0-sun-compat"], Package["ntc-tomcat-log4j"]], ! ! ! ensure => "installed"; ! ! "tomcat6-admin-webapps": ! ! ! ensure => "installed"; ! ! "log4j": ! ! ! ensure => "installed"; ! ! "tanukiwrapper": ! ! ! ensure => "installed"; ! ! "mysql-connector-java": ! ! ! ensure => "installed"; ! } ! file { ! ! "/etc/init.d/tomcat6": mode => "0755", owner => "root", group => "root", source => "puppet:///tomcat/tomcat6.init"; } ! user { ! ! "tomcat": ! ! ! ensure => "present", ! ! ! require => Package["tomcat6"]; ! } }! Example tomcat recipe
  24. Agile Infrastructure
  25. Rebuild from Scratch
  26. Version control
  27. Automate things
  28. Controlled changes
  29. It’s more then just automation
  30. use tests as brakes to allow you to go faster
  31. Test deploy + rollback scenario’s
  32. Make things reproducible
  33. Agile Sysadmin
  34. Operations backlog
  35. Planning Poker
  36. Iterations vs flow
  37. Pair system administration
  38. Kanban board Backlog Todo(3) Test(2) Production(1)
  39. OPS-OPS Problem Network Sysadmin Storage Security
  40. But agile devs know all that
  41. We all become developers now?
  42. Devs can just ship a virtual machine?
  43. Stop the rockstar mentality!
  44. Don’t fear for your job
  45. All this automation will only help against some local pain
  46. Let’s turn the pain level up a notch
  47. Continuous Integration If it’s hard do it more often
  48. Build Pipelines DEV TEST UAT PREPROD PROD
  49. Make all environments the same DEV TEST PROD
  50. Software only brings value in Production
  51. Parallel Build Pipelines Infrastructure Build & Test Software Build & Test Data Build & Test Application OS Level Data
  52. Synchronize your release cycles
  53. Think Continuous Delivery
  54. There are still a few problems to solve
  55. How to package things
  56. access We all want our
  57. Debug logs != Operational Logs
  58. Focus on: Flow & Cycle Time
  59. Value stream mapping
  60. Minimize waste
  61. Zero defect policy
  62. Stop the line mentality
  63. Fix things early in the process
  64. We want Continuous Improvement
  65. We need to overcome a bigger pain
  66. We need to overcome the silos Development Operations
  67. Prince2,Agile, Scrum ITIL, Cobit, CMMI Current management styles
  68. focus on optimizing individual parts
  69. Devs optimize their world view
  70. Ops optimize their world view
  71. Not In My Back Yard Syndrome
  72. Causing technical debt
  73. Like cron job fixes
  74. The map is not the territory Alfred Korzybski
  75. Systems Thinking
  76. Understand it’s a business problem
  77. do the right thing vs the thing right
  78. Collect Metrics Problems in production Failure to deploy Functionality not working Bugs Failed deploys Incidents
  79. When to decide Project vs Incidents
  80. Or functional vs non-functional requirements
  81. Relate it to business value Value lostMarket lossValue Added Bugs Failed deploys Incidents
  82. Advise and Accept the business decision
  83. Recap: No Silver Bullet
  84. It’s a jobtitle
  85. Even though we have a different culture HardwareSoftware
  86. We share the same customer
  87. We try to solve the same business problem
  88. Why only work together when things go wrong?
  89. Managers are there to support you. Not to tell you what to do
  90. It’s not about the tools
  91. It’s a cultural shift
  92. THE SECRET SAUCE OF THE DEVOPS: CAMS • Culture • Automation • Measurement • Sharing JohnWillis & Damon Edwards
  93. Multiple levels have higher impact
  94. Culture is hard, start with behavior Effort to change Impact Tools Behavior Culture
  95. Become Awesome again
  96. Interesting Books
  97. Want to know more? #devops on twitter & irc http://devopsdays.org http://devopscafe.org http://planetdevops.net devops googlegroup devops-toolchain googlegroup
  98. What keeps you awake at night?
  99. Inspired by • Vampires (Programmers) versus Werewolves (Sysadmins) • http://www.codinghorror.com/blog/ 2010/08/vampires-programmers-versus- werewolves-sysadmins.html

×