381f3ffba2
Once we remove the repo build process, this needs to point to the location where wheels are served by pypiserver. For now we use this to ensure that we don't rebuild the wheels that were already built by the repo build process. It has also been found that pypiserver hangs when it encounters duplicated wheels. Change-Id: I86510cb7407e4ee69a376fc64ba5b8f5676f0bff |
||
|---|---|---|
| defaults | ||
| doc | ||
| handlers | ||
| meta | ||
| releasenotes | ||
| tasks | ||
| tests | ||
| zuul.d | ||
| .gitignore | ||
| .gitreview | ||
| LICENSE | ||
| README.rst | ||
| Vagrantfile | ||
| bindep.txt | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
README.rst
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:
- virtualenv >= 1.10 (to support using the never-download option)
- pip >= 7.1 (to support using the constraints option) in the virtualenv once it has been created.
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:
- Release notes for the project can be found at:
-
https://docs.openstack.org/releasenotes/ansible-role-python_venv_build/