Introduction to DevOps and SRE

Introducing DevOps and SRE and their functionality into software development life cycle. How agile alliance with devops to fasten the CI/CD process and from cultural shift of devops to operational workload of SRE along with its principles.

Transcript

1. Introduction to DevOps and SRE 12-10-2019 | Mohan Pawar
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. What is DevOps ?
6. How it benefits... • Enable rapid evolution of product or services • Reduced risk, improve quality across portfolio, and reduced cost • Demand for an increased rate of production releases from applications and business stakeholders
7. Principles of DevOps • Application and End user focus • Collaboration • Performance orientation • Development speed • Service orientation • Automation • Monitor everything
8. Why DevOps ?
10. Why there is a gap b/w Dev and Ops ? Dev view: • Mostly deliver features after testing in development systems • Dev systems may or may not be identical to production systems • Developers will have faster turnaround time w.r.t. Features • Not much concerned about the infrastructural as well as deployment impact as well as code changes
11. Ops view: • Worries more about PSR (Proposing a Standards Recommendation) • Rewarded mainly for uptime • Lesser turn around time w.r.t. Feature deployment and testing due to large number of deployment coming their way • Very much concerned about infrastructure as well as deployment impact because of code changes
20. Addressing Delivery Challenges Top 3 Delivery challenges • Release Management ◦ Better understanding of risk, dependencies, compliance issue • Release/Deployment coordination ◦ Better tracking of discrete activities, faster escalation of issues, documented process control and granular reporting • Release/Deployment automation ◦ Usually have existing automation but want to flexibly manage and drive this automation that can be invoked by non-operations resource in specific non-production environments.
25. Continuous Delivery vs Continuous Deployment
26. When to adopt and when not to... When 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, Power systems, etc.)
27. Cloud Native Applications DISRUPT INDUSTRIALIZE HYPERSCALE Traffic, Data, Features CONTINUOUS DELIVERY AND DEVOPS OPEX SAVINGS (automation & utilization) ANTIFRAGILITY
28. 3 key principles of Cloud Native Applications • Build and Composed as Microservices • Packaged & Distributed in containers • Dynamically executed in the cloud
29. SLI, SLO & SLAs SLI • Request Latency • Batch throughput • Failure per request SLO Binding target for a collection of SLIs SLA
30. Resources for DevOps Practices Accelerate your application delivery lifecycle Optimize your DevOps practices and tools: Get started on your DevOps journey: aka.ms/DevOps DevOps Dimension Show on Channel 9 Continuous Improvement on your DevOps journey: aka.ms/DevOpsDimension Technical resources for Practitioners: Get access to free online training: aka.ms/DevOpsLearn DevOps Maturity Self-Assessment See where your organization is at across 7 areas: http://devopsassessment.azurewebsites.net/ Learn DevOps Practices hands-on with Parts Unlimited apps http://aka.ms/PartsHOL
31. Thank you @mohan08p /in/mohan08p @mohan08p Ask any further questions. @mohan08p