Project

Profile

Help

Story #6793

[Epic] As a pulp_installer user, I can install Pulp from RPMs

Added by mdepaulo@redhat.com 5 months ago. Updated 3 months ago.

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

60%

Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

This was previously attempted: https://github.com/pulp/pulp_installer/pull/188

but is now requested by galaxy_ng devs rather than katello devs.

The goal is an alternate install mode for the installer: distro packages (RPMs or debs) rather than PyPI. Although debs may not be fully implemented or tested at this time.

It is assumed that the RPMs (at this time) do not have any significant amount of scriptlets that would replace configuration functionality of the installer.

Also, the following situation needs to be addressed:

  1. Users install pulp from RPMs using the installer.
  2. Users run dnf update and update Pulp.
  3. Whether they re-run the installer or not, the handlers Collect static content and Restart all Pulp services do not get run. This differs from foreman-installer, which is designed to handle this situation: they require users to re-run it after dnf update.

Subtasks

Story #6794: As a pulp_installer user, I can specify a repo full of RPMs to install Pulp fromCLOSED - CURRENTRELEASE

Actions
Story #6795: As a pulp_installer user, I can specify the names of the RPMs to install fromCLOSED - CURRENTRELEASE

Actions
Task #6796: Create CI for installing Pulp from RPMsCLOSED - CURRENTRELEASE

Actions
Task #6942: Update galaxy_ng docs for the pulp_installer install-from-rpm supportNEW

Actions
Story #7007: As a user, I do not have to worry about Pulp being accidentally upgraded and broken by external dnf updatesNEW

Actions

Related issues

Related to Pulp - Issue #7255: pulp_installer via RPM does not account for pulp_install_dirCLOSED - CURRENTRELEASE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision 184f1235 View on GitHub
Added by Mike DePaulo 4 months ago

As a pulp_installer user, I can install Pulp from RPMs

Heavily adapted from "allow installing pulp from packages"

https://github.com/pulp/pulp_installer/pull/188

Includes:

  1. Dropping the fixed repo from the old PR.
  2. Add var pulp_pkg_repo (currently only yum/dnf)
  3. Finish cleaning up pulp_webserver_static_dir
  4. Many new variables, but still using the overall pulp_install_plugins.
  5. Testing upgrades with new images on quay (can't truly test until RPM updates are issued)
  6. Cron/branch CI: Adding py38 testing
  7. PR CI: Move upgrade testing from py37 to py38, and testing from RPMs on py37.
  8. Deduplicating the tasks for checking plugins for nginx/apache snippets.
  9. Using pulp_django_admin_paths list var because RPMs often use different names for django-admin.
  10. Note: Rest of tasks should be package manager independent.
  11. pulp_upgraded_manually variable in case users ran yum update
  12. package only variables in seperate section of the pulp README.md.

fixes: #6793

Includes these subtasks implemented: re: #6794 re: #6795 re: #6796 (It was easiest to implement them all in one PR.)

Revision 184f1235 View on GitHub
Added by Mike DePaulo 4 months ago

As a pulp_installer user, I can install Pulp from RPMs

Heavily adapted from "allow installing pulp from packages"

https://github.com/pulp/pulp_installer/pull/188

Includes:

  1. Dropping the fixed repo from the old PR.
  2. Add var pulp_pkg_repo (currently only yum/dnf)
  3. Finish cleaning up pulp_webserver_static_dir
  4. Many new variables, but still using the overall pulp_install_plugins.
  5. Testing upgrades with new images on quay (can't truly test until RPM updates are issued)
  6. Cron/branch CI: Adding py38 testing
  7. PR CI: Move upgrade testing from py37 to py38, and testing from RPMs on py37.
  8. Deduplicating the tasks for checking plugins for nginx/apache snippets.
  9. Using pulp_django_admin_paths list var because RPMs often use different names for django-admin.
  10. Note: Rest of tasks should be package manager independent.
  11. pulp_upgraded_manually variable in case users ran yum update
  12. package only variables in seperate section of the pulp README.md.

fixes: #6793

Includes these subtasks implemented: re: #6794 re: #6795 re: #6796 (It was easiest to implement them all in one PR.)

History

#1 Updated by mdepaulo@redhat.com 5 months ago

  • Description updated (diff)

#2 Updated by mdepaulo@redhat.com 5 months ago

  • Description updated (diff)

#3 Updated by mdepaulo@redhat.com 5 months ago

  • Description updated (diff)

#4 Updated by mdepaulo@redhat.com 5 months ago

  • Description updated (diff)

#5 Updated by Anonymous 4 months ago

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

#6 Updated by Anonymous 4 months ago

  • % Done changed from 0 to 100

#7 Updated by fao89 3 months ago

  • Sprint/Milestone set to 3.5.0

#8 Updated by fao89 3 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

#9 Updated by mdepaulo@redhat.com 3 months ago

  • Related to Issue #7255: pulp_installer via RPM does not account for pulp_install_dir added

Please register to edit this issue

Also available in: Atom PDF