T90668: Replace custom server.js with service-runner makes Parsoid use service-runner as its run library, which changes may things around how it is started and run. We need to remove the automatic BC update job for Parsoid because of it. Additionally, the Parsoid beta hosts shouldn't be Zuul/Jenkins slaves any more.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Remove beta-parsoid-update-eqiad from mediawiki/services/parsoid | integration/config | master | +0 -42 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T53494 Use Beta cluster as a true canary for code deployments (epic) | |||
| Open | None | T87220 Minimize infrastructure differences between Beta Cluster and production | |||
| Resolved | yuvipanda | T86644 Remove all ::beta roles in puppet | |||
| Resolved | hashar | T86633 Unify ::production / ::beta roles for *oid | |||
| Resolved | • mobrovac | T124989 Move all Node.JS services to Jessie and Node 4 | |||
| Resolved | akosiaris | T135176 Migrate Parsoid cluster to Jessie / node 4.x | |||
| Resolved | • mobrovac | T109926 [keyresult] Migrate all Service team owned services to scap | |||
| Resolved | • mobrovac | T120103 Deploy Parsoid with scap3 | |||
| Resolved | • GWicke | T114549 Offer a combo of Parsoid and RESTbase in a single process using service-runner for severely memory-constrained environments | |||
| Resolved | Arlolra | T114854 Fix Parsoid heap usage statistics | |||
| Resolved | • mobrovac | T90668 Replace custom server.js with service-runner | |||
| Resolved | • mobrovac | T140218 Remove automatic beta updates for Parsoid |
Event Timeline
Comment Actions
I removed role::ci::slave::labs and role::parsoid::beta from deployment-parsoid0[56].
Comment Actions
So if I understand properly Parsoid is going to move to the generic service runner system. For beta we would:
- remove deployment-parsoid as a slave of Jenkins
- drop the jenkins job that auto-update it (beta-parsoid-update-eqiad) and remove it from the repo postmerge pipeline in Zuul
- clear up the puppet class role::parsoid::beta
Out of scope of this task but: how are you going to keep it up-to-date on beta?
Comment Actions
Change 298701 had a related patch set uploaded (by Mobrovac):
Remove beta-parsoid-update-eqiad from mediawiki/services/parsoid
Comment Actions
Done by removing the roles from deployment-parsoid0[56]
- drop the jenkins job that auto-update it (beta-parsoid-update-eqiad) and remove it from the repo postmerge pipeline in Zuul
Done in the above patch
- clear up the puppet class role::parsoid::beta
It is likely that this role will go away. A WIP patch for that is in progress.
Out of scope of this task but: how are you going to keep it up-to-date on beta?
The Parsoid folks are ok with manually updating beta for now. We do need to find a generic way of deploying to beta for services that use service-runner / service::node (but that's definitely out of scope here).
Comment Actions
Mentioned in SAL [2016-07-13T08:33:49Z] <hashar> removing deployment-parsoid05 from the Jenkins slaves T140218
Comment Actions
Change 298701 merged by jenkins-bot:
Remove beta-parsoid-update-eqiad from mediawiki/services/parsoid
Comment Actions
The Parsoid folks are ok with manually updating beta for now. We do need to find a generic way of deploying to beta for services that use service-runner / service::node (but that's definitely out of scope here).
If that can be handled with scap3 we eventually want to get a generic Jenkins job that will run on deployment-tin, does the git pull and scap deploy from there.
I have deployed the CI change, dropped the slave from Jenkins and delete the job.