Continuous Delivery - the missing parts

A talk designed to help developers understand the ecosystem needed to implement a good continuous delivery pipeline

Transcript

1. Continuous Delivery - The Missing Parts Paul Stack http://twitter.com/stack72 mail: paul@paulstack.co.uk
2. About Me Infrastructure Engineer for a cool startup :) Reformed ASP.NET / C# Developer DevOps Extremist Conference Junkie
3. Background to this talk
4. Continuous Delivery …. is a set of practices and principles aimed at, building, testing and releasing software faster and more frequently.
5. 8 principles of Continuous Delivery The process for releasing/deploying software MUST be repeatable and reliable. Automate everything! If somethings difficult or painful, do it more often. Keep everything in source control Done means “released” Build quality in! Everybody has responsibility for the release process Improve continuously
6. 4 Practices of Continuous Delivery Build binaries only once Use precisely the same mechanism to deploy to every environment Smoke test your deployment If anything fails, stop the line!
7. Has anyone read this book?
8. So continuous delivery is now 5 years old?
9. Agile Manifesto “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software"
10. Common Misconceptions
11. 1. Continuous Delivery is something only startups can achieve
12. 2. Continuous Delivery only works for NodeJS / Ruby / Go developers
13. 3. We can hire a consultant to help us implement ‘Continuous Delivery’
14. 4. A good tool will help us implement continuous delivery
15. 5. Continuous delivery is as simple as hooking github to our Azure account…..
17. “Until your pretty code is in production, making money, or doing whatever it does, you’ve just wasted your time” Chris Read @cread #LondonCI
18. But haven’t I just contradicted myself?
19. The traditional technical side of a company Developers QA SysAdmins Network Helpdesk InfoSec + lots more
21. Aren’t we supposed to be one team?
22. “How long would it take your organisation to deploy a change that involved just one single line of code? Do you do this on a repeatable, reliable basis?” Implementing Lean Software Development Mary Poppendieck
23. Value Stream Map
24. The Value Stream Map for Ops is worse….
26. The rise of DevOps…..
28. October 30 - 31, 2009 Ghent, Belgium Developers + System Administrators for 2 days = DevOpsDays
34. How does DevOps help with this type of thing?
35. ‘The 3 ways’ • Systems thinking • Amplify Feedback loops • Culture of Continual Experimentation and learning
36. The first way…
37. Understanding Work.. • Business Projects (search, UI improvements) • Internal Projects (architecture changes) • Changes (deployments, schema updates) • Unplanned work (downtime, investigations)
38. The second way…
39. We found that when we woke developers up at 2am, defects got fixed faster! -Patrick Lightbody CEO, Browsermob
40. The third way…
42. DevOps is about… Culture Automation Measurement Sharing
43. We are *all* part of the same team!
44. Metrics and Automation are key!
45. The technical side of the business post-DevOps….
47. The ops side of Continuous Delivery
48. Configuration Management
49. Immutable Infrastructure
51. Immutable Infrastructure
52. Disposable Infrastructure
53. Logging
56. Metrics
58. Monitoring
60. https://github.com/stack72/nagios-elasticsearch
61. Orchestration
63. Data Center as Code?
65. Disaster Recovery?
67. The Continuous Delivery Maturity Model
68. http://www.infoq.com/articles/Continuous-Delivery-Maturity-Model
69. The Benefits of Continuous Delivery • High Performing IT Teams are more Agile! • High Performing IT Teams can recover faster! • High Performing IT Teams can experiment more!
70. Continuous Delivery means better products for your customers!* * Customers can be internal or external
71. Questions?
72. Paul Stack @stack72