Project

Profile

Help

Story #6795

closed

Story #6793: [Epic] As a pulp_installer user, I can install Pulp from RPMs

As a pulp_installer user, I can specify the names of the RPMs to install from

Added by mdepaulo@redhat.com almost 4 years ago. Updated almost 4 years ago.

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

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

The current design for this is, given a list of plugins like:

pulp_install_plugins:
  pulp-file:
    version: 0.4.0
  pulp-ansible:
    upgrade: true

To install the plugin RPM packages according to their names (the dictionary keys), and ignore the upgrade / version variables.

Details likely to change, depending on the needs of users & the repos:

  1. Ignoring the upgrade / version subvariables
  2. allowing for possible dashes or underscores substitution
  3. Adding another subvariable for users to override the names of the plugins to install, such as:
  pulp-ansible:
    package_name: MyCoolSCL-11-pulp-ansible

Also, similar logic applies to the pulpcore package itself, and its vars.

Also, for dependency resolution, we should let the distro's package manager handle this. So we should probably have 1 atomic task equivalent to: dnf install pulpcore pulp-file pulp-ansible Rather than: dnf install pulpcore dnf install pulp-file dnf install pulp-ansible

dnf would give an error if there is any dependency error at all.

Also available in: Atom PDF