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.

Introducing DevOps

76,080 views

Published on

This ppt is an attempt to give a short intro on DevOps. This will be updated as my knowledge level also improves.

Published in: Software, Technology, Business

Introducing DevOps

  1. 1. Agile Series by NishanthintroducingDevOps
  2. 2. Agenda• What is DevOps• Why DevOps?• Addressing Delivery Challenges• Agile and DevOps – How is it connected?• DevOps vs. Release Management• When to adopt and when not to
  3. 3. What is DevOps?
  4. 4. What is DevOps?
  5. 5. What is DevOps?• DevOps (a combination of development andoperations) is a software developmentmethod that stresses communication,collaboration and integration betweensoftware developers and informationtechnology(IT) professionals thereby– Enable rapid evolution of products or services– Reduce risk, improve quality across portfolio, andreduce costs
  6. 6. What is DevOps?• DevOps integration targets product delivery, quality testing,feature development and maintenance releases in order toimprove reliability and security and faster development anddeployment cycles.• The adoption of DevOps is being driven by factors such as:• Use of agile and other development processes andmethodologies• Demand for an increased rate of production releases fromapplication and business stakeholders• Wide availability of virtualized and cloud infrastructurefrom internal and external providers• Increased usage of data center automation andconfiguration management tools
  7. 7. Principles of DevOps• Develop and test in an environment similar toproduction• Deploy builds frequently• Validate operation quality continuously
  8. 8. Why DevOps?
  9. 9. Why DevOps? – Delivery Challenges
  10. 10. Why Gaps?Dev View:• Mostly delivers features after testing indevelopment systems• Dev systems may not be same as productionsystem• Developers will have faster turn around time w.r.tfeatures• Not much concerned about the infrastructural aswell as deployment impact because of the codechanges
  11. 11. Why Gaps?Ops View:• Worries more about PSR• Rewarded mainly for uptime• Lesser turn around time w.r.t featuredeployment and testing due to large numberof dev builds coming their way• Very much concerned about theinfrastructural as well as deployment impactbecause of the code changes
  12. 12. Dev and Ops• Developers work with Ops to understand the impact ofcode changes• Developers now work more closely with production-equivalent systems• Developers focuses on metrics required by Ops teamlike PSR• Ops now have more clarity on infrastructure needs• More automation on deployment• Closely monitors the Dev – Test – Prod pipeline foreach deployment with immediate feedback• Better collaboration and communication
  13. 13. Addressing Delivery Challenges
  14. 14. Top 3 delivery challenges• Release management– Better understanding of risks, dependencies,compliance issues• Release/Deployment coordination– Better tracking of discrete activities, faster escalationof issues, documented process control and granularreporting• Release/Deployment Automation– Usually have existing automation but want to flexiblymanage and drive this automation that can be invokedby non-operations resources in specific non-production environments
  15. 15. Addressing Delivery Challenges
  16. 16. Addressing Delivery ChallengesDeployTestDevOps
  17. 17. Agile and DevOps
  18. 18. Addressing Delivery Challenges
  19. 19. Addressing Delivery ChallengesDeployTestDevOps
  20. 20. DevOps vs. ReleaseManagement
  21. 21. Agile and DevOps
  22. 22. Agile and DevOpsDeployTestBuildTestPrioritiseDesignDevOpsAgile
  23. 23. Agile and DevOps• Agile Development– Addresses the gap between customer requirements anddev + testing teams– Cross-functional teams to design, develop, and testfeatures/stories prioritised by the PO (Customer)– Focuses more on functional and non-functional readiness• DevOps– Addresses the gap between dev + testing and Ops– Automated release management– Focuses on functional and non-functional plus operationaland business readiness– Intensifies reusability and automation
  24. 24. Agile + Traditional ReleaseManagement
  25. 25. Agile + DevOpsTestDeployDevOpsBuildTestPrioritiseDesignAgileContinuous FeedbackFaster Delivery reduces riskContinuous Integration extended as Continuous Delivery
  26. 26. Continuous Integration andContinuous Delivery
  27. 27. Continuous Integration• Integrate the code changes by each developerso that the main branch remains up-to-date
  28. 28. Continuous Delivery• Taking each CI build and run it throughdeployment procedures on production orproduction-equivalent environments
  29. 29. When to adopt and When not to
  30. 30. When to adopt and when not toWhen to Adopt:• For eCommerce and other web site projects(Amazon, Flickr, Groupon,etc)• Cloud platform (IaaS and PaaS)When not to Adopt:• Mission critical applications (Banks, PowerSystems, etc)
  31. 31. Thanks!Exciting new transitions

×