Project

Profile

Help

Task #3078

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

Added by dkliban@redhat.com about 2 years ago. Updated 6 months ago.

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

100%

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

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.

Associated revisions

Revision cafd0171 View on GitHub
Added by Ichimonji10 about 2 years ago

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

History

#1 Updated by dkliban@redhat.com about 2 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

#2 Updated by Ichimonji10 about 2 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.

#3 Updated by amacdona@redhat.com about 2 years ago

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

#4 Updated by dkliban@redhat.com about 2 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.

#5 Updated by amacdona@redhat.com about 2 years ago

  • Groomed changed from No to Yes

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

#6 Updated by amacdona@redhat.com about 2 years ago

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

#7 Updated by jortel@redhat.com about 2 years ago

  • Sprint/Milestone set to 46

#8 Updated by Ichimonji10 about 2 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.

#9 Updated by amacdona@redhat.com about 2 years ago

  • Status changed from NEW to ASSIGNED

#10 Updated by Ichimonji10 about 2 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.

#11 Updated by Ichimonji10 about 2 years ago

  • Status changed from ASSIGNED to MODIFIED
  • % Done changed from 0 to 100

#12 Updated by bmbouter over 1 year ago

  • Sprint set to Sprint 27

#13 Updated by bmbouter over 1 year ago

  • Sprint/Milestone deleted (46)

#14 Updated by johnsharp about 1 year ago

I'm not persuaded we should run the django webserver with systemd. Possibly this should hold up until the point that we have apache or nginx. We ought to do it thusly until further notice. When we include nginx or httpd, we will make essay writing company systemd unit documents for them too. The client should pick which one they needs.

#15 Updated by BeckySpencer 12 months ago

I'm not sure if you need to start the Django web server with Systemd. This should perhaps be supported if we have Apache or Nginx. We have to do it until further notice. If we add plugin or httpd, we will also text blast and documents for the system division of the company. The customer must choose the one he needs.

#16 Updated by SMSAPI 7 months ago

Any software application or website-based business and services can send out digital receipts to customers after a sale. This is simply done by connecting the website to a mass texting service using a [[https://www.thetexting.com/sms-api/]] so users can get these receipts in the form of SMS.

#17 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#18 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF