DevOps.pptx

Complete information about "Devops" in the form of PPT.

1. Fundamentals of DevOps: Need of DevOps Architecture Deployments Orchestration Instance of Applications DevOps Delivery Pipeline DevOps Eco system. DevOps adoption in projects: Technology aspects Agiling Capabilities Tool Stack Implementation People aspect and Processes

2. DevOps

3. Traditional Development The Inventors Create new features and functionality in “dev” environment Occasionally deliver new product to operators, along with instructions May incorporate feedback from operators in future deliveries Rewarded for delivering new features The inventors are responsible for changing the system 8

4. Traditional Operations The Mechanics Receive new product from developers to be installed and operated Expected to keep production systems up and running Track problems, deployment failures, and system outages May provide feedback to the inventors for future consideration Penalized for downtime 9 The mechanics are responsible for keeping the system in operation

5. Need for DevOps

6. Benefits of DevOps

7. DevOps orchestration is the automation of numerous processes that run concurrently in order to reduce production issues and time to market, while automation is the capacity to do a job or a series of procedures to finish an individual task repeatedly. Many people believe that DevOps orchestration is just merging several jobs into a larger script. DevOps orchestration services include such jobs into a process or workflow, which may involve many automated tasks and stages, and resources to streamline the entire workflow or process. DevOps Orchestration

8. DevOps Orchestration

9. DevOps Architecture

10. Deployment Strategy in DevOps

11. A deployment strategy is any technique employed by DevOps teams to successfully launch a new version of the software solution they provide. These techniques cover how network traffic in a production environment is transitioned from the old version to the new version. What Is a Deployment Strategy ?

12. In this type of deployment strategy, the new version of the software runs alongside the old version. Note that you can also refer to this as red/black deployment strategy in some cases. Here , the stable or the older version of the application is always blue or red, while the newer version is green or black. After the new version has been tested and certified to meet all the requirements, the load balancer automatically switches the traffic from the older version to the newer version. Blue/Green Deployment

13. Blue/Green Deployment

14. The deployment team sets up the new version and then gradually shifts the production traffic from the older version to the newer version. For example, at a point in time during the deployment process, the older version might retain 90% of all traffic for the software while the newer version hosts 10% of the traffic. This deployment technique helps the DevOps engineers test the stability of the new version. Canary Deployment

15. Canary Deployment

16. The ramped deployment strategy gradually changes the older version to the new version. Unlike canary deployment, the ramped deployment strategy makes its switch by replacing instances of the old application version with the instances from the new application version one instance at a time. You can also call this method the rolling upgrade deployment strategy. When developers replace all instances of the older version, they shut down the older version. The new version then controls the whole production traffic. Ramped Deployment

17. Ramped Deployment

18. In A/B testing deployment, developers deploy the new version alongside the older version. However, the new version is only available to a subset of users. These users are selected based on specific conditions and parameters the engineers choose. These parameters can be the user’s location, type of device, UI language, and operating system. A/B Testing Deployment

19. A/B Testing Deployment

20. DevOps Delivery Pipeline

21. 36 User Commits Merge code B u il d Unit t e st/c o v e r ag e Code Review Log Issues D e p l oy A Pipeline is a chain of tasks that can be automated Integration tools use pipelines to perform tasks repetitively and continuously The process is called Continuous Integration (CI) Pipelines keep work flowing forward in our DevOps system

22. Pipeline Stages Code Done Unit Tests I n t eg r a t e Acceptance Testing Deploy to P r odu c t i o n 86 Continuous Delivery A uto Manual A uto A uto Continuous Deployment Code Done Unit Tests I n t eg r a t e Acceptance Testing Deploy to P r odu c t i o n A uto A uto A uto Au t o Code Done Unit Tests Integrate Continuous Integration A uto A uto

23. DevOps Eco System

24. DevOps adoption in Projects

25. 40 B u siness D e v End Users Ops What is the minimum viable product? Is it profitable? Do we have the capability to build it and maintain it?

26. Breaking the Silos: Communication, Collaboration, Integration 48 How can dev help system stability? How can ops help accelerate feature delivery? We can build cross-functional teams around “knowledge overlaps” – people with experience on both sides and “Ops Devs” Co mm un ic a t i o n Integration Collaboration Development Operations

27. Breaking the Silos: Dev and Ops 49 De v elop m ent O perat i ons Ops can anticipate how new f u n c t i onali t y will effect production Dev can respond to bugs and deployment failures quickly Dev and Ops can work together to permanently remove root causes of bugs and failures Ops trusts dev will provide good code Dev trusts ops will put code in prod quickly Visibility enables “trust but verify”

28. Breaking the Silos: Communication, Collaboration, Integration 50 Co mm un ic a t i o n Integration Collaboration Development B u s ine s s Operations

29. Breaking the Silos: Dev, Ops, and Business 51 De v elop m ent Business O pe r at i ons Business better understands capability for changes to features and functionality Dev can better incorporate needs of the business and customers into new development

30. Breaking the Silos: Dev, Ops, and Business 21 De v elop m ent Business O pe r at i ons Business better understands operational capabilities Ops understands better how to support business goals

31. Agiling Capabilities in DevOps

32. Tool Stack Implementation in DevOps

33. People, Process and Products