c7d3889bd8
Since lockdown is really just a form of specific pip configuration and since the pip_install role already does some pip configuration, it seems logical and desirable for these functions to take place in the same role. This change should pave the way for a simplification of role dependencies and the removal of explicit pip_lockdown role usage with various playbooks that will already have a dependency on pip_install. Change-Id: Ia0fc276c2b501f16d4acf73bbbcad6f80804628e |
||
---|---|---|
defaults | ||
doc | ||
files | ||
meta | ||
releasenotes/notes | ||
tasks | ||
templates | ||
tests | ||
.gitignore | ||
.gitreview | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
Vagrantfile | ||
other-requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
OpenStack pip install
- tags
-
openstack, pip, install, cloud, ansible
- category
-
*nix
This role will install pip using the upstream pip.
- name: Install pip and lock it down
hosts: host_name
user: root
roles:
- role: "pip_install"
pip_upstream_url: https://bootstrap.pypa.io/get-pip.py
tags:
- "pip-install"