Track deployment of the storage layer component of MCR. This particularly covers the necessary DB schema migration as well as beginning to use the new schema.
See also the Deployment Schedule.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| wgMultiContentRevisionSchemaMigrationStage SCHEMA_COMPAT_OLD | operations/mediawiki-config | master | +8 -0 |
Event Timeline
There are a very large number of changes, so older changes are hidden. Show Older Changes
Comment Actions
No actionables here (yet), add Schema-change-in-production when it actually is blocked on that.
Comment Actions
Well, it actually is blocked on the schema change. We can't fully deploy MCR without it. But I suppose the tag is for situations where something is blocked only on the schema change.
Comment Actions
Schema-change-in-production is used when the schema change is ready to go and further progress is blocked on the change actually being made on WMF's databases. In this case, we're still working out the details of what the change should be.
Comment Actions
@Anomie is right, adding it now would only spam us and deplay actually blocked changes. Add the DBA to tell us we will be involved in the future, as a heads up, which I already did (the Blocked external is the meaning here, not the not db team, we *will* be involved, just not yet).
Comment Actions
Change 440128 had a related patch set uploaded (by Addshore; owner: Addshore):
[operations/mediawiki-config@master] wgMultiContentRevisionSchemaMigrationStage MIGRATION_OLD
Comment Actions
This will be set to take the train on the week of the 25th of June, providing everything goes well on group0 over the coming week.
Comment Actions
Change 440128 merged by jenkins-bot:
[operations/mediawiki-config@master] wgMultiContentRevisionSchemaMigrationStage SCHEMA_COMPAT_OLD
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2018-07-16T14:22:44Z] <anomie@deploy1001> Synchronized wmf-config/InitialiseSettings.php: Explicitly set wgMultiContentRevisionSchemaMigrationStage to current default (T174044) (duration: 00m 50s)
Comment Actions
This is done. We still have the old fields in the database, and we still write to them. Changing that is tracked in T184615: Once MCR is deployed, drop the rev_text_id, rev_content_model, and rev_content_format fields from the revision table and T198312: Set the WMF cluster to use the new MCR-only schema.