Page MenuHomePhabricator

Decommission Parsoid/JS from the Wikimedia cluster
Closed, ResolvedPublic

Description

Now that Parsoid/PHP is live on the cluster, we can start taking steps to decommission Parsoid/JS from the cluster.

However, note that nodejs is still required on scandium since rt-testing and other testing tools are still node.js based.

We can either create specific steps here or create subtasks.

Let us deploy changes and update the cluster in the new year

Event Timeline

ssastry triaged this task as Medium priority.Dec 20 2019, 7:48 AM
ssastry created this task.

Change 559705 had a related patch set uploaded (by Dzahn; owner: Dzahn):
[operations/puppet@production] conftool: remove parsoid, keep parsoid-php

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

Change 559705 abandoned by Dzahn:
[operations/puppet@production] conftool: remove parsoid, keep parsoid-php

Reason:

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

This is definitely done now.

@Jdforrester-WMF I don't think it fully is, honestly.

for example conftool-data has the old parsoid service:

eqiad.yaml: wtp1040.eqiad.wmnet: [parsoid, parsoid-php]

Also, nodejs is running:

@wtp1025:~# ps aux | grep nodejs  | wc -l
52

Ah, oops, we should clean that up, certainly.

I checked the HEAD of all git repos under /srv/deployment […]

Comparison between deploy2002 and deploy1002:

$ colordiff -U0 --text deploy2002 deploy1002 
--- deploy2002	2022-05-02 14:33:48.321048639 +0200
+++ deploy1002	2022-05-02 14:33:49.585064545 +0200
@@ -88 +87,2 @@
-/srv/deployment/parsoid/config/node_modules/events/@modules/raw.github.com/Gozala/extendables/v0.2.0/.git/srv/deployment/parsoid/config/.gitf12b09d5dfeb18c74104a5cdefc7ec4ea23a2b2a
+/srv/deployment/parsoid/config/.gitf12b09d5dfeb18c74104a5cdefc7ec4ea23a2b2a
+/srv/deployment/parsoid/config/node_modules/events/@modules/raw.github.com/Gozala/extendables/v0.2.0/.git/srv/deployment/ores/deploy/submodules/assets/.git08b9cebc5e0148ace73915a94e65a5dd0f0ba9a2

The presence of /srv/deployment/parsoid/config/node_modules looks like a left-over of Parsoid JS that probably can or should at some point be decom'ed. Leaving here as reminder and/or to clarify otherwise.

To a certain extent a duplicate of T279059 which we just closed.

Just ran across this while looking through Phabricator history. It seems all subtasks are resolved. What is left to do here?

Is decom'ing scandium part of this (at some point)? or not?

No! :) scandium is now Parsoid/PHP. AFAICT, I think this task can be resolved. But, you all should evaluate in case there are any lingering Parsoid/JS things lying around in puppet.

Change 825753 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/puppet@production] scap/dsh: remove parsoid service, replaced by parsoid-php

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

@ssastry Alright, thanks. I found a small remnant.

Change 825753 abandoned by Dzahn:

[operations/puppet@production] scap/dsh: remove parsoid service, replaced by parsoid-php

Reason:

referenced in scap configuration

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

@Dzahn If there is anything left here, I reckon we can mark it as resolved? Thank you!

Dzahn claimed this task.

@jijiki There is a small detail left but I am not going to work on it. It requires changes to scap config first.

I don't mind if it gets closed though. No strong opinion here. It depends on the definition of what belongs to "decom from the cluster".

Well.. thinking about it.. it is effectively decom'ed from the cluster, what I am talking about is remnants in repos. so... let's close it.

If anyone disagrees please just reopen.