We are jazzed to announce the release of: kayobe 13.3.0: Deployment of OpenStack to bare metal using OpenStack kolla and bifrost This release is part of the zed stable release series. The source is available from: https://opendev.org/openstack/kayobe Download the package from: https://tarballs.openstack.org/kayobe/ Please report issues through: https://storyboard.openstack.org/#!/project/openstack/kayobe For more details, please see below. 13.3.0 ^^^^^^ New Features ************ * The Spanning Tree Protocol (STP) can now be configured on bridge interfaces. Enable or disable STP by setting the "bridge_stp" attribute for a network. Note that STP is not set by default on Ubuntu, but it is disabled on Rocky Linux 9 for compatibility with network scripts, as NetworkManager enables STP on all bridges by default. * Attempts to log in to the kolla docker registry can be skipped by setting "deploy_containers_registry_attempt_login" to false. This is required for deployments using a non-standard registry deployed on the seed during the deploy-container step, since it takes place after the registry login attempt. Upgrade Notes ************* * For Rocky Linux 9, Kayobe now disables STP on a bridge by default. This action will cause the bridge interface to restart during the host configuration process. * Adds an introspection rule to update the location of the deployment kernel registered in existing Ironic nodes. Nodes discovered on a deployment running the Train release or earlier may still be using the "ipa.vmlinuz" kernel, which stays unchanged when deployment images get updated. If only default introspection rules are in use, existing nodes may be updated from the Bifrost container with the following command: "OS_CLOUD=bifrost baremetal introspection reprocess $NODE_UUID_OR_NAME" If non-default rules are used, reprocessing may revert any customisation done by the operator. In this case, a more cautious approach is to update the deployment kernel location manually: "OS_CLOUD=bifrost baremetal node set --driver-info deploy_kernel=<http://url/to/ipa.kernel> $NODE_UUID_OR_NAME" If the "kolla_bifrost_inspector_rules" list is customised, the rule "inspector_rule_legacy_deploy_kernel" should be added to it. Bug Fixes ********* * Fixes failure to run "kayobe overcloud deprovision" after Bifrost is redeployed. LP#2038889 * Improves performance of Bifrost operations by preventing unnecessary requests to the Ironic API. * Fixes detection of data file path when using editable installations with a recent pip. * Fixes the regression in configuring additional route options on CentOS / Rocky. * Fixed issue of seed containers being unable to use password protected registry by adding docker login function to kayobe deploy- containers role. * Adds a workaround to avoid NetworkManager setting the MTU of bridge VLAN interfaces to an incorrect value. LP#2039947 * Fixes conflicts between NetworkManager nmconnection files generated by "cloud-init" and those generated by Kayobe by upgrading the "MichaelRigart.interfaces" role to version 1.14.4. LP#2039975 Changes in kayobe 13.2.0..13.3.0 -------------------------------- 790427f8 Fix MTU of NetworkManager bridge VLAN interfaces bacab88a Bump MichaelRigart.interfaces to v1.14.4 0638862a Add option to skip kolla docker registry login a1a1f8d3 bifrost: Populate bifrost host vars on deprovision cd0bdbdd Add introspection rule to update deploy kernel location 8b7b8e37 Revert "CI: Disable bare metal testing on RL9/c9s" a1fc1b43 CI: Enable Ubuntu jobs again d773ed56 Use importlib.metadata instead of importlib_metadata 77a0e36f Fix data file path detection with new pip 16c10d12 Fix firewalld configuration for monitoring hosts 0cb8a93e Speed up calls to Bifrost 3e3b41cc CI: fetch systemd configuration including kolla-generated unit files fbe1bd4f Fix for seed-containers being unable to use password protected registry 3abfeb27 Fix CentOS / Rocky route options b0f5e013 Add STP option for bridge interfaces e00f9cad docs: Add a warning on creating network loops abff761c Limit interface names to 15 characters Diffstat (except docs and test files) ------------------------------------- ansible/container-image-build.yml | 5 +- ansible/inventory/group_vars/all/bifrost | 5 +- ansible/inventory/group_vars/all/inspector | 12 +++++ ansible/inventory/group_vars/monitoring/firewall | 4 +- ansible/overcloud-bios-raid.yml | 2 + ansible/overcloud-deprovision.yml | 3 ++ ansible/overcloud-hardware-inspect.yml | 4 ++ ansible/overcloud-introspection-data-save.yml | 2 +- ansible/overcloud-provision.yml | 4 ++ ansible/roles/deploy-containers/defaults/main.yml | 2 + ansible/roles/deploy-containers/tasks/main.yml | 9 ++++ ansible/roles/network-redhat/tasks/main.yml | 2 +- ansible/seed-introspection-rules.yml | 1 + ...tenks-deploy-config-compute-libvirt-on-host.yml | 6 +++ dev/tenks-deploy-config-compute.yml | 6 +++ .../reference/seed-custom-containers.rst | 23 +++++++++ etc/kayobe/bifrost.yml | 3 ++ kayobe/cli/commands.py | 3 +- kayobe/plugins/action/kolla_ansible_host_vars.py | 5 +- kayobe/plugins/filter/networkd.py | 3 ++ kayobe/plugins/filter/networks.py | 60 ++++++++++++++++++++-- kayobe/utils.py | 22 ++++++++ playbooks/kayobe-overcloud-base/run.yml | 2 - .../overrides.yml.j2 | 2 + playbooks/kayobe-overcloud-upgrade-base/run.yml | 4 -- .../add-bridge-stp-option-9be6bf35f6425548.yaml | 12 +++++ ...ost-host-vars-deprovision-525c450cf20f7f71.yaml | 7 +++ .../notes/bifrost-speedup-9902552b86150ad4.yaml | 5 ++ ...le-install-data-file-path-743b7a85a5f5db6d.yaml | 5 ++ .../fix-rhel-route-options-94b7dd3712a0c6d3.yaml | 5 ++ .../kayobe_docker_login-495a424c2da479a7.yaml | 6 +++ ...ridge-vlan-mtu-workaround-71d48d582b5e23d6.yaml | 6 +++ ...manager-cloud-init-config-315c0eb846b72c93.yaml | 7 +++ ...lla-docker-registry-login-f5b0ba858a35ea39.yaml | 9 ++++ .../update-deploy-kernel-6943f3ad3cb82c51.yaml | 20 ++++++++ requirements.yml | 4 +- roles/kayobe-diagnostics/files/get_logs.sh | 4 ++ zuul.d/project.yaml | 16 ++---- 42 files changed, 296 insertions(+), 34 deletions(-)