Refactored the code to switch the distribution source of the roles
to new collections for the roles that have already been migrated into
collections.
Updated:
- requirements
- role invocations
- documentation
- release notes
- minor whitespace fixes
Change-Id: I8dbb88aa2061b3afcab07caeb30f45b3a5c939af
This has now been removed from upstream docker-ce packages.
```
the devicemapper storage-driver has been deprecated and removed
```
and has shown deprecation warnings for some time.
This change also includes some fixes necessary for CI to pass:
* update the Zuul previous_release variable to 2023.2
Closes-Bug: #2051233
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/906858
Change-Id: I263f59ea77e39accffe4febe0d47e56b35d9800e
Switch all dependencies to use the OpenStack 2023.2 release.
This commit should be reverted on the master branch once the
Kayobe stable/2023.2 branch has been cut and RC1 released.
Change-Id: I749a1ac30fa15cf7faa456fcb90c4ddbbef77cc9
Kayobe has fairly coarse-grained default groups - controller, compute,
etc, which work well in the majority of cases. Kolla Ansible allows much
more fine-grained placement on a per-service basis, e.g.
ironic-conductor. If the operator has taken advantage of this
fine-grained placement, then it is possible that some of the assumptions
in Kayobe may be incorrect. This is one downside of the split between
Kayobe and Kolla Ansible.
For example, Ironic conductor services may have been moved to a subset
of the top level 'controllers' group. In this case, we would not want
the Ironic networks to be mapped to all hosts in the controllers group -
only those running Ironic conductor services. The same argument can be
made if the loadbalancer services (HAProxy & keepalived) or Neutron
dataplane services (e.g. L3 & DHCP agents) have been separated from the
top level 'network' group.
This change abstracts the placement of Ironic conductor Ironic
inspector, loadbalancer and network services into separate variables,
rather than referencing the top level 'controllers' and 'network' groups
directly. These variables may be updated by the operator to match the
service placement.
Change-Id: Idbf181c795ee98ad653f11ae483f9dab4ef1b599
Fixes an issue when user forgot to combine
'kolla_ansible_custom_passwords',
'kolla_ansible_default_custom_passwords' and own dictionary with
custom passwords in configuration files. Now
'kolla_ansible_extra_custom_passwords' should provide only user
custom passwords to add or override in the passwords.yml.
Change-Id: I4813a1f6ab9cb566596e806bd0ada6dff342d119
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
Kolla Ansible renamed kolla_internal_fqdn_cacert to
kolla_admin_openrc_cacert in Victoria, after which we no longer set the
variable correctly in globals.yml. This would lead to a missing
OS_CACERT in admin-openrc.sh and public-openrc.sh.
This change fixes the issue by renaming the relevant Kayobe variables to
match and passing through the correct variable. Backwards compatibility
is provided until the end of the deprecation period.
kolla_public_openrc_cacert -> kolla_external_fqdn_cacert
kolla_admin_openrc_cacert -> kolla_internal_fqdn_cacert
Story: 2010486
Task: 47054
Change-Id: I9e1cc20579cf80525d6ef732a1aac99a65bc171b
Co-Authored-By: Maksim Malchuk <maksim.malchuk@gmail.com>
This variable is not supported since
I61a61ca59652b13687c2247d5881012b51f666a7, but was not removed from
etc/kayobe/kolla.yml in that change.
This change also adds the replacement variable docker_registry_insecure
to etc/kayobe/docker.yml.
TrivialFix
Change-Id: I3fa96f0276e08a6678e5d743399d01bc19a8dd1b
Follow on to Ie17ef9ce1147cbaec2e42db932c7d59293b49b1b
Adds seed_deploy_containers_registry_attempt_login variable to seed.yml,
which acts as a redirection of deploy_containers_registry_attempt_login
so that the variable is more descriptive, declared in a better location,
and extensible to other groups
Change-Id: I86d8f13062ff8e664919cd5d63bc17bdafb32e0c
Back in the Ussuri release, we changed the Bifrost kernel location to
use ipa.kernel instead of ipa.vmlinuz. While this works fine for newly
discovered nodes, any node added to Bifrost in Train or earlier will
have kept ipa.vmlinuz as its deploy kernel.
This can cause issues since upgrading Bifrost or building new deployment
images will update ipa.kernel, but not ipa.vmlinuz, resulting in nodes
booting with an old kernel and a new ramdisk.
Fix by adding a new rule updating the legacy kernel location and
documenting how to update node information.
Change-Id: I6ae44dcae78424b4638762d015cf24336444707f
The default value for ipa_build_dib_elements_default was previously
changed in Iefd2d0b7a3a3e07f5c112d58e2ec0b3da0a747d3. This change
updates the comments to match.
Change-Id: I47e5acb19c806a1067879c9cf5fa5ccb7f07ccd4
Since I2831e58d84f1da03485f8315eccdd2e79231e584 is used by Bifrost
we add custom user_data content configuration for Bifrost.
Story: 2010580
Task: 47336
Change-Id: I989069f3b3b43bc7a7a2e46ef5f046b8ed7cf8d1
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
The name of ``mrlesmithjr.manage_lvm`` was changed yesterday in release
v0.2.10 to use an underscore, instead of a hyphen. As this changes the
name of the role on Ansible Galaxy, it needs to be updated in
``requirements.yml``.
Closes-Bug: #2024163
Change-Id: I4ea8d8c3a822a7c217bcfcfd5027eecfd21beaed
This patch adds new functionality - merging base & environment specific
kolla config. This allows you to place common settings in the base
configuration and only keep environment specific settings in the
environment directories.
Change-Id: Id4588f4529a4522e68e22ce58711cb927fa68a9d
Story: 2002009
Task: 42903
Switch all dependencies to use the OpenStack 2023.1 release.
This commit should be reverted on the master branch once the
Kayobe stable/2023.1 branch has been cut and RC1 released.
Change-Id: Id5e946fd7b0526faea99536f4a055f0f5c2b8176
Preparations for Antelope RC1.
Synchronises Kayobe with the Kolla-Ansible feature flags and inventory.
Change-Id: I89a3fd800fafb29be27846806de4e6465209134c
This change fixes the description accidently copied from the
'kayobe_env_config_path' description.
TrivialFix
Change-Id: I7b9ced54ad886b3f92f7c757adc2efafa4cbfa4e
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
Without this change, Kayobe was tagging container images with `zed` when
kolla-ansible was expecting something like `zed-ubuntu-jammy`.
Change-Id: I23c409900db2c37105e7b218bbaedcfacb235787
This commit adds the necessary changes needed to support
reading and writing Kolla passwords to a Hashicorp Vault server
using Kolla-Ansible commands `kolla-readpwd` and `kolla-writepwd`.
This follows the support that was added into Kolla-Ansible in
the Change-Id Icf0eaf7544fcbdf7b83f697cc711446f47118a4d.
Change-Id: I732988e6160cc64d663d6ef8179f04d3e1226537
Switch all dependencies to use the OpenStack Zed release.
This commit should be reverted on the master branch once the
Kayobe stable/zed branch has been cut and RC1 released.
Change-Id: I1ea18a68bb2c1ea6a2a45f6cbd3c48fd30bb1c8a
This follows removal of support from Kolla Ansible. This also removes
support for configuring Grafana with overcloud post configure.
Change-Id: I8102fafb00db178f1ae6801d37c43a39033cbfe6
CentOS Stream 8 support has been dropped. Migration path will be present
in Yoga release - as a followup change.
MichaelRigart.interfaces does not support custom routes for
NetworkManager yet. It has been disabled in CI for Rocky Linux 9
temporarily.
Non-voting CentOS Stream 9 CI overcloud job is using RL9 container
images (as kolla CI is not building CS9 images anymore).
Change-Id: Idf5ee822b03ba40179803c981500a6bad37594bf
Zuul