Story #3716: As a production Pulp user, I have an Ansible installer
Create the pulp3 role
The pulp3 role will use the pip module and will install a plugin generically. It will take the following variables:
name - The name of a Python library to install or the url of the remote package. As of 2.2 you can supply a list of names. It can take the following types of data:
* VCS project url
* Local path to project
- Local or remote source archive
virtualenv - An optional path to a virtualenv directory to install into. Defaults to
/usr/local/pulpenv. If unset, it will install in the system packages. If set but the virtualenv does not exist, it will be created before installing packages.
pulp_user - the user to switch to before installing
editable - defualts to no.
pulp_data_dir - defaults to '/var/lib/pulp'.
#10 Updated by dalley about 2 years ago
- Assignee changed from Ichimonji10 to dalley
There is some differences between this and the ansible-pulp3 project I suppose, which is that this is a source install (or seems to be written that way). There should be overlap but I would consider this blocked for now.
Please register to edit this issue