Downloaded 15 times
Uploaded byGil Zilberfeld
An agile introduction to DevOps
This document discusses DevOps principles and practices. It introduces DevOps as a culture emphasizing collaboration between software developers and IT professionals to automate software delivery and infrastructure changes. It then covers various DevOps topics like continuous integration, deployment, monitoring and product validation practices. It also provides examples of applications that could benefit from a DevOps pipeline and asks the reader to design such pipelines.
More Related Content
Similar to An agile introduction to DevOps
More from Gil Zilberfeld
An agile introduction to DevOps
- 1.
- 2. @gil_zilberfeld Hello! I AM GILZILBERFELD www.gilzilberfeld.com www.everydayunittesting.com www.fastee.im @gil_zilberfeld
- 3.
- 4. @gil_zilberfeld DevOps A culture, movementor practice that emphasizes the collaboration and communication of both software developers and other information- technology professionals while automating the process of software delivery and infrastructure changes.
- 5.
- 6.
- 7.
- 8. @gil_zilberfeld DevOps A culture, movementor practice that emphasizes the collaboration and communication of both software developers and other information- technology professionals while automating the process of software delivery and infrastructure changes.
- 9.
- 10.
- 11.
- 12.
- 13. @gil_zilberfeld The new stuff Newcomplex problems (Cloud, Serverless) Environments all the way down Governance and risk (“You can’t do that!”) We trust automation Better tools (Docker, Puppet, Chef)
- 14.
- 15. @gil_zilberfeld New questions What isrelease management? What is a version? What is a feature? What is an environment? When is it ready for release? How do we fix it when it fails?
- 16.
- 17. @gil_zilberfeld Working software Developed Tested Does whatwe want Does what the user wants Incrementally adds value
- 18.
- 19. @gil_zilberfeld PRINCIPLES Minimize risk Minimize waste Earlyfeedback You can also split your content PRACTICES Source control Branching Continuous integration Unit and integration tests How do we do develop it?
- 20.
- 21. @gil_zilberfeld PRINCIPLES Minimize risk Minimize waste Earlyfeedback You can also split your content PRACTICES Source control Branching Continuous integration Automatic package Automatic deploy Unit and integration tests E2E tests “Non-functional” tests How do we do test it?
- 22.
- 23. @gil_zilberfeld PRINCIPLES Minimize risk Minimize waste Earlyfeedback You can also split your content PRACTICES Branching Separate environments Continuous integration Automated sanity tests Automatic package Automatic deploy Functional tests E2E tests “Non-functional” tests How do we do test it?
- 24.
- 25. @gil_zilberfeld The App Manual testsuite takes a week to run Data preparation for testing takes 7 hours Single development environment No actual customers Everyone steps on everyone else
- 26. @gil_zilberfeld The App Design apipeline from development to pre- production with the following goals: Quickest feedback Reliability
- 27.
- 28.
- 29.
- 30. @gil_zilberfeld PRINCIPLES Minimize risk Early feedback Youcan also split your content PRACTICES Version management “Side by side” deploy Continuous deployment Canary releases Post-deployment testing Rollback and roll-forward How do we do ship it?
- 31.
- 32. @gil_zilberfeld PRINCIPLES Minimize risk Minimize waste Youcan also split your content PRACTICES Production monitoring Chaos monkeys Reports on KPIs How do we do monitor it?
- 33.
- 34. @gil_zilberfeld PRINCIPLES Minimize risk Minimize waste Earlyfeedback You can also split your content PRACTICES Feature toggles Versioning MVPs Data extraction A/B testing How do we do product validation?
- 35.
- 36. @gil_zilberfeld The App The Appis live! We think people interested in hi-tech gadgets will bring us the big bucks We want to run a bucket load of experiments We also have mobile versions, not just web
- 37. @gil_zilberfeld The App Design thepipeline from dev to production with the goals: Quick feedback Do not interrupt production Describe risks mitigations, capabilities, and issues
- 38.
- 39.
- 40.
- 41.
- 42. @gil_zilberfeld Thanks! ANY QUESTIONS? You canfind me at: @gil_zilberfeld http://www.GilZilberfeld.com http://www.EverydayUnitTesting.com http://www.fastee.im
Editor's Notes
- #8 Simple to explain, hard to implement