c1323f2d77
To prevent Ansible get_url module from generating SNI warnings several system packages are being installed so that system python will allow us to get pip and install it. The strategy for using system pip to install the python packages to prevent SNI warnings causes additional issues as system package pip versions may be broken in spectacular ways which prevent us from upgrading to pinned versions of each of pip, setuptools, wheel. Change-Id: I45e3eff716dba4fb2926794bc25bfb079bb328bf Closes-Bug: 1612377 |
||
---|---|---|
defaults | ||
doc | ||
files | ||
meta | ||
releasenotes | ||
tasks | ||
templates | ||
tests | ||
vars | ||
.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-Ansible pip install
This role will install pip using the upstream pip installation script. Within the installation of pip the role will create a .pip directory within the deploying user's home folder and a blank selfcheck JSON file for pip to use to keep track of versions.
It can also configure pip links that will restrict the package sources to the OpenStack-Ansible repository.
Default Variables
../../defaults/main.yml
Required Variables
None
Example Playbook
- name: Install pip and lock it down
hosts: host_name
user: root
roles:
- role: "pip_install"
pip_lock_to_internal_repo: True