Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Enabling DevOps

Enabling DevOps

This is an overview of DevOps and Cloud-Native Introduction for Kothalawala Defence Academy ( KDU ), IEEE Branch.

Avatar for Ruwan Ranganath

Ruwan Ranganath

September 27, 2021

More Decks by Ruwan Ranganath

Other Decks in Technology

Transcript

  1. PART 1/2 Enabling Adapting Your Workspace with DevOps Practices Sep

    25, 2021 KDU IEEE www.withops.com RUWAN RANGANATH Lead - DevOps Docker and Mozilla Community Lead DevOps
  2. Even before the term DevOps is coined, some companies start

    practising it. In an interview, Amazon's Werner Vogels states that their developers are also looking after day-to-day operations, interfacing with customers and collecting direct feedback. The goal is to improve quality of service. At the Agile Conference in Toronto, Andrew Shafer calls for a session titled "Agile Infrastructure". Only one person, Patrick Debois, attends this. He later meets Andrew and they together form the "Agile Systems Administration Group". Eric Ries refers to Steve Blank's book titled "The Four Steps to Epiphany". The basic idea is to release early a minimum set of features to the customer, get feedback, validate product-market fit and iterate quickly. This was the start of the Lean movement and had an influence on DevOps. Source: devopedia.org/devops Brief History How DevOps practices adopted 2006 Aug 2008 Nov 2008
  3. At the O'Reilly Velocity conference John Allspaw and Paul Hammond

    present 10+ Deploys a Day: Dev and Ops Cooperation at Flickr. Debois watches this from Belgium. Inspired by this, Patrick Debois organizes DevOpsDays in Ghent, Belgium in October. By the time the event ends, twitter hastag #DevOps becomes commonly used, giving the movement its current name. DevOpsDays is organized in Sydney, California, Hamburg and Sao Paulo. This is also the year when Jez Humble publishes his well-known book titled "Continuous Delivery". Enterprises start adopting DevOps. Source: devopedia.org/devops 2010 Jun 2009 2014
  4. Resource Page Presenting live not your thing? No worries! Record

    your Canva Presentation your audience can watch at their own pace. DevOps is a cultural, professional movement focused on how we build and operate high-velocity organizations, born from the experiences of its practitioners. DevOps is largely founded in an organization’s skillful collaboration and communication, and the culture that results. DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support. DevOps is ops who think like devs and devs who think like ops. The point of dev-ops is that developers need to learn how to create high-quality, production-ready software, and ops needs to learn that Agile techniques are actually powerful tools to enable effective, low-risk change management. Ultimately, we’re all trying to achieve the same thing – creating business value through software. The Devops movement is characterized by people with a multidisciplinary skill set - people who are comfortable with infrastructure and configuration, but also happy to roll up their sleeves, write tests, debug, and ship features.
  5. DevSecOps DevOps is NOT ENOUGH! DevSecOps is what must be

    implemented with the cybersecurity stack built-in into the DevOps pipeline. https://software.af.mil/training/devops/ atlassian.com/devops/devops-tools/devsecops-tools
  6. DevOps is about connecting people, products, and processes. Ultimately, DevOps

    is about connecting IT to business Oracle Definition
  7. This speed enables organizations to better serve their customers and

    compete more effectively in the market. DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity AWS Definition
  8. Continue to trust the process and trust yourself. an organizational

    and cultural movement that aims to increase software delivery velocity, improve service reliability, and build shared ownership among software stakeholders.
  9. Three Ways Framework From The Phoenix Project/ DevOps Handbook’s The

    First Way: Principles of Flow The Third Way: Principles of Continuous Learning The Second Way: Principles of Feedback
  10. DevOps Metrics Mean-time to recovery (MTTR): shows how long it

    would take applications in the production stage to recover from failure Mean-time to production: shows how long it takes when new code is committed into code repository Average lead-time: shows how long it would take for a new requirement to be delivered and deployed Deployment speed: shows how fast you can deploy a new version of the application between staging, test and production Deployment frequency: shows how often you can deploy a new release into production environment and testing / QA Production failure rate: shows how often software fails during production
  11. DevOps Challenges Culture Test automation Legacy systems App Complexity No

    DevOps plan Managing environments Skillset Budget Tools Leadership Support
  12. Components of a DevOps pipeline Continuous integration Continuous delivery Continuous

    deployment Continuous FeedBack Continuous Testing Contineous Monitoring Continuous Operation atlassian.com/devops/devops-tools/devops-pipeline
  13. Cloud Native Infra Independent OSS to implement and support Patterns

    than just use "tool x" Open Standards Share experience and code for generic problems “Cloud-native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds.” - CNCF SOURCE: SOFTWARE FREEDOM DAY '21 SRI LANKA According to the Cloud Native Computing Foundation (CNCF), there are at least 6.5 million cloud-native developers on the planet today
  14. Provisioning Runtime Orchestration and Management App Definition and Development Observerbility

    and analyze Monitoring Logging Tracing Alerting Chaos Engineering Database Streaming & Messaging App Definition & Image Build Continuous Integration & Delivery Scheduling and Orchestration Coordination & Service discovery Remote procedure call Service Proxy API Gateway Service Mesh Cloud Native Storage Container Runtime Cloud Native Network Automation & Configuration Container Registry Security and complience Key Management Cloud Native Landscape https://landscape.cncf.io
  15. CNCF PROJECTS Cloud Native Computing Foundation (CNCF) serves as the

    vendor-neutral home for many of the fastest-growing open source projects, Scheduling & Orchestration Coordination & Service Discovery Continuous Integration & Delivery Monitoring Security & Compliance Service Mesh Service Proxy Monitoring Application Definition & Image Build 135K+ CONTRIBUTORS 6.7M+ CONTRIBUTIONS 294.2M+ LINES OF CODE 16 GRADUATED PROJECTS 23 INCUBATING PROJECTS 59 SANDBOX PROJECTS HTTPS://LANDSCAPE.CNCF.IO
  16. RedHat survey of 1,250 IT leaders was commissioned by Red

    Hat to better understand the unique role of enterprise open source. Respondents were unaware that Red Hat was the sponsor of this research.
  17. “We spent many years building various types of infrastructure ourselves,

    including container orchestration. And obviously, none of those things have taken off the way like Kubernetes has. So, in that sense, we’re doing our best to stop building our own stuff and use much more open source or at least industry standards,” “There’s a lot of innovation that happens with open source internally, and one of the [examples] I can name — that is actually a CNCF project — that’s on my radar right now is Kubernetes,” Dave Zolotusky Senior Staff Engineer Spotify Jasmine James Developer Experience Lead and Manager for Engineering Effectiveness Twitter Source : The New Stack Makers podcast
  18. The pillars of the AWS Well- Architected Framework Source :

    AWS Cloud Security Reliability Performance Efficiency Cost Optimization Operational Excellence
  19. Operational Excellence Perform operations as code Make frequent, small, reversible

    changes Refine operations procedures frequently Anticipate failure Learn from all operational failures
  20. Security Implement a strong identity foundation Enable traceability Apply security

    at all layers Automate security best practices Protect data in transit and at rest Keep people away from data Prepare for security events
  21. Reliability Automatically recover from failure Test recovery procedures Scale horizontally

    to increase aggregate workload availability Stop guessing capacity Manage change in automation
  22. Performance Efficiency Democratize advanced technologies Go global in minutes Use

    serverless architectures Experiment more often Consider mechanical sympathy
  23. Cost Optimization Implement Cloud Financial Management Adopt a consumption model

    Measure overall efficiency Stop spending money on undifferentiated heavy lifting Analyze and attribute expenditure
  24. DevOps is about People, Process and Tools, in that order.

    Starting with tools will be the wrong way to do it. John Willis gives us the CAMS formula: Culture, Automation, Measurement, Sharing. Again, culture is critical to successful DevOps. Everything needs to be automated and measured. For measurements, establish KPIs. Mean time to recovery is an example KPI. Empathy is important to understand needs, break down silos and bring various teams together. Start small on something strategic and then apply it on a large scale across the organization. Invest in tools that give real-time visibility. Tool integration is essential. Multiple tools that don't work well together will hamper collaboration. Increase the speed of deployment. To achieve this, invest in automation and practise Agile techniques. Participate in community events and online channels to share and learn. Improve feedback at every step, whether it's build, deploy, recovery or notifications. Although DevOps is not a set of practices, the following may help newbies get into the DevOps movement