Current Series Release Notes¶
19.0.0.0rc1-66¶
New Features¶
Add support for easily viewing the content of
kolla/passwords.ymlwith the new commandkayobe overcloud service passwords view.
Allows configuring
inspector_keep_portsfor Bifrost viakolla_bifrost_inspector_keep_ports(defaults topresentto match Bifrost).
Adds support for bootstrapping Python on Ubuntu through a proxy.
Bumps
stackhpc.linuxAnsible collection to v1.5.1. This adds support for configuring MIG devices without creating vGPUs.
Adds support for managing the Ansible control host configuration. This is provided by the new
kayobe control host configurecommand, and uses the existing host configuration features in Kayobe.Also provided is a
kayobe control host command runcommand for running commands on the Ansible control host, and akayobe control host package updatecommand for updating its OS packages.
Configure inspection network DNS servers to enable Ironic inspection when
kolla_internal_fqdnis set.
Added the tag
bifrosttokolla-bifrost.ymlso that we can easily limit to Bifrost inkayobe seed service deploy.
Removed the options
--kolla-tagsandkolla-limitfrom all commands. Regular--tagsand--limitwill now be passed directly to the Kolla-Ansible invocations. Added the tagkayobe-generate-configtokolla-ansible.ymlandkolla-openstack.yml. This tag is now always called, to allow for limiting to OpenStack services with just one tag, e.g.kayobe overcloud service deploy -t nova`. You can still skip this with ``--skip-tags kayobe-generate-config.
Skip external connectivity check behind a proxy.
Adds an opt-in
nmstatenetwork engine (network_engine: nmstate) for host network configuration via NetworkManager/libnmstate.
Supports Ethernet, VLAN, bond, bridge, routes, and routing rules, and adds OVS patch-link veth generation for overcloud bridge-to-OVS connectivity.
Adds structured ethtool configuration via
<network>_ethtool_configfor ring parameters and selected offload features.
The nmstate network engine is only supported on Rocky Linux. Ubuntu Noble is not supported because the required system packages (nmstate, python3-libnmstate) are not available in Ubuntu repositories. Attempting to use nmstate on Ubuntu will fail with a clear error message directing users to use the
legacynetwork engine.
Adds support for installing and configuring fail2ban. See the docs http://docs.openstack.org/kayobe/latest/configuration/reference/hosts.html#fail2ban for more information.
Known Issues¶
NTP configuration was missing from infrastructure VMs because
infra-vmswas not present under the[ntp]group. Operators should ensure the most recent upstreamkayobe-configis merged into their local configuration to resolve this issue.
Upgrade Notes¶
Rocky Linux based Ironic Python Agent images are now built in Rocky Linux based deployments rather than CentOS Stream:
ipa_build_dib_elements_defaultusesrocky-containerelement;ipa_build_dib_packagesincludes thepython3-yamlpackage;ipa_build_dib_env_defaultuses specifiedos_release; and container runtime is set tocontainer_engine.
baremetalelement now included inipa_build_dib_elements_default
Updates the maximum supported version of Ansible from 12 (ansible-core 2.19) to 13 (ansible-core 2.20). The minimum supported version is updated from 11.x to 12.x. This is true for both Kayobe and Kolla Ansible.
Removed the options
--kolla-tagsandkolla-limitfrom all commands. Regular--tagsand--limitwill now be passed directly to the Kolla-Ansible invocations. Added the tagkayobe-generate-configtokolla-ansible.ymlandkolla-openstack.yml. This tag is now always called, to allow for limiting to OpenStack services with just one tag, e.g.kayobe overcloud service deploy -t nova`. You can still skip this with ``--skip-tags kayobe-generate-config.
Python 3.10 and 3.11 are no longer supported on the control host. Use Python 3.12 as a minimum version for the Kayobe virtualenv.
Introduces
network_engineinglobals.yml:legacy(default) andnmstate.
With
nmstate, ethtool settings use structured YAML in<network>_ethtool_config.legacyengine behavior is unchanged.
With
network_engine: nmstate,<network>_rulesentries must use dict format (keys such asfrom,to,priority,table). String-format rules are rejected on thenmstatepath.legacyengine behavior is unchanged.
Switching to
nmstatemay reconfigure host networking and cause temporary connectivity disruption.
Bug Fixes¶
Fixes generation of Bifrost host variable files when
ipv4_gatewayis undefined. LP#2133489
Bumps
stackhpc.linuxAnsible collection to v1.5.1. This fixes race conditions in setup of vGPU SR-IOV devices.
Fixes swap configuration for the seed hypervisor, seed and infra VM hosts. LP#2138800
Bumps version of
nvidia.nvueAnsible collection from1.2.6to1.2.9. This fixes an issue where switch configuration could not be applied to switches running Cumulus Linux 5.13. See LP#2131677 for more details.
Fixes an issue building diskimage-builder images when EPEL is disabled. See LP#2141684 for more details.
Fixes an issue building diskimage-builder images when using the podman container engine, See LP#2142501 for more details.
Fixes host configure regressions when using
network_engine: nmstateon Rocky Linux. Kayobe now ensures named route tables fromnetwork_route_tablesare defined in/etc/iproute2/rt_tablesfor nmstate-managed hosts. These fixes apply only to thenmstateengine path;legacyengine behavior is unchanged.
When using
network_engine: nmstatewith firewalld enabled, Kayobe now reconciles interface-to-zone mappings in both permanent and runtime firewalld configuration for interfaces that define<network>_zone.