Download as PPSX, PPTX
Uploaded byMatthew Jones
DevOps
The document discusses the roles and relationships between development (Dev) and operations (Ops) teams, and introduces the DevOps approach. It notes that traditionally there has been a disconnect between Devs and Ops that results in inefficiencies. DevOps aims to bridge this gap through a collaborative mindset and practices like automating infrastructure provisioning and deployments, implementing continuous integration/delivery, monitoring metrics, and breaking down silos between teams. Specific tools mentioned that support DevOps include Puppet for configuration management and Autobahn for continuous deployment.
More Related Content
![Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day3-cfd-251120170304-ddef8112-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Full-Stack Development] The Modern Stack: Building Web & AI Appli...](https://cdn.slidesharecdn.com/ss_thumbnails/fs-themodernstackbuildingwebaiapplicationswithserverless-251124030844-388cf04f-thumbnail.jpg?width=640&height=640&fit=bounds)
DevOps
- 1.
- 2. Dev or Ops?6Days after a successful deployment, the server experiences high load.
- 3. Dev or Ops?Thereis an issue with the build server.Code isn’t building.
- 4. Dev or Ops?Softwareis deployed to the test environment.You can’t login to the application.
- 5.
- 6. “It works onmy machine...”
- 7. “It’s not theserver, it’s your code.”
- 8. What is therole of Dev and Ops?
- 9. What are theroles of Devs and Ops?DevCreate changeAdd or modify featuresOpsCreate stabilityCreate or enhance services
- 10. What are theroles of Devs and Ops?DevCreate changeAdd or modify featuresOpsCreate stabilityCreate or enhance services
- 11. We Have AProblem...
- 12. The ProblemDisconnect betweenthe groups
- 13. Results in conflictand inefficiencies
- 14. Devs don’t deployconsistent software
- 15. Ops are motivatedto resist change
- 16.
- 17. Operations process isStaticAnd we are missing the point of it all...
- 18. We are allhere to ENABLE business
- 19. So What’s AllThis Change?
- 20. ChangeIs required forbusinessDoesn’t mean outagesShould be exploited and not feared
- 21. Change shouldn’t meanfire fighting
- 22. DevOps To TheRescue!
- 23. What is DevOps?“DevOpsis an approach to bridge the gap between agile software development and operations” – agileweboperations.comCollaborative Mindset of Devs and OpsIt’s what Agile is to software developmentC.A.M.S.
- 24.
- 25. CultureRelationshipsEngage early, engageoftenBust Silos TMBe openStop finger pointingEradicate “last-mile syndrome”
- 26. CultureCommunicationTalk is cheap(get out of your chair)Involve each other in core processes and decisionsAsk QuestionsDon’t say “no”Invite everyone to stand-ups and retrospectives
- 27.
- 28. AutomationMachines are reallygood at doing the same task over and overConsistent and Known StateFast and Efficient5 mins/day = 2.6 days/year
- 29. AutomationWhat can beautomated?BuildsDeploymentsTestingsMonitoringSelf-healingSystem rolloutsSystem configuration
- 30.
- 31. MetricsCapture, learn, improve. Assists in:Capacity PlanningTrend AnalysisFault FindingSimple as saving Tomcat access infoPlotted on a graph over time
- 32.
- 33.
- 34. SharingShare IdeasShare MetricsOps:Give devs shell accessDevs: See what technology can be leveraged
- 35.
- 36. BeforeTalk about functionalrequirements
- 37. Talk about non-functionalrequirements
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45. MetricsDuringCommunicationSource ControlAutomate BuildsAutomateTestsAutomate Deployments (Dev, Test and Prod)Collate App and System Metrics
- 46. AfterReleaseRetrospective MeetingsContinue toRun TestsMonitor Applications and SystemsIssues (Yes, they do happen)Post Mortem Meetings
- 47. What are wedoing?
- 48.
- 49.
- 50. Automated System Admin101Puppet Lives Here
- 51. Configuration Management ToolOpenSource (FTW!)Infrastructure Is CodeConfidence of System StateLather, Rinse, Repeat...Puppet
- 52. nodedefault {includesudoincludentpincludessh}nodeproject-dev01inheritsdefault {includejdk6include tomcat55include fonts}nodeproject-test01inheritsdefault {include jdk6include tomcat6include fonts}
- 53. classsudo {package {["sudo"]:ensure => latest, }file { "/etc/sudoers":owner => root,group => root,mode => 440,source => "puppet:///files/sudo/sudoers",require => Package["sudo"]; }}
- 54.
- 55. AutobahnContinuous Deployment ToolDevelopedIn-HouseAutomates Deployment ProcessGrabs Builds from HudsonDeploys to App Server
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62. Ask yourself “Ismy work creating business value?”More Info?Podcasts
- 63.
- 64.
- 65.
- 66.
- 67.
- 68.
- 69.
- 70. Google Groups: agile-system-administration,devopsQuestion Time
Editor's Notes
- #13 Problem is engrained into usDevelopment-centric folks tend to come from a mindset where change is the thing that they are paid to accomplish. The business depends on them to respond to changing needs. Because of this relationship, they are often incentivized to create as much change as possible.Operations folks tend to come from a mindset where change is the enemy. The business depends on them to keep the lights on and deliver the services that make the business money today. Operations is motivated to resist change as it undermines stability and reliability. How many times have we heard the statistic that 80% of all downtime is due to those self-inflicted wounds known as changes?as it undermines stability and reliability - Ops are keeping them from deliveringChangeCulture
- #20 DevOps has been broken down into four categories.CAMS, which I am going to go into detail.
- #22 Culture is created from these differences between dev and opsDevelopment Complete is not Live, Production, Make-Us-Millions
- #25 AKA less human error16mins/day over 30 people = 250days/year