Task #3078: pulp 3 ansible installer does not create a systemd unit file for the webserver - Pulp

Actions

Send by e-mail Copy link

Task #3078

closed

pulp 3 ansible installer does not create a systemd unit file for the webserver

Added by dkliban@redhat.com about 7 years ago. Updated about 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

Ichimonji10

Category:

Installer - Moved to GitHub issues

Sprint/Milestone:

3.0.0

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Yes

Sprint Candidate:

Yes

Tags:

Sprint:

Sprint 27

Quarter:

Description

The user should be able to start the webserver using systemd. The pulp3_systemd ansible role already creates a systemd file for the pulp_workers. However, it fails to create one for the web server.

Actions

Copy link

Updated by dkliban@redhat.com about 7 years ago

Subject changed from pulp 3 ansible installer does not create a systemd unit file the webserver to pulp 3 ansible installer does not create a systemd unit file for the webserver

Actions

Copy link

Updated by Ichimonji10 about 7 years ago

This issue can be solved by creating a unit named e.g. pulp-manager-runserver in ~/.config/systemd/user/. It can then be managed with commands like systemctl --user start pulp-manager-runserver. Also see loginctl(1), especially the stuff related to lingering.

Actions

Copy link

Updated by amacdona@redhat.com about 7 years ago

I'm not convinced we should run the django webserver with systemd. Maybe this should wait until we have apache or nginx.

Actions

Copy link

Updated by dkliban@redhat.com about 7 years ago

We should do it this way for now. When we add nginx or httpd, we will create systemd unit files for them also. The user will have to choose which one she wants.

Actions

Copy link

Updated by amacdona@redhat.com about 7 years ago

Groomed changed from No to Yes

I'm convinced. We aren't guaranteeing this for production.

Actions

Copy link

Updated by amacdona@redhat.com about 7 years ago

Tracker changed from Issue to Task
% Done set to 0
Sprint Candidate changed from No to Yes

Actions

Copy link

Updated by jortel@redhat.com about 7 years ago

Sprint/Milestone set to 46

Actions

Copy link

Updated by Ichimonji10 about 7 years ago

Assignee set to Ichimonji10

I'm taking the liberty of assigning this to myself, both because I'm working on it, and also because this issue is on the sprint for the benefit of QE.

Actions

Copy link

Updated by amacdona@redhat.com about 7 years ago

Status changed from NEW to ASSIGNED

Added by Ichimonji10 about 7 years ago

Revision cafd0171 | View on GitHub

Run the development Pulp 3 webserver for testing

Make the pulp-3-dev-{os} jobs run the development webserver after Pulp 3 has been installed, so that it can be smashed. Do so by simply executing pulp-manager runserver … as the "pulp" user. This is a hacky and awful solution, because among other things, it makes process management a pain. Stopping the dev webserver requires manually hunting down and killing processes. Restarting the dev webserver is worse.

However, this is intended to be a temporary solution that's only in place until the devs figure out how Pulp 3 is supposed to run. When a solution that integrates with Apache/Nginx/LightTPD/etc is devised, this can be dropped.

See: https://pulp.plan.io/issues/3078

closes #3078

Actions

Copy link

#10

Updated by Ichimonji10 about 7 years ago

See: https://github.com/pulp/pulp_packaging/pull/442

The proposed solution doesn't make use of systemd at all. It's totally doable, but the proposed solution is even simper. For an exmaple of what the systemd-based solution might look like, see master...Ichimonji10:pulp-3-webserver-systemd.

Actions

Copy link

#11