Wikimedia Release Engineering Team/Group -1/Progress reports/2024-12-19
Appearance
â week ending 2024-11-28 | Group -1 progress reports week ending 2024-12-19 |
Report on activities in the Group -1 project for the week ending 2024-12-19.
[WE6.2.6] Create design document for Group -1 deployment
[edit]If we gather feedback from QTE, SRE, and individuals with domain specific knowledge and use their feedback to write a design document for deploying and using the wmf/next OCI container, then we will reduce friction when we start deploying that container.
- Progress update
-
- Stage: Design
- Effie, Giuseppe, and Alexandros have all given initial feedback on the list of questions for Service Operations. Bryan has been asked to give more detail on the pros and cons for choosing between "push" and "pull" models of triggering an automated deployment.
- Tyler has helped share the list of questions with the Test Platform team. Additional discussion is needed with this group to more clearly enumerate the specific test collections they run against Beta Cluster wikis and evaluate which are candidates for migration to the Group -1 system.
- There is emerging consensus that the "Group -1" name will not be ideal for the deployed environment. People who are deeply familiar with the current Deployment Train process understand the logic and humor of adding a "-1" group before the current "0" starting group. The potential of confusion between "group 1" and "group -1" in both written and verbal communication however is concerning in the longer term. Currently proposed alternatives are some variation on "pretrain" or a complete relabeling of the Train's groups to avoid ambiguity, for example as "A" (this project), "B" (current group0), "C" (current group1), & "D" (current group2). Selecting a more widely supported name is now part of the work for this hypothesis.
- A goal of completing the requirements gathering and design document creation by the end of January 2025 has been set. That sounds like kind of a long time if you start counting days, but with all of the end of year holidays and vacations that date is really only about 3 working weeks from now.
- The next report on this project is expected the week of 2025-01-09. Happy holidays and a restful end of year break are wished for everyone.
- Any new metrics related to the hypothesis
-
- None
- Any emerging blockers or risks
-
- None
- Any unresolved dependencies - do you depend on another team that hasnât already given you what you need? Are you on the hook to give another team something you arenât able to give right now?
-
- Not yet
- Have there been any new lessons from the hypothesis?
-
- Not yet
- Have there been any changes to the hypothesis scope or timeline?
-
- No