Modifies provisioning and cleaning networks in multi-tenant ironic
environments to be non-shared. Flat networks remain shared.
To apply the change to an existing environment, run 'kayobe overcloud
post configure'.
Change-Id: Ie59f0c729381e5bea112ab7f5d0c738a9488b772
Story: 2006409
Task: 36295
Kayobe uses a number of virtual environments on the remote hosts for
python dependencies such as shade, python-openstackclient, docker, etc.
By default these are stored in /opt/kayobe/venvs/. Typically we do not
provide version restrictions when installing these packages, so over the
course of time they may become stale and incompatible.
This change installs the latest version of packages allowed by OpenStack
upper constraints.
It also adds a new variable, 'pip_upper_constraints_file', to set the
upper constraints file. The existing variable
'kolla_upper_constraints_file' now defaults to the value of
'pip_upper_constraints_file'.
Change-Id: I8d2956f95bbc44b5a9e88e7569372048a62f12f5
Story: 2005923
Task: 34193
Fixes an issue where the admin-openrc.sh and public-openrc.sh files
would not be generated when preparing a new control host environment for
an existing cloud. These files are now generated during 'kayobe control
host bootstrap' if the Kolla Ansible 'passwords.yml' file exists in the
Kayobe configuration.
Change-Id: I47cc95bc4c4198532c8cfd2c105f1c7033e7b932
Story: 2001667
Task: 6713
This provides a more predictable and stable ordering for the inventory
generated via 'kayobe overcloud inventory discover'.
TrivialFix
Change-Id: Ie784b7e91cd70ed5c552723789958e32724b17a8
Juniper physical network device configuration fails when running the
following command:
kayobe physical network configure --group switches
The error is as follows:
fatal: [switch]: FAILED! => {
"msg": "Unknown host key [<key>] for [[<IP>]:830]"
}
This is due to a bug [1] in ncclient.
This patch avoids the issue by pinning ncclient to version 0.6.2 or
lower.
[1] https://github.com/ncclient/ncclient/issues/302
Change-Id: I7ecd6cd3460bea56d0ab9cb221d0ef5b5ec2d0bb
Story: 2006378
Task: 36174
There is no need to connect controllers nodes to the storage management
network by default. It should only be used by storage nodes.
Change-Id: I6fa7640658fd112aaddbe08c4af01711fb1f7916
Story: 2006273
Task: 35973
When an allocation pool range is not defined by the operator, we should
not include network and broadcast addresses in the list of IP addresses
to give to hosts.
Change-Id: Id6e14286b5eb2b767a515e7edfc56741fb8d2c78
Story: 2006267
Task: 35958
This command slightly modifies the deploy operation to first stop the
bifrost services and container if they are running.
Change-Id: If0fe1115f01738254a61c0f5460548b0d6ae6b9a
Depends-On: https://review.opendev.org/667630
Story: 2006050
Task: 34743
Version v1.1.0 includes useful updates needed for supporting the
PowerConnect 6248, such as support for 'enable' and quirky differences
in the CLI.
Change-Id: I1a9e0471f34183c85002de30c395b82baa5f3ef4
If using the kayobe --limit <hosts> argument, only those hosts matching
the limit will have an inventory generated for Kolla Ansible. This can
cause problems for Kolla Ansible, even when using a similar limit via
--kolla-limit <hosts>, since it gathers facts for all hosts, and expects
all host variables to be defined.
This change adds a new 'ignore_limit' argument to the playbook running
methods, which allows us to override and ignore the --limit argument
provided by the user, ensuring that we always run these plays.
Change-Id: I104d6af48ddd916460ee454e17a50a2475de6bff
Story: 2004805
Task: 28960
The IPA ramdisk fails to boot on UEFI compute nodes with iPXE. We see
the following error on the console, followed by a kernel panic:
Fix kernel panic-not syncing: VFS: unable to mount root fs on unknown
block(0,0)
The cause is the lack of an initrd=ironic-agent.initramfs kernel
argument in inspector.ipxe.
The initrd argument is present in the kolla-ansible version of
inspector.ipxe, and now contains all parameters that we need (since
Rocky), so this change simply removes our custom template, and passes
through the extra kernel argument option configuration value.
Story: 2006214
Task: 35804
Story: 2006213
Task: 35803
Depends-On: https://review.opendev.org/670566
Change-Id: I8a103b7c6d3dd1f0433f922ae90deae9b92c0c78
Fixes an issue where multiple NTP daemons could be running on the
overcloud hosts, due to Kolla Ansible deploying a chrony container by
default starting with the Rocky release.
Kayobe now overrides this default, to ensure that chrony does not conflict
with the NTP daemon deployed on the host. To use the containerised chrony
daemon instead, set ``kolla_enable_chrony`` to ``true`` in
``${KAYOBE_CONFIG_PATH}/kolla.yml``. This will also disable the host NTP
daemon.
To ensure that chrony is not running, Kayobe removes the chrony container
if ``kolla_enable_chrony`` is ``false`` in the following commands:
* ``kayobe overcloud service deploy``
* ``kayobe overcloud service reconfigure``
* ``kayobe overcloud service upgrade``
The play in Kayobe is tagged with ``stop-chrony``.
Change-Id: I89a973c0b600abece79bddcba5a46cc28a4f1df9
Story: 2005272
Task: 30122
