Project

Profile

Help

Task #4770

closed

Add an ansible-pulp role to dynamically load pre-requisite roles

Added by dkliban@redhat.com almost 5 years ago. Updated over 3 years ago.

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

0%

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

Description

pulp-pre-requisites role needs to be added to the installer so that users have an opportunity to install pre-requisites for plugins such as pulp_rpm and pulp-certguard.

This role needs to look at the list of plugins being installed and check if any of them specify 'pre-requisite' key. For each pre-requisite this role finds, it needs to dynamically load the role and execute it. The role can assume that the pre-requisite roles are present in the working directory.

The pulp_rpm_prerequisites[0] role should be added as a submodule to the pulplift repo. This way when pulp_rpm is specified in the list of installed plugins, the pre-requisite role will be present.

[0] https://github.com/pulp/pulp-rpm-prerequisites

Actions #1

Updated by dkliban@redhat.com almost 5 years ago

  • Tracker changed from Issue to Task
  • % Done set to 0
Actions #2

Updated by ehelms@redhat.com almost 5 years ago

I think this ability already exists within the provided structures. You can specify a list of playbooks to the box definitions. For example, instead of what is found at:

https://github.com/pulp/pulplift/blob/master/vagrant/boxes.d/30-source.yaml#L9

You could specify:

```
....
ansible:
playbook:
- pre-playbook.yml
- main-playbook.yml
....
````

There is also what is done here:

https://github.com/pulp/pulplift/blob/4b6f8f007ceb80e9e359c60827494038f550b23a/playbooks/source-install.yml#L10-L11

Actions #3

Updated by ttereshc over 4 years ago

Actions #4

Updated by dkliban@redhat.com over 4 years ago

  • Subject changed from Add ability to specify a pre-playbook for pulplift to Add an ansible-pulp role to dynamically load pre-requisite roles
  • Description updated (diff)
Actions #5

Updated by bmbouter over 4 years ago

If that role is added to the installer itself then when pulplift's submodule upgrades to that ref it will receive it. For pulplift to use this installer feature it needs the vars pre-commented in the *-config.yml files. https://github.com/pulp/pulplift In other words this looks right except for the last line of the description (to me). What do you think?

Actions #6

Updated by dkliban@redhat.com over 4 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to dkliban@redhat.com
  • Sprint set to Sprint 57
Actions #7

Updated by dkliban@redhat.com over 4 years ago

  • Status changed from ASSIGNED to NEW
  • Assignee deleted (dkliban@redhat.com)
  • Sprint deleted (Sprint 57)
Actions #8

Updated by dkliban@redhat.com over 3 years ago

  • Status changed from NEW to CLOSED - WONTFIX

We don't use pre-req roles anymore.

Also available in: Atom PDF