Actions
Task #3078
closed
pulp 3 ansible installer does not create a systemd unit file for the webserver
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
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
.
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 executingpulp-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