Ansible role to manage the building of python venvs
d169906c68
1. Variables have been renamed to make it easier to understand their purpose. 2. Unnecessary variables have been removed. 3. The role no longer caters to installing pip packages on the host. This should never be necessary - if it is, then something should do so beforehand. 4. The expected versions of pip/virtualenv are documented and a check has been added to ensure that they exist. 5. The handler has been named to make debug logs less confusing. 6. The default storage path for venvs/wheels is no longer opinionated. If paths based on distro/architecture are required then different paths should be provided to the role. Change-Id: I9eb96e9db22f918b00456af943d81f66050107ce |
||
|---|---|---|
| defaults | ||
| doc | ||
| handlers | ||
| meta | ||
| releasenotes | ||
| tasks | ||
| tests | ||
| vars | ||
| zuul.d | ||
| .gitignore | ||
| .gitreview | ||
| bindep.txt | ||
| LICENSE | ||
| README.rst | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
| Vagrantfile | ||
Team and repository tags
OpenStack-Ansible python_venv_build
This Ansible role prepares a python venv for use in OpenStack-Ansible.
The role requires the following to be present prior to execution:
- pip >= 7.1 (to support using the constraints option)
- virtualenv >= 13.0.0 (to support using the no-pip, no-setuptools, no-wheels options)
Use-cases
This role is built to cater to the following use-cases:
- # Execute a build against a build host, then serve the venvs from a web
-
server.
- # Execute a build against the first host in a group, then serving the
-
venvs from the deployment host.
References
- Documentation for the project can be found at:
-
https://docs.openstack.org/openstack-ansible-python_venv_build/latest/
- The project home is at: