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.

DevOps transformations for DevOpsDays Riga 2018

151 views

Published on

SysAdmins are obsolete, we need more DevOps engineers! Or do we? Why technology X is not what you need right now? Why ignoring skills that are already present in the team may be a huge risk? Why everything-as-code is an effective approach? Why not investing in team member education may be very destructive? Why not having time is a bad excuse for not automating? Why process improvement effects may not be observable immediately? Why cost of automation sometimes is higher than the time invested in writing the scripts?

Published in: Technology
  • Be the first to comment

  • Be the first to like this

DevOps transformations for DevOpsDays Riga 2018

  1. 1. "DevOps" tools
  2. 2. Tools
  3. 3. More tools
  4. 4. Even more tools
  5. 5. Is this the best stack?
  6. 6. Does this help?
  7. 7. Or this?
  8. 8. Ocean of tools!
  9. 9. But...
  10. 10. DevOps is not about tools!
  11. 11. Or is it?
  12. 12. History
  13. 13. Tools and weapons
  14. 14. Build and protect!
  15. 15. We use tools to protect our culture!
  16. 16. Tools vs Culture
  17. 17. Cargo cult
  18. 18. Healthy lifestyle
  19. 19. Start running
  20. 20. Broken leg!
  21. 21. Regret
  22. 22. Running does not work!
  23. 23. Running is not for me!
  24. 24. Running is for healthy people!
  25. 25. Well...
  26. 26. Combination of things Just walking instead of running Different diet More sleeping time Mix activities Reduce stress (peace of mind) Find a trainer/mentor • • • • • •
  27. 27. Tools vs Culture
  28. 28. Dialogues
  29. 29. Broken communication
  30. 30. Rigid structure
  31. 31. Lack of culture?
  32. 32. Lack of tooling?
  33. 33. 2001
  34. 34. Agile
  35. 35. Agile principles Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan • • • •
  36. 36. 2003
  37. 37. Mary Poppendieck
  38. 38. Lean Software Development
  39. 39. Lean principles Eliminate waste Amplify learning Decide as late as possible Deliver as fast as possible Empower the team Build integrity in See the whole • • • • • • •
  40. 40. 2008
  41. 41. Andrew Clay Shafer
  42. 42. Infrastructure is Code
  43. 43. Patrick Debois
  44. 44. Agile Infrastructure
  45. 45. DevOps
  46. 46. Wikipedia DevOps aims at shorter development cycles, increased deployment frequency, and more dependable releases, in close alignment with business objectives. “
  47. 47. 2010
  48. 48. John Willis
  49. 49. C.A.M.S Culture Automation Measurement Sharing • • • •
  50. 50. 2011
  51. 51. Jez Humble
  52. 52. CD principles Build quality in Work in small batches Computers perform repetitive tasks, people solve problems Relentlessly pursue continuous improvement Everyone is responsible • • • • •
  53. 53. 2013
  54. 54. Gene Kim
  55. 55. The 3 ways of DevOps
  56. 56. The first way
  57. 57. The second way
  58. 58. The third way
  59. 59. Isomorphic models
  60. 60. 2017
  61. 61. GitOps!
  62. 62. GitOps Provisioning and deployment is declarative Entire system state is under version control Operational changes are made by pull request (plus build & release pipelines) Diff tools detect any divergence and sync tools enable convergence Rollback and audit logs are also provided via Git • • • • •
  63. 63. Ops by pull request
  64. 64. The single source of truth
  65. 65. Knowledge capture
  66. 66. Everything is code!
  67. 67. Everything is code Pipeline-as-code Documentation-as-code Tests-as-code Security-as-code Infrastructure-as-code Network-as-code Metrics-as-code • • • • • • •
  68. 68. IT is code!
  69. 69. We are all contributors!
  70. 70. We are all collaborators!
  71. 71. Who do we need?
  72. 72. T-shaped people
  73. 73. T-shaped people
  74. 74. How do we plan?
  75. 75. Gene Kim
  76. 76. Unplanned work
  77. 77. Unplanned work
  78. 78. Unplanned work
  79. 79. Unplanned work
  80. 80. Dominica DeGrandis
  81. 81. Time thieves
  82. 82. Reduce WIP
  83. 83. More No!
  84. 84. How should we work together?
  85. 85. Mathew Skelton
  86. 86. DevOps Topologies
  87. 87. Type 1: Dev and Ops Collaboration
  88. 88. Type 2: Fully Shared Ops Responsibilities
  89. 89. Type 3: Ops as Infrastructure-as-a- Service
  90. 90. Type 4: DevOps as an External Service
  91. 91. Type 5: DevOps Team with an Expiry Date
  92. 92. What should we use?
  93. 93. Neal Ford
  94. 94. Innovation curve
  95. 95. Technology radar
  96. 96. Rings Hold Assess Trial Adopt • • • •
  97. 97. Quadrants
  98. 98. Radar example
  99. 99. Radar example
  100. 100. Future is here! The future is already here ? it's just not very evenly distributed. William Gibson “
  101. 101. Where do we aim?
  102. 102. Where is the industry going?
  103. 103. Simon Wardley
  104. 104. Maps Visual Context Position, anchor and movement Components • • • •
  105. 105. Maps Navigation Learning Strategy Situational awareness • • • •
  106. 106. Maps
  107. 107. Final words Directions and planning as well as progress should be visible (radars, maps, boards) VCS repos are the only source of truth (CD + GitOps) Pipelines handle all aspects of software delivery (CD + GitOps) Tools do not matter that much, but use them to enforce your culture! • • • •
  108. 108. Thank you!
  109. 109. Kahoot!

×