Project

Profile

Help

Story #5996

As a user, I can easily stop/start/restart all Pulp services on a box via a systemd multi-service app

Added by mdepaulo@redhat.com about 1 month ago. Updated about 1 month ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 3 installer
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

We should do this:
http://alesnosek.com/blog/2016/12/04/controlling-a-multi-service-application-with-systemd/

To:
1. Provide a better user experience.
2. Ensure that if the order of starting the Pulp services ever becomes significant, they are stopped/started/restarted in the right order (currently, there seems to be no significance.)
3. Accomplish code cleanup in ansible-pulp.

This will work well for when ansible-pulp eventually supports api, content, workers, and resource-managers on separate hosts. Because the app can consist of multiple services, and each service's unit file declares that they are part of it. (i.e., we won't even have to template the app's .service file to accommodate the different set of services installed per host.)

History

#1 Updated by mdepaulo@redhat.com about 1 month ago

  • Description updated (diff)

#2 Updated by fabricio.aguiar about 1 month ago

  • Tracker changed from Issue to Story
  • % Done set to 0

Please register to edit this issue

Also available in: Atom PDF