Downloaded 46 times
Uploaded byFrancesco Garavaglia
Introduction to DevOps
This document provides an introduction to DevOps. It defines DevOps as a movement to improve collaboration between development and operations teams. The document outlines reasons for DevOps including reducing lead time and improving feedback. It discusses DevOps principles like continuous integration and delivery. It also shares statistics on benefits organizations see from DevOps like reduced deployment times and incidents. The presentation ends with inviting any questions.
More Related Content
Similar to Introduction to DevOps
Introduction to DevOps
- 1. Introduction to DevOps F.Garavaglia Vers. 1.0 / November 2017
- 2. I am FrancescoGaravaglia o over 10 years of experience in IT consulting companies. o Took part in large scale projects (Energy Markets, Bank, Insurance) o Pay attention to Software architecture and Business value o Photographer o High-Aggressive-I-eat-you-German-Shepherd-Protected-by You can find me at Francesco.garavaglia@gmail.com Hello!
- 3. Agenda ◉What is DevOps? ◉Onceupon a time ◉Why DevOps? ◉How to start DevOps? ◉DevOps, Finally ◉DevOps Stats ◉Q/A
- 4.
- 6. “ “It’s a movementof people who think its time for change in the IT industry – time to stop wasting money, time to start delivering great software and building systems that scale and last” Patrick Debois
- 7.
- 10. a true story OnceUpon a Time
- 11. Once Upon atime, in 2013
- 14. Once Upon atime
- 15.
- 16. Why Lead Time DEV OPS Feedback Wallof Confusion Shorten
- 17.
- 18. Why does itmatter?
- 19. Why does itmatter?
- 20. How to startDevOps?
- 21.
- 22.
- 25.
- 26. CI is aboutwhat people do Not about what Tools they use
- 27. CI is apractice ◉ Discipline to integrate frequently ◉ Strive to make small Changes ◉ Strive to fast feedback
- 28.
- 30.
- 31.
- 32. DevOps Goals Cultural Change– Collaboration, Cooperation, Transformation to a learning Organization (Improved knowledge retention & deeper Knowledge understanding of the business Increased responsiveness to business needs (increased understanding to prioritize for feature requests from the business ability to communicate) Improved quality of the code (reduction of defects in each environment deployment & increase test coverage of the code More Agile developments (increased development capabilities for product feature) People Tecnology Process More agile change process (increased rate of acceptance for new features & visibility across the product lifecycle Improved Quality of Sofware deploy (reduction of incidents per deploy) More frequent releases (increase of velocity of product releases) Improved Visibility into IT process & requirement
- 34. Add DevOps intoDev Enhance Service Design with Operation al Knowledge ◉ Reliability ◉ Performance ◉ Security ◉ Test Them ◉ Build Feedback Loops from Production ◉ Monitoring and KPI Dashboards Culture of Responsibility: Whether your code passes test, gets deployed and stays up for users as your responsibility Make Development Better with Ops – Productionlike enviromnents – Power tooling
- 35. Accelerate Flow toProduction Reduce batch size Automated environments means identical dev / test / prod Create safety through automation ◉ Continuous Integration/Testing ◉ Automated Regression Testing ◉ Continuous Delivery ◉ Continuous Deployment ◉ Feature Flags (A/B Testing) ◉ Security Testing
- 36. Add Dev intoOps Don’t do tasks for people ◉ Build tools so they can do their own work Monitoring/logging / metrics feeds back into dev (and the business) Developers Do production support/empower ◉ ops acceptance
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44. Any questions ? Youcan find me at ◉ Francesco.garavaglia@gmail.com Thanks!
- 45.