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.
Upcoming SlideShare
What to Upload to SlideShare
What to Upload to SlideShare
Loading in …3
×
1 of 128

DevOps Transformations for BCS London

2

Share

Download to read offline

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?

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

DevOps Transformations for BCS London

  1. 1. 01
  2. 2. 02
  3. 3. 03
  4. 4. 04
  5. 5. "DevOps" tools 05
  6. 6. Tools 06
  7. 7. More tools 07
  8. 8. Even more tools 08
  9. 9. Is this the best stack? 09
  10. 10. Does this help? 10
  11. 11. Or this? 11
  12. 12. Ocean of tools! 12
  13. 13. But... 13
  14. 14. DevOps is not about tools! 14
  15. 15. Or is it? 15
  16. 16. History 16
  17. 17. Tools and weapons 17
  18. 18. Build and protect! 18
  19. 19. We use tools to protect our culture!19
  20. 20. Tools vs Culture 20
  21. 21. Cargo cult 21
  22. 22. Healthy lifestyle 22
  23. 23. Start running 23
  24. 24. Broken leg! 24
  25. 25. Regret 25
  26. 26. Running does not work! 26
  27. 27. Running is not for me! 27
  28. 28. Running is for healthy people!28
  29. 29. Well... 29
  30. 30. Combination of things Just walking instead of running Different diet More sleeping time Mix activities Reduce stress (peace of mind) Find a trainer/mentor • • • • • • 30
  31. 31. Tools vs Culture 31
  32. 32. Dialogues 32
  33. 33. 33
  34. 34. 34
  35. 35. 35
  36. 36. 36
  37. 37. Broken communication 37
  38. 38. Rigid structure 38
  39. 39. Lack of culture? 39
  40. 40. Lack of tooling? 40
  41. 41. 2001 41
  42. 42. Agile 42
  43. 43. 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 • • • • 43
  44. 44. 2003 44
  45. 45. 45
  46. 46. Mary Poppendieck 46
  47. 47. Lean Software Development47
  48. 48. 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 • • • • • • • 48
  49. 49. 2008 49
  50. 50. 50
  51. 51. Andrew Clay Shafer 51
  52. 52. Infrastructure is Code 52
  53. 53. 53
  54. 54. Patrick Debois 54
  55. 55. Agile Infrastructure 55
  56. 56. DevOps 56
  57. 57. Wikipedia DevOps aims at shorter development cycles, increased deployment frequency, and more dependable releases, in close alignment with business objectives. “ 57
  58. 58. 2010 58
  59. 59. 59
  60. 60. John Willis 60
  61. 61. C.A.M.S Culture Automation Measurement Sharing • • • • 61
  62. 62. 2011 62
  63. 63. 63
  64. 64. Jez Humble 64
  65. 65. CD principles Build quality in Work in small batches Computers perform repetitive tasks, people solve problems Relentlessly pursue continuous improvement Everyone is responsible • • • • • 65
  66. 66. 2013 66
  67. 67. 67
  68. 68. Gene Kim 68
  69. 69. The 3 ways of DevOps 69
  70. 70. The first way 70
  71. 71. The second way 71
  72. 72. The third way 72
  73. 73. Isomorphic models 73
  74. 74. 2017 74
  75. 75. GitOps! 75
  76. 76. 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 • • • • • 76
  77. 77. Ops by pull request 77
  78. 78. The single source of truth78
  79. 79. Knowledge capture 79
  80. 80. Everything is code! 80
  81. 81. Everything is code Pipeline-as-code Documentation-as-code Tests-as-code Security-as-code Infrastructure-as-code Network-as-code Metrics-as-code • • • • • • • 81
  82. 82. IT is code! 82
  83. 83. We are all contributors! 83
  84. 84. We are all collaborators! 84
  85. 85. Who do we need? 85
  86. 86. T-shaped people 86
  87. 87. T-shaped people 87
  88. 88. How do we plan? 88
  89. 89. 89
  90. 90. Gene Kim 90
  91. 91. Unplanned work 91
  92. 92. Unplanned work 92
  93. 93. Unplanned work 93
  94. 94. Unplanned work 94
  95. 95. 95
  96. 96. Dominica DeGrandis 96
  97. 97. Time thieves 97
  98. 98. Reduce WIP 98
  99. 99. More No! 99
  100. 100. How should we work together?100
  101. 101. 101
  102. 102. Mathew Skelton 102
  103. 103. DevOps Topologies 103
  104. 104. Type 1: Dev and Ops Collaboration 104
  105. 105. Type 2: Fully Shared Ops Responsibilities 105
  106. 106. Type 3: Ops as Infrastructure-as-a- Service 106
  107. 107. Type 4: DevOps as an External Service 107
  108. 108. Type 5: DevOps Team with an Expiry Date 108
  109. 109. What should we use? 109
  110. 110. 110
  111. 111. Neal Ford 111
  112. 112. Innovation curve 112
  113. 113. Technology radar 113
  114. 114. Rings Hold Assess Trial Adopt • • • • 114
  115. 115. Quadrants 115
  116. 116. Radar example 116
  117. 117. Radar example 117
  118. 118. Future is here! The future is already here ? it's just not very evenly distributed. William Gibson “ 118
  119. 119. Where do we aim? 119
  120. 120. Where is the industry going?120
  121. 121. 121
  122. 122. Simon Wardley 122
  123. 123. Maps Visual Context Position, anchor and movement Components • • • • 123
  124. 124. Maps Navigation Learning Strategy Situational awareness • • • • 124
  125. 125. Maps 125
  126. 126. 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! • • • • 126
  127. 127. Thank you! 127127
  128. 128. 128

×