Page MenuHomePhabricator

Split group1 so that Commons and Wikidata aren't in the general group1, but their own buckets
Open, Needs TriagePublic0 Estimate Story Points

Description

Problem:

  • group1 includes almost all wikis which aren't Wikipedias, including two of our largest and most complex wikis, Wikidata and Commons.
  • Each time we bump the train to group1, some of the fallout happens at a scale that is unfeasible to manage and hinders investigation.
  • Problems most often hit Wikidata, which is exceptionally complex and has a number of unique features.
  • The train rolling late on Wednesday to Wikidata means we have to rush to try to fix it.

Proposal:

  • Split group1 into group0b for Wikidata, group1a for most wikis, and group1b for Commons.
  • Try to roll out the Wikidata change on Tuesdays during European hours so that the Wikidata team are around, after the main group0 deployment
  • Roll out the group1s on Wednesday, maybe 15 minutes apart, to allow things to settle between deployments.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMay 15 2019, 7:24 PM

Intuitively, I think Wikidata would benefit from being deployed during European mornings. This way we get ample coverage from WMDE developers. The actual promotion is a single command, the devil lies in monitoring the log. I am definitely volunteering in training WMDE people to assist in the Wikidata promotion, if we go that way.

For commonswiki, I do not know. Maybe it is fine to just deploy it with group1, but I think we sometime have to roll back just that wiki.

greg added a subscriber: greg.

Putting in Next for us to review next month

mmodell added a subscriber: mmodell.
brennen added a subscriber: brennen.Dec 7 2019, 2:35 AM
brennen moved this task from Backlog to Watching on the User-brennen board.

Adding WMDE folks. Ping us if you need anything

I generally like this proposal, however, I dislike the growing complexity of the groups and their naming. I don't currently have a better proposal than what's listed in the task description so this comment is worth < $0.02

Try to roll out the Wikidata change on Tuesdays during European hours so that the Wikidata team are around, after the main group0 deployment

Wouldn't this mean either Wikidata will get the new train before test wikis (in case the train is being rolled in US time) or we need to cut the branch and deploy for test wikis in European time no matter what?

Try to roll out the Wikidata change on Tuesdays during European hours so that the Wikidata team are around, after the main group0 deployment

Wouldn't this mean either Wikidata will get the new train before test wikis (in case the train is being rolled in US time) or we need to cut the branch and deploy for test wikis in European time no matter what?

Not sure. Note that the actual /cut/ of the weekly branch is planned to be entirely scripted (T196517: Automate weekly branch cut) so making the group0 / group0b deploys a European thing isn't asking anything like as much of time commitment as running the train right now is.