Project

Profile

Help

Story #3723

closed

Story #3716: As a production Pulp user, I have an Ansible installer

Create the pulp3 role

Added by bmbouter over 6 years ago. Updated about 4 years ago.

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

100%

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

Description

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'.


Sub-issues 2 (0 open2 closed)

Story #3720: As a role user, I specify an Ansible variable that specifies the data directory Pulp will use. Defaults to '/var/lib/pulp/'CLOSED - CURRENTRELEASE

Actions
Story #3721: As a role user, server.yml behaviors are saneCLOSED - CURRENTRELEASE

Actions

Also available in: Atom PDF