Page MenuHomePhabricator

Undeploy ParsoidBatchAPI from the Wikimedia cluster
Open, Stalled, LowPublic

Description

Now that Parsoid/JS receives no traffic and is slated to be decommissioned (T241207), there is no longer any use for the ParsoidBatchAPI extension and it should be removed from the Wikimedia cluster.

Details

Related Gerrit Patches:
mediawiki/tools/release : masterStop branching ParsoidBatchAPI
operations/mediawiki-config : masterUndeploy ParsoidBatchAPI

Event Timeline

ssastry triaged this task as Medium priority.Jan 10 2020, 1:48 PM
ssastry created this task.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJan 10 2020, 1:48 PM

Change 563461 had a related patch set uploaded (by Reedy; owner: Reedy):
[operations/mediawiki-config@master] Undeploy ParsoidBatchAPI

https://gerrit.wikimedia.org/r/563461

Change 563462 had a related patch set uploaded (by Reedy; owner: Reedy):
[mediawiki/tools/release@master] Stop branching ParsoidBatchAPI

https://gerrit.wikimedia.org/r/563462

Jdforrester-WMF added a subscriber: Jdforrester-WMF.

Does this need to wait for T241207 to be finished before being done, or can we action it immediately?

Let us wait for T241207 because we do have at least one more Parsoid/JS rt test run to do on scandium -- so that our final Parsoiid/JS deb release is tested with all the minor code cleanup since we stopped traffic to it in production.

Jdforrester-WMF changed the task status from Open to Stalled.Jan 10 2020, 4:38 PM

Understood.

@cscott pointed out that our developer standalone mode references the parsoid-batch extension ( https://github.com/wikimedia/parsoid/blob/9c52e78989bed9c4b87997ea9764f340010d9510/src/Config/Api/DataAccess.php#L160 ). So, we'll have to stop using it before we do this. Probably a simple fix since performance is not a concern here.

Jdforrester-WMF lowered the priority of this task from Medium to Low.Mon, Feb 24, 5:38 PM