5f7000e185
The current ansible bootstrap process tried to pin the versions of pip, setuptools and wheel on the host and also uses inherited python packages from the host. This causes problems when the host has a version of setuptools which is cannot be changed (perhaps due to some bug) or when the host has otherwise undesirable python packages. The ansible bootstrap process only needs to be concerned with whether pip is installed and understands how to use constraints. From there we can bootstrap the venv using get-pip and completely avoid package conflicts with the host. Once Ansible is bootstrapped, the pip_install role will ensure that pip, setuptools and wheel are correctly bootstrapped and pinned across all hosts. The pip_install role now uses constraints for the initial get-pip [1], so we can also remove the list of pip pins from group_vars. We remove pip, setuptools and wheel from the requirements.txt to allow the packages on the host to be installed in the bootstrap without forcing a change of pip/setuptools/wheel at the same time (which causes failures in some circumstances). [1] https://review.openstack.org/483905 Change-Id: Ida84fb6bb726e1332f0e29ade51b67a5721f0785
15 lines
527 B
Plaintext
15 lines
527 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
pyasn1!=0.2.3 # BSD
|
|
pyOpenSSL>=0.14 # Apache-2.0
|
|
requests>=2.14.2 # Apache-2.0
|
|
ndg-httpsclient>=0.4.2;python_version<'3.0' # BSD
|
|
netaddr!=0.7.16,>=0.7.13 # BSD
|
|
PrettyTable<0.8,>=0.7.1 # BSD
|
|
pycrypto>=2.6 # Public Domain
|
|
python-memcached>=1.56 # PSF
|
|
PyYAML>=3.10.0 # MIT
|
|
urllib3>=1.21.1 # MIT
|
|
virtualenv>=13.1.0 # MIT
|