7a7f858ae2
Instaling and using Ansible from source for bifrost has several
drawbacks, mainly due to how Ansible's 'ansible/hacking/env-setup'
script mangles with PATH and PYTHONPATH, which complicates running it as
part of other scripts. Besides, cloning the whole repo and it's
submodules is somewhat longer.
The main reason why we were doing that at all was a necessity to install
some additional Ansible modules from newer Ansible versions, which we
dropped right into the source of Ansible code - but this does not have to
be so.
Luckily for us, all Ansible versions we target to support can load
modules from 'library' directory next to playbooks/roles,
and we already use that for 'os_ironic_facts' module.
The need to install a particular module can be assessed by running
ad-hoc 'ansible' command against localhost with the module in question
and without any arguments ('ansible localhost -m <module>'):
- if the module is available in Ansible, the stderr will contain
"changed" substring (as part of the standard module output)
- if the module is absent form Ansible, "changed" string will be absent
from stderr too, in which case we can download the module from github
directly into 'playbooks/library' directory.
This patch removes possibility of installing Ansible from source, and
always installs a released Ansible version via pip.
If not installed into venv, Ansible will be installed in user's ~/.local
directory via 'pip install --user'.
The missing but needed modules are downloaded as described above.
Some level of backward compatibility is provided:
- when the ANSIBLE_GIT_BRANCH has form of 'stable-X.Y', the
env-setup.sh script will do the next best thing and install latest
available Ansible version of X.Y.w.z
Also, ANSIBLE_PIP_VERSION can now accept a full pip version specifier:
- if ANSIBLE_PIP_VERSION starts with a digit, this exact version will be
installed (as 'ansible==X.Y.W.Z')
- otherwize this whole variable is assigned as Ansible version specifier
for pip, e.g
env ANSIBLE_PIP_VERSION="<2.2" env-setup.sh
will result in pip being called as
pip install -U "ansible<2.2"
Closes-Bug: #1663562
Change-Id: I2c9f47abbbb6740d03978f684ad2c876749655b7
20 lines
1.0 KiB
YAML
20 lines
1.0 KiB
YAML
---
|
|
prelude: >
|
|
During the Ocata cycle, a number of improvements have been made to bifrost
|
|
to improve the managability and longevity of a bifrost installation.
|
|
Coupled with a number of fixes, and improvements, users upgrading should
|
|
take the time to read the entire release notes. A few highlights are below:
|
|
|
|
* Bifrost now installs and utilizes Ansible 2.1 by default from
|
|
PyPI.
|
|
* Ironic's default of modifying a pre-existing ironic.conf upon the
|
|
installation being re-executed, has been changed to a utilize a
|
|
template file.
|
|
* Bifrost supports generating and reading from a os-client-config
|
|
``clouds.yaml`` file for obtaining credentials.
|
|
* Bifrost can now leverage authentiation, as well as install and
|
|
configure keystone if requested by the installer.
|
|
* As a number of in-tree drivers in ironic were removed this past
|
|
cycle, due to lack of third-party CI, support has been added to
|
|
enable installation of the staging drivers repository.
|