Continuous Delivery & DevOps Specialization
- 1. Session – 1 Continuous Delivery & DevOps
- 2. What is DevOps 2 DevOps is not a tool or technology; it is an approach or culture that makes things better. How DevOps solves different problems of the traditional application— delivery cycle. It also describes how it can be used to make development and operations teams efficient and effective in order to make time to market faster by improving culture. It also explains key concepts essential for evolving DevOps culture. DevOps is a culture which aims at removing the communication barrier among the Developers and the Operations and develop trust among them. INTRODUCTION
- 3. Key Points: • Course Handout • Understanding the DevOps movement. • The waterfall model, • The agile model DevOps is short for Development and Operations It concentrates on collaboration between developers and other parties involved in building, deploying, operating, and maintaining software systems. 3
- 4. Overview of DevOps •DevOps is an agile relationship between development and IT operations •DevOps is the abbreviation for Development and Operations •The Development includes Plan, Create, Verify, and Package •The Operations include Release, Configure, and Monitor
- 5. Understanding the DevOps movement • DevOps is a blend of complex terminologies. It can be considered as a concept, culture or a movement. • Consider there are multiple environments where an application is deployed. • The following sequence of events takes place when any new feature is implemented or bug fixed: • The development team writes code to implement a new feature or fix a bug. This New code is deployed to the development environment and generally tested by the development team. • The new code is deployed to the QA environment, where it is verified by the testing team. • The code is then provided to the operations team for deploying it to the production environment. • The operations team is responsible for managing and maintaining the code.
- 6. 6 List the possible issues in this approach: •The transition of the current application build takes weeks or months. The priorities of the development team, QA team, and IT operations team are different in an organization and effective, and efficient co-ordination becomes a necessity for smooth operations. •The development team is focused on the latest development release, while the operations team cares about the stability of the production environment. •The development and operations teams are not aware of each other's work and work culture. •Both teams work separately and hence there can be a situation where both use different automation techniques. •Both teams are unaware of the challenges faced by each other and hence may not be able to visualize or understand an ideal scenario in which the application works.
- 7. Challenges for the development team: • The competitive market creates on-time delivery pressure. • They have to take care of production-ready code management and new feature implementation. • The release cycle is often long and hence the development team has to make assumptions before the application deployment finally takes place. In such a scenario, it takes more time to fix the issues that occurred during deployment in the staging or production environment.
- 8. Challenges for the operations team: • Resource contention: It's difficult to handle increasing resource demands. • Redesigning or tweaking: This is needed to run the application in the production environment. • Diagnosing and rectifying: They are supposed to diagnose and rectify issues after application deployment in isolation.
- 9. The waterfall model • The waterfall model follows sequential application design process for software development. • It comes with good control but lacks revisions. • It is a goal based development but without any scope of revision. • The waterfall model has long been used for software development. 9
- 10. The waterfall model Contd.. It has its advantages, as follows: • Easy to understand • Easy to manage—the input and output of each phase is defined • Sequential process—order is maintained • Better control It has its share of disadvantages, as follows: • No revision • No outcome or application package until all phases are completed • Not possible to integrate feedback until all phases are completed • Not suitable for changing requirements • Not suitable for long-term and complex projects 10
- 11. The waterfall model Contd.. 11
- 12. The waterfall model Contd.. 12
- 13. The Agile model: • Agile development or the agile methodology is a method of building an application by empowering individuals and encouraging interactions, giving importance to working software, customer collaboration using feedback for improvement in subsequent steps and responding to change in an efficient manner. • It emphasizes customer satisfaction through continuous delivery in small interactions for specific features in short timelines or sprints. 13
- 15. Relationship Between Agile and DevOps 15
- 16. Replace non- human steps using tools Improvethe collaboration between all the teams Automate to create a potentially shippable increment Relationship between Agile and DevOps Relationship Between Agile and DevOps
- 17. Questions 1. Define DevOps. 2. List out the challenges of Development and Operations Teams. 3. Explain Waterfall model, why is disadvantage when compared to Agile. 4. Explain Waterfall Model and list out the advantages of it. 5. Explain Agile Model and list out the advantages of it. 6. Explain the relationship between Agile and DevOps 7. Explain the Agile with and Example(Scrum)