Jesse Pretorius d5a9f025b8 Separate build and install stage
In order to ensure that the build tasks are entirely skipped
when a package venv is re-used, the build and install stages
are split.

The ability to re-use venvs is also now able to be toggled.
Disabling this feature would set the build to always happen,
catering to environments where a service venv is always
deployed to the same folder (eg: stateless hypervisors with
squashfs partitions).

The ability to set constraints, etc is changed to a generalised
set of arguments that can be passed to the pip install task.
2018-03-23 11:57:09 +00:00
2018-03-23 11:57:09 +00:00
2018-03-23 11:57:09 +00:00
2018-03-09 17:50:21 +00:00
2018-03-23 11:57:09 +00:00
2018-03-09 17:50:21 +00:00
2018-03-09 17:50:21 +00:00
2018-03-09 17:50:21 +00:00
2018-03-09 17:50:21 +00:00

Team and repository tags

image

OpenStack-Ansible python_venv_build

This Ansible role prepares a python venv for use in OpenStack-Ansible.

Documentation for the project can be found at:

https://docs.openstack.org/openstack-ansible-python_venv_build/latest/

The project home is at:

http://launchpad.net/openstack-ansible

Description
Ansible role to manage the building of python venvs
Readme 2.8 MiB
Languages
Python 72.5%
Shell 27.5%