Update systemd tasking service files to use new Pulp 3 locations
Now that the tasking system is up and running, we'd like to get those services working automatically via systemd. In order to do that, we should take the existing systemd unit files and update them to use the new paths.
Here are the unit files related to the tasking system in pulp 2:
The reserved resource worker service files are created by the manage_workers script:
Here are the current updated app invocations in Pulp 3, which hopefully won't change before we start this task:
# celery beat /usr/bin/celery beat -A pulp.tasking.celery_instance.celery -S pulp.tasking.services.scheduler.Scheduler # resource manager worker /usr/bin/celery worker -A pulp.tasking.celery_app -n resource_manager@<i> -Q resource_manager -c 1 --events --umask 18 --pidfile=/var/run/pulp/resource_manager.pid --heartbeat-interval=30 # reserved resource workers /usr/bin/celery worker -n reserved_resource_worker-<i>@<hostname> -A pulp.tasking.celery_app:celery -c 1 --events --umask 18 --pidfile /var/run/pulp/reserved_resource_worker-<i>.pid --heartbeat-interval=30
Systemd provides an "instancing" mechanism that we could potentially use for the reserved resource workers, if we'd like get away from using the "manage_workers" script, documented here:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html (look for
getty.service@ and the meaning of the %i expansion in unit files)
Once these unit files are in place, the ansible dev playbook will need to be updated to install these unit files and start/stop these services using the aliases defined in its
#7 Updated by dalley over 2 years ago
I just want to note that the app invocations have, indeed, changed. Make sure to use the form of the ones in the current tree instead of the ones described in this issue. I believe the only difference is that the heartbeat interval is no longer specified.
re: "Here are the current updated app invocations in Pulp 3, which hopefully won't change before we start this task:"
#9 Updated by fdobrovo over 2 years ago
Yeah I think I have seen it removed from the current systemd files. Also one thing that came into my mind and I don't know how to solve it. It would be nice to specify requirements, such as when starting the worker ensure that the broker is started or resource manager is running. But I'm thinking in our dev environment we may want to not run such things.
Please register to edit this issue