Download as PDF, PPTX
Introduction to devops 201604
- 1. Introduction to devops 2016-04-14 Gerardde Vos @gr4rd gjdevos@gmail.com
- 2. Agenda ● Me ● Onedefinition of devops ● Old or new? A bit of history ● Another definition of devops ● Where? ● CALMS ● Takeaways
- 3.
- 4. One definition ofdevops “Devops is a cultural and professional movement, focused on how we build and operate high velocity organizations, born from the experiences of its practitioners.” - Adam Jacob, CTO & founder of Chef http://readwrite.com/2015/07/29/devops-people-not-technology/
- 5. It is notnew
- 7. It is new In2009 things came together: ● “Lean Startup” by Eric Ries ● Agile infrastructure thread by Patrick Debois et al. ● "10+ Deploys Per Day: Dev and Ops Cooperation at Flickr" by John Allspaw and Paul Hammond https://www.youtube.com/watch?v=LdOe18KhtT4 ● “Continuous Delivery” by Jez Humble and David Farley http://itrevolution.com/the-convergence-of-devops/
- 8.
- 9.
- 10.
- 11. Another definition ofdevops “Devops is co-evolution of practice with the evolution of an underlying activity.” - Simon Wardley Researcher @ Leading Edge Forum Previously: VP Cloud at Canonical, CEO at Fotango http://blog.gardeviance.org/2015/04/devops-weve-been-here-before-we-will-be.html
- 12.
- 13.
- 14.
- 15.
- 17. CALMS ● Culture ● Automation ●Lean ● Measurement ● Sharing http://itrevolution.com/devops-culture-part-1/ (https://www.chef.io/blog/2010/07/16/what-devops-means-to-me/)
- 18.
- 20.
- 21. Design for failure “Thebest way to avoid failure is to fail constantly.” http://techblog.netflix.com/2010/12/5-lessons-weve-learned-using-aws.html
- 22. “Waking up developersat 3am is a great feedback loop: defects get fixed very quickly” MobBrowser case study http://www.slideshare.net/realgenekim/devops-kanban-meet-up-32212
- 23. “You built it,you run it” - Werner Vogels CTO Amazon https://queue.acm.org/detail.cfm?id=1142065
- 25.
- 26.
- 27. Blameless (or blame-aware)post-mortems “Take a hard look at how the accident actually happened, treat the engineers involved with respect, and learn from the event.” https://codeascraft.com/2012/05/22/blameless-postmortems/
- 28. Automation Continuous integration Continuous delivery Infrastructureas code --------+ Reduce risk Increase speed Usually in that order
- 31. Automation Git / VCS Automatedtesting. Test driven development etc. Deployment tooling ChatOps These document and share the decision making process and development progress.
- 32. Lean W. Edwards Deming,Henry Ford, Taiichi Ohno et al. Toyota Production System Kaizen. Continuous Improvement Muda. Remove ‘waste’
- 33.
- 34.
- 35. Measurement The feedback loop Howyou know what you are doing
- 36. “only about 1/3of ideas improve the metrics they were designed to improve.” Online Experimentation at Microsoft: http://ai.stanford.edu/~ronnyk/ExPThinkWeek2009Public.pdf
- 38. “The ability tolearn faster than your competitors may be the only sustainable competitive advantage.” - Arie de Geus Former head of Shell's Strategic Planning Group
- 39. Sharing Share discoveries andlessons. Work in the open: repositories, wikis, trackers, monitors.
- 40.
- 41.
- 42.
- 44. More Devops Meetup Amsterdam http://www.meetup.com/DevOpsAmsterdam/ DevopsdaysAmsterdam June 29, 30 & July 1st http://www.devopsdays.org/events/2016-amsterdam/ Devopsweekly.org newletter http://www.devopsweekly.com/
- 45. In short ● Devopsis just part of evolution. ● It is not for everywhere. Most powerful in the middle. ● It is not just for those with job labels of “dev” or “ops”. ● It is still young and evolving. Adapt it to your organization, department, team. ● Keep learning and improving. ● Share and enjoy!
- 46.
- 47.