UploadLanguage (EN)Support
BusinessMobileSocial MediaMarketingTechnologyArt & PhotosCareerDesignEducationPresentations & Public SpeakingGovernment & NonprofitHealthcareInternetLawLeadership & ManagementAutomotiveEngineeringSoftwareRecruiting & HRRetailSalesServicesScienceSmall Business & EntrepreneurshipFoodEnvironmentEconomy & FinanceData & AnalyticsInvestor RelationsSportsSpiritualNews & PoliticsTravelSelf ImprovementReal EstateEntertainment & HumorHealth & MedicineDevices & HardwareLifestyle
Upload
Sign in
HA
Uploaded byHawkman Academy
PPTX, PDF9,065 views

Introduction to DevOps

DevOps is a movement to change how IT is done by promoting collaboration between development and operations teams. It aims to reduce waste and improve delivery of software by making development and operations processes more efficient through automation, monitoring, and communication. The DevOps philosophy advocates enhancing software design with operational knowledge, building feedback loops from production into development to improve systems, and fostering a culture of shared responsibility. Key DevOps practices include accelerating the flow of changes to production through continuous integration, delivery, and deployment; adding development practices to operations like automated testing; and empowering developers to do production work to break down barriers between teams. DevOps uses tooling throughout the development and operations process to measure and monitor systems and provide feedback.

Software◦
Downloaded 814 times
1 / 73
2 / 73
3 / 73
4 / 73
5 / 73
6 / 73
7 / 73
Most read
8 / 73
9 / 73
10 / 73
11 / 73
12 / 73
13 / 73
14 / 73
15 / 73
16 / 73
17 / 73
18 / 73
19 / 73
20 / 73
Introduction to DevOps
What is DevOps?
What is DevOps? “It’s a movement of 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
DevOps Philosophy
2008 2009 2011 2013 2015+ Patrick Debois John Allpaw Paul Hammond Cameron Haight Gene Kim
Why DevOps?
Why does it Matter?
How to start DevOps?
Tonight…
Add Ops into Dev • Enhance Service Design with Operation al Knowledge – Reliability – Performance – Security – Test Them • Build Feedback Loops from Production – Monitoring and KPI Dashboards – Postmortems • Foster Culture of Responsibility – Whether your code passes test, gets deployed and stays up for users us your responsibility • Make Development Better with Ops – Productionlike enviromnents – Power tooling
Accelerate Flow to Production • 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
Add Dev into Ops • 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) • Blameless incident postmortems • Developers Do production support/empower ops acceptance
DevOps Toolchain
DevOps Trends
DevOps Toolchain
Questions?
References • Gene Kim’s Visible Ops • Tom Limoncelli’s The Practice Of Cloud System Administration • Gene Kim’s The Phoenix Project (modeled on Goldratt’s The Goal) • Jez Humble’s Continuous Delivery • Michael Nygard’s Release It! • Gene Kim’s The DevOps Cookbook (coming soon-ish) • Various Mary and Tom Poppendieck Lean Software Development Books • Velocity Conference (velocityconf.com) • DevOpsDays Unconferences – There’s one near you! (devopsdays.org) • DevOps Weekly newsletter (devopsweekly.com) • DevOps Café Podcast (devopscafe.com) • The Twelve Factor App (12factor.net) • The Agile Admin (theagileadmin.com) • Somkiat Pulsungnoen DevOps 101