Cleanup requirement and set ignore_basepython_conflict = True
in tox to avoid python version conflict warning which going
to be error in future.
Change-Id: Ia4ce42a20417d69efd50ef563aabd8cffbb7b346
The ironic-python-agent coreos images are unsupported and are
anticipated to be removed from the tarballs.openstack.org site.
In advance of this, we need to remove references to these images.
Change-Id: Ifb402418d7962cf507b190e028a59b94ad5d46ac
* Use storyboard instead of launchpad since this project uses
storyboard. This fixes the "Report a bug" link.
* Remove unneeded configuration bits for doc building, the
defaults of openstackdocstheme are fine.
Change-Id: Id7513b245d1b4eac09f717a7f47469fd7bb4d3b5
Clearly not very user friendly at the moment. We probably want to
include these files as part of test.
Change-Id: Ib6ed0e68b55a98920cbaf3e8ec828901b4b9ed9f
Story: 2004291
Task: 37810
In Kayobe hosts which are part of a Nova cell can be managed via the
existing controller and compute groups. However, since Nova Cells are
configured via group vars in Kolla Ansible we need some way of setting
these. We could pass vars through to Kolla Ansible host vars using
`kolla_overcloud_inventory_pass_through_host_vars` but the list of
variables which may be set on a per cell basis is large and undefined.
This change allows the user to directly specify Kolla Ansible group vars
as part of Kayobe config, allowing the deployment of Nova Cells by
Kayobe to be largely unchanged from the procedure documented in Kolla
Ansible.
Change-Id: I2695034d36936fcc77a4828c67f9552155781dd6
Story: 2004291
Task: 37804
Kolla ansible switched its database backup support to mariabackup from
xtrabackup due to incompatibilities. See
https://bugs.launchpad.net/kolla/+bug/1843043 for details.
Change-Id: Ib95771f09fd6d5e71a2af471de47f811e1cab88b
Related-Bug: #1843043
Story: 2006952
Task: 37634
Kolla Ansible Train introduces support for TLS encryption of the
internal API. This change introduces support for internal API encryption
in Kayobe.
The following new variables are introduced:
* kolla_enable_tls_internal
* kolla_internal_tls_cert
* kolla_internal_fqdn_cacert
Also only set kolla_*_fqdn_cacert in globals.yml if set.
Change-Id: If432afde374fe247d09c952e110c9567e17daea1
Story: 2006959
Task: 37649
On Ubuntu sys.prefix is set to '/usr' even though pip will install
packages to '/usr/local' when not using a virtualenv. This change fixes
the detection in this instance. Non standard install locations are not
currently supported.
Change-Id: I214e11e7d099d1b39041fdc6b91002e1929d9c00
Story: 2005510
Task: 30620
Hopefully this provides access to relevant information without breaking
the flow.
Change-Id: I40b71cdf782dda6971dafb5894670c30e446ccb0
Story: 2004337
Task: 37387
Diskimage builder supports specifying a list of packages to install via
-p. We currently support this for the root image, but not IPA images.
This change adds a new configuration option, 'ipa_build_dib_packages',
that should be a list of additional packages to install in locally built
IPA images. This affects the following commands:
kayobe seed deployment image build
kayobe overcloud deployment image build
This depends on
https://github.com/stackhpc/ansible-role-os-images/pull/25.
Also adds an example to the documentation for the equivalent option for
root image.
Change-Id: I04191d9541894b6a264e966c9ecb1056e0edade4
Story: 2006855
Task: 37446
Kolla ansible train adds a new command, kolla-ansible deploy-containers,
that will only deploy containers, and skips registration, bootstrapping
and configuration.
This change adds a new 'kayobe overcloud service deploy containers'
command to make use of the new kolla-ansible command.
Change-Id: I999dfe4b1d082bc88148f54b236644abcbd96a5a
Story: 2006951
Task: 37633
Ideally we will fix these issues, but documenting them is a good first
step.
Change-Id: I9a840005d62b974f0681ac39e1ff02ae3ff0120e
Story: 2004967
Task: 29410
Also reorder upgrade documentation to make it clear that configuration
migration is something that should be done as a preparatory task.
Change-Id: I97ada3c6fd94a9ab7b5add97e90717f2a56bc8f3
Story: 2006677
Task: 36953
If the kayobe overcloud provision command is executed with overcloud
ironic nodes without names, cloud-init will fail with the following
Traceback when the deployed image boots:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 447, in find_source
if s.get_data():
File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 132, in get_data
self._get_standardized_metadata())
File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 110, in _get_standardized_metadata
'local-hostname': self.get_hostname(),
File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 317, in get_hostname
if util.is_ipv4(lhost):
File "/usr/lib/python2.7/site-packages/cloudinit/util.py", line 544, in is_ipv4
toks = instr.split('.')
This is a bug [1] in cloud-init. The symptom is that hosts provision
successfully, but are not accessible via SSH. A solution is to ensure
that all nodes are named.
Until we have a release of CentOS with the cloud-init fix included, we
should at least mention this limitation in our documentation.
[1] https://bugs.launchpad.net/cloud-init/+bug/1852100
Change-Id: If54f56fb9f0b626d9fae80db622b0feeae5464b9
Story: 2006832
Task: 37405
The :project-doc: format is part of the openstackdocstheme, and allows
us to link to the same release of the documentation for other projects,
without having to keep our links in sync.
Change-Id: Ifff2fd2d4e3680a9a757d77928acf84b7e5a3dd7
1. Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.
2. Cleanup the folders before run commands
[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
Change-Id: Ib3133820a3d3ca3027ea2f9bc9b6907929cff8ed
While not proper documentation, this should help people follow the ZTP
model.
Change-Id: If84a472826110bce151109ce80e70e1cef2a8177
Story: 2006640
Task: 37389
This is to resolve the following issue in CI:
c/_cffi_backend.c:15:17: fatal error: ffi.h: No such file or directory
#include <ffi.h>
^
compilation terminated.
error: command 'gcc' failed with exit status 1
----------------------------------------
ERROR: Command errored out with exit status 1: /home/zuul/kayobe-venv/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-PV3WhJ/cffi/setup.py'"'"'; __file__='"'"'/tmp/pip-install-PV3WhJ/cffi/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-ZvlZVY/install-record.txt --single-version-externally-managed --compile --install-headers /home/zuul/kayobe-venv/include/site/python2.7/cffi Check the logs for full command output.
Change-Id: I1bd724be7dc77058870f37cb1c9404472fa466ca
see: https://zuul.opendev.org/t/openstack/build/c20a316a699b4073abf75960634ebfcd
