scap deploy --service-restart doesn't affect ORES celery
Closed, DeclinedPublic
Actions

Assigned To

None

Authored By

	awight
	Dec 14 2017, 8:26 PM

Description

This is a bug in our scap configuration. scap deploy --service-restart does restart uWSGI, but not celery. We've got some stuff in the wrong place.

Event Timeline

awight created this task.Dec 14 2017, 8:26 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 14 2017, 8:26 PM

Zppix moved this task from Unsorted to Maintenance/cleanup on the Machine-Learning-Team board.Dec 15 2017, 2:10 AM

thcipriani moved this task from Needs triage to External/Watching on the Scap board.Jul 11 2018, 12:17 AM

Ladsgroup triaged this task as Low priority.Nov 26 2018, 3:00 PM

I noticed that ores/deploy has the configuration service_name: uwsgi-ores set. --service-restart will only restart services listed there. You could do something like service_name: uwsgi-ores,celery-ores-worker. This would restart both services after deployment; however, there may be additional service needs to consider that may mean that that isn't the correct course of action in all cases.

awight unsubscribed.Mar 21 2019, 4:02 PM

• ACraze moved this task from Maintenance/cleanup to Backlog/ORES on the Machine-Learning-Team board.Jan 19 2021, 10:29 PM

We are moving to Lift Wing: https://wikitech.wikimedia.org/wiki/Machine_Learning/LiftWing

I am closing old tasks related to ORES since it is being deprecated, please re-open if you feel that any work could be done on Lift Wing.

scap deploy --service-restart doesn't affect ORES celeryClosed, DeclinedPublicActions

Description

Event Timeline

scap deploy --service-restart doesn't affect ORES celery
Closed, DeclinedPublic
Actions