How to choose tools for DevOps and Continuous Delivery - DevOps Manchester meetup


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

How to choose tools for DevOps and Continuous Delivery - DevOps Manchester meetup

  1. 1. How to choose tools for DevOps and Continuous Delivery Matthew Skelton, Skelton Thatcher Consulting DevOps Manchester meetupgroup, 2ndSeptember 2014, Manchester, UK #devopsmanc#twuknorth
  2. 2. Collaboration Learning Singleton tools Conway’s Law
  3. 3. Matthew Skelton •15 years building & operating software systems •Cybernetics + Neuroscience •control engineering •psychology •‘network’ interactions @matthewpskelton
  4. 4. PIPELINE Conference London Continuous Delivery meetupgroup (#londoncd)
  5. 5. Help orgs to adopt and sustain good engineering practices Interim CTO/Head of X, tech strategy, architecture, workshops, delivery
  6. 6. Recent clients •Tourism •Betting & gambling •Travel booking •Financial data & reporting •Healthcare
  7. 7. Common themes •Online since ~1999 •Successful in their sector •Large, central core database(s) •Non-aligned goals •Need to adopt DevOps and Continuous Delivery
  8. 8. Common needs •Technology selection ticklists •Team interactions •Collaboration opportunities •Tools as catalysts
  9. 9. Continuous Delivery •A scientific approach to changing software systems (Dave Farley) •Regular, rapid, repeatable, reliable changes
  10. 10. Continuous Delivery •Quality •Safety •Reliability •Psychology •Effectiveness
  11. 11. DevOps “Highly effective, daily collaboration between software developers and IT operations people to produce relevant, working systems” * *also QA/Testing, IT Service Desk, Programme Management, Commercial, Marketing, etc.
  12. 12. Not DevOps “Automation” “Build & Release” “Infrastructure Development” “System Administration”
  13. 13. Collaboration
  14. 14. 1. Version Control
  15. 15. 2. Deployment Pipeline
  16. 16. A large online retailer •Travel sector •Since ~1999 •UK market •‘Non-core’ applications
  17. 17. Challenges were: •Limited Git skills in Service team •Manual deployments •‘Snowflake’ servers •No CI •Risks: security, automation, etc
  18. 18.
  19. 19. What we did •Built a walking skeleton pipeline •Modelled security roles and stages •Included manual steps (at first) •Walked people through steps •Finally: opened firewall so everyone could see the UI
  20. 20. Results •Security: happy •Service team: relieved (& happy) •Developers: won over (& happy) •Business: surprised (& happy)
  21. 21. 3. Log Aggregation
  22. 22. LogStash •ElasticSearch+ LogStash+ Kibana •ELK •In Production, Pre-Prod, Test •On developer machines!!!
  23. 23.
  24. 24. Collaboration & tool choice Value collaboration as a key criterion Orthogonal to main purpose (?) “How does [the use of] this tool help people to collaborate?”
  25. 25. Learning
  26. 26. Learning & tool choice Bring people with you Appreciate current skills Prefer achievable gains now Avoid fear of too-scary tools
  27. 27. Singleton tools (or the ‘Prize Bull’ approach)
  28. 28. Singleton tools •Special database server •Costly log aggregation •Costly monitoring •Server configuration
  29. 29.
  30. 30. “Better features”? Optimise globally across the teams that need to collaborate
  31. 31. Singleton tool Breaks feedback (learning) loop from Production Makes CI/CD more difficult Underestimates value of collaboration and learning
  32. 32. Conway’s Law
  33. 33. Mel Conway, 1968 “organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations”
  34. 34. DevOps Topologies
  35. 35. DevOps Topologies
  36. 36. DevOps Topologies
  37. 37. DevOps Topologies
  38. 38. Conway & Tool Choice See the organisation as a system Separate tools for separate teams Shared tools for collaborative teams
  39. 39. Conway’s Law •Allan Kelly -@allankellynet •
  40. 40. How to choose tools for DevOps Value collaboration aspects Avoid a learning mountain: evolve tooling Avoid Production-only tools Consider Conway’s Law (this list is incomplete!)
  41. 41. Further reading HighOps Operability eBook Build Quality In
  42. 42. Thank you / @matthewpskelton HT: @Squire_Matt, @alan_parkinson
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.