1、ADOPTING MONTHLYOPERATIONAL REVIEWMEETINGS AS A LEARNINGEXERCISETerry Brady,So?ware Developerhttps:/ PURPOSEDevelopment team needed to take on newoperational responsibilitiesOur approach to this challengeWhat we learned2MERRITT TEAM is a Digital Preservation Service that is run bythe MerrittCaliforn
2、ia Digital Library3.1MERRITT SYSTEM1.4 PB of Cloud Storage(3 distinct providers)4.5M Objects188M Files7 microservices,26 ServersMySQL,ZooKeeperhttps:/ ROLES1 Product Manager3 So?ware Developers1 DevOps engineer(supporting multiple teamswithin our department)3.3OUR BACKGROUNDSPrimarily so?ware develo
3、pment(Java,Ruby,SQL)One developer has a Systems Admin backgroundOur DevOps engineer has a Systems AdminbackgroundCDL has 3 full-time Systems Administratorssupporting multiple departments3.4DEVOPS ADOPTION AT CDLWe are adopting a DevOps approachNeed to empower developers to performoperational functio
4、nswithout turning them into full time SystemsAdministrators3.5IMMEDIATE NEEDS FOR THEDEVELOPMENT TEAM TO TAKEONCapacity PlanningSo?ware End of LifeSo?ware Vulnerabilities/DependenciesProactive Error Discovery3.6NOT OUR EXPERTISENeed to learn functions that have not traditionallybeen part of so?ware
5、developmentWhile still primarily focusing on so?waredevelopment3.7DISCUSSIONDoes this challenge sound familiar?How has your team addressed this challenge?3.8OUR APPROACH4.1LETS FIGURE IT OUT TOGETHER!Hold each other accountableLearn togetherHopefully make it more interestingIteratively improve our a
6、pproach4.23 AREAS OF FOCUSCapacity Planning-Server PerformanceSo?ware Dependency ReviewVulnerabilitiesEnd of LifeProactive Error Log Tracking4.3OUR PROCESSSchedule time once a month for each area of focusLimit to 30 minutesAccomplish as much as we canFigure it out togetherDocument learningsBuild a s