当前位置:首页 > 报告详情

采用每月的运营审查会议作为学习练习.pdf

上传人: 鲁** 编号:615462 2025-03-03 89页 1.04MB

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

word格式文档无特别注明外均可编辑修改,预览文件经过压缩,下载原文更清晰!
三个皮匠报告文库所有资源均是客户上传分享,仅供网友学习交流,未经上传用户书面授权,请勿作商用。
本文介绍了Terry Brady作为一名软件开发者,在加州数字图书馆的Merritt团队中,如何将月度运营审查会议作为一种学习实践。面临新的运营责任,他们的团队采纳了DevOps方法,使开发者能够执行操作职能,而不是成为全职系统管理员。文章详细描述了三个关注领域:容量规划、软件依赖审查和错误日志。通过定制的审查脚本,他们能够识别性能瓶颈、软件漏洞和管理问题。团队通过这些会议加强了对安全、成本和日志数据的理解,并获得了同事和管理层的支持。此外,他们还提出了未来可能探索的问题,如服务功能的重复次数、云提供商的表现等。
"如何通过月度运营审查提高团队学习能力?" "如何在多云存储环境中进行容量规划和性能优化?" "如何通过软件依赖审查和错误日志分析确保软件安全性和稳定性?"
客服
商务合作
小程序
服务号
折叠