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.

La La Land of DevOps Integration - Madrid DevOps Febrero 2018

108 views

Published on

21/02/2018 "La La Land of DevOps Tools Integration" por Manuel Pais (@manupaisable)
https://www.meetup.com/madrid-devops/events/247459841/
madrid.devops.es

Published in: Engineering
  • Be the first to comment

La La Land of DevOps Integration - Madrid DevOps Febrero 2018

  1. 1. La La Land of DevOps Integration Manuel Pais @manupaisable | manuelpais.net Madrid DevOps Feb 2018 21 Feb 2018, Madrid ES
  2. 2. Continuous Delivery (Tooling) (Anti-)Patterns Manuel Pais @manupaisable | manuelpais.net Madrid DevOps Feb 2018 21 Feb 2018, Madrid ES
  3. 3. Today 1. DevOps integration: two camps 2. Pattern #1: Best of breed tools 3. Pattern #2: Pipeline = workflow 4. Pattern #3: Own your golden logs
  4. 4. About me Manuel Pais MS Software Eng @manupaisable manuelpais.net me@manuelpais.net DevOps and Delivery Consultant Focused on teams and flow
  5. 5. DevOpsTopologies.com
  6. 6. releasabilitybook.com Upcoming book: Team Guide to Software Releasability by Chris O’Dell & Manuel Pais
  7. 7. Today 1. DevOps integration: two camps 2. Pattern #1: Best of breed tools 3. Pattern #2: Pipeline = workflow 4. Pattern #3: Own your golden logs
  8. 8. “integrating various tools in software delivery is very hard” “a toolchain is a design pattern that everybody can agree on” https://www.infoq.com/articles/tool-integration-hard-truth https://www.infoq.com/interviews/interview-damon-edwards-qcon-2014
  9. 9. Integrated DevOps Tool In the left corner…
  10. 10. Integrated DevOps Toolchain In the right corner…
  11. 11. Integrated DevOps Toolchain Integrated DevOps Tool
  12. 12. Quick setup Familiar, consistent UI Less to worry about Integrated DevOps Tool
  13. 13. Long term ownership Best tool for (each) job Update tools independently Integrated DevOps Toolchain
  14. 14. tool choices… are trade-offs
  15. 15. the problem is not being aware of those trade-offs
  16. 16. some patterns become extremely hard with integrated tools…
  17. 17. Today 1. DevOps integration: two camps 2. Pattern #1: Best of breed tools 3. Pattern #2: Pipeline = workflow 4. Pattern #3: Own your golden logs
  18. 18. Integrated DevOps Toolchain
  19. 19. single-purpose tools need APIs to survive
  20. 20. Integrated DevOps Tool
  21. 21. Integrated DevOps Toolchain
  22. 22. Integrated DevOps Toolchain
  23. 23. Integrated DevOps Toolchain
  24. 24. a flexible toolchain standardizes practices, not tools
  25. 25. Integrated DevOps Tool
  26. 26. Integrated DevOps Tool
  27. 27. tooling should evolve when YOU need it
  28. 28. Limit blast radius
  29. 29. tightly coupled tooling
  30. 30. tightly coupled tooling
  31. 31. tightly coupled tooling
  32. 32. tightly coupled tooling
  33. 33. limit blast radius
  34. 34. poorly understood concepts
  35. 35. poorly understood concepts
  36. 36. Today 1. DevOps integration: two camps 2. Pattern #1: Best of breed tools 3. Pattern #2: Pipeline = workflow 4. Pattern #3: Own your golden logs
  37. 37. what’s missing?
  38. 38. what’s missing? we tend to care about technical bits only…
  39. 39. Integration Tests Functional Tests Performance Tests Operational Acceptance PROD
  40. 40. painful bottlenecks in team interactions
  41. 41. bottlenecks = silos time is lost in queues, not execution
  42. 42. automating hand-offs requires trust… which in turn requires time
  43. 43. breaking down silos is HARD!
  44. 44. we need to design pipelines with our users in mind, just like with our apps
  45. 45. Amy, the Product Owner
  46. 46. Amy, the Product Owner
  47. 47. non-technical stakeholders are part of delivery too
  48. 48. pipeline = (real) workflow highlight bottlenecks => build bridges trust requires time => automate gradually not just technical => include everyone
  49. 49. pipeline = (real) workflow highlight bottlenecks => build bridges trust requires time => automate gradually not just technical => include everyone
  50. 50. pipeline = (real) workflow highlight bottlenecks => build bridges trust requires time => automate gradually not just technical => include everyone
  51. 51. Today 1. DevOps integration: two camps 2. Pattern #1: Best of breed tools 3. Pattern #2: Pipeline = workflow 4. Pattern #3: Own your golden logs
  52. 52. 111.222.333.123 HOME - [01/Feb/1998:01:08:39 -0800] "GET /bannerad/ad.htm HTTP/1.0" 200 198 "http://www.referrer.com/bannerad/ba_in tro.htm" "Mozilla/4.01 (Macintosh; I; PPC)"
  53. 53. the problems with logs
  54. 54. the problems with logs too much information information hiding
  55. 55. the problems with logs information hiding
  56. 56. the problems with logs integrated tools information hiding
  57. 57. the problems with logs too much information
  58. 58. difficult to use log aggregation to diagnose pipeline issues with an integrated DevOps tool
  59. 59. https://www.infoq.com/articles/why-test-logging
  60. 60. information hiding should not be the reason why you can’t diagnose
  61. 61. the problem with error messages
  62. 62. generic error messages
  63. 63. generic error messages “VM could not be started”
  64. 64. generic error messages “VM could not be started” “Deployment failed”
  65. 65. without correct error information you can’t diagnose/improve
  66. 66. time between failures time to repair old view of the world
  67. 67. time between failures time to repair new view of the world
  68. 68. time to repair = time to diagnose + time to fix
  69. 69. time to repair = time to diagnose (80) + time to fix (20)
  70. 70. log aggregation own your logs quickly find correlated events don’t depend on generic error messages reduce time to diagnose
  71. 71. Today 1. DevOps integration: two camps 2. Pattern #1: Best of breed tools 3. Pattern #2: Pipeline = workflow 4. Pattern #3: Own your golden logs
  72. 72. Tomorrow tooling choices are trade-off choices
  73. 73. Tomorrow tool chain ownership supports evolution
  74. 74. Tomorrow visualize real workflow to break down silos
  75. 75. Sources • Manuel Pais and Matthew Skelton, 2017, ‘Continuous Delivery Anti-Patterns’, https://dzone.com/articles/continuous-delivery- anti-patterns • Betty Zakheim, 2017, ‘How Difficult Can It Be to Inte- grate Software Development Tools? The Hard Truth’, https://www.infoq.com/articles/tool-integration-hard-truth • Damon Edwards, 2014 ‘DevOps is an Enterprise Concern’, https://www.infoq.com/interviews/interview-damon-edwards-qcon-2014 • Don G. Reinertsen, 2009, ‘The Principles of Product Development Flow: Second Generation Lean Product Development’ https://www.youtube.com/watch?v=L6v6W7jkwok
  76. 76. thank you Manuel Pais @manupaisable me@manuelpais.net
  77. 77. La La Land of DevOps Integration Manuel Pais @manupaisable | manuelpais.net Madrid DevOps Feb 2018 21 Feb 2018, Madrid ES

×