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 10 months ago. Updated 28 days ago.

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

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Q1-2021

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 10 months ago

  • Description updated (diff)

#2 Updated by fao89 9 months ago

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

#3 Updated by bmbouter 6 months ago

  • Category set to Installer
  • Tags deleted (Pulp 3 installer)

#4 Updated by dkliban@redhat.com 28 days ago

  • Quarter set to Q1-2021

Please register to edit this issue

Also available in: Atom PDF