Current Series Release Notes

21.0.0-19

New Features

  • Adds a new kayobe overcloud firmware update command to update firmware on the overcloud hosts. The firmware update is performed out of band via the hosts’ BMCs using the dellemc.openmanage.idrac_firmware Ansible module, and currently supports Dell servers with iDRACs. The firmware update repository is configured via the dell_firmware_update_* variables in bmc.yml. Use Ansible check mode (--check) to show the available firmware updates without applying them.

  • Improves network role to host mapping, avoiding networks being mapped to hosts unnecessarily.

  • Custom playbook hooks are no longer considered experimental. Future changes to their design will follow the standard deprecation process.

  • Support for infrastructure VMs is no longer considered experimental. Future changes to its design will follow the standard deprecation process.

  • Support for multiple Kayobe environments, including environment dependencies declared in .kayobe-environment files, is no longer considered experimental. Future changes to their design will follow the standard deprecation process.

Upgrade Notes

  • Modifies the default mapping of networks to hosts.

    Operators upgrading an existing deployment should check whether this change affects their topology before running kayobe overcloud host configure. Deployments using the default inventory, where the network, monitoring and Ironic conductor and inspector groups all resolve to controllers, are unaffected. Deployments that separate those groups may find that some networks are no longer mapped to some hosts.

    On Ubuntu and Debian, kayobe removes systemd-networkd configuration for networks that are no longer mapped to a host, so the corresponding interface is torn down the next time kayobe overcloud host configure runs. On Rocky Linux the existing interface configuration is left in place, but is no longer managed by kayobe.

    To review the effect before applying it, compare network_interfaces for each host before and after the upgrade:

    kayobe configuration dump --hosts overcloud \
      --var-name network_interfaces
    

    To keep a network mapped to a host, either override the relevant <role>_net_required flag in networks.yml, or add the network to that group’s <group>_extra_network_interfaces.

    • overcloud admin network (admin_oc_net_name): unchanged

    • overcloud out-of-band network (oob_oc_net_name): unchanged

    • overcloud provisioning network (provision_oc_net_name): unchanged

    • workload (compute) out-of-band network (oob_wl_net_name): previously mapped to all controllers. Now mapped to controller_ironic_conductor_group (default controllers), when Ironic is enabled.

    • workload (compute) provisioning network (provision_wl_net_name): previously mapped to all controllers. Now mapped to controller_ironic_conductor_group (default controllers), when Ironic is enabled.

    • internal network (internal_net_name): previously mapped to compute, controllers, monitoring, network, storage groups. Now mapped to overcloud group.

    • external networks (external_net_names): previously mapped to compute group when kolla_enable_neutron_provider_networks is true, and network group unconditionally. Now mapped to compute group when kolla_enable_neutron is true and kolla_enable_neutron_provider_networks is true, and controller_network_group group when kolla_enable_neutron is true.

    • public network (public_net_name): previously mapped to the network and monitoring groups. Now mapped to controller_loadbalancer_group (default network) only. Hosts in the monitoring group that are not also in controller_loadbalancer_group are no longer attached to the public network, since the services running on them are reached via the load balancer. Set public_net_required or monitoring_extra_network_interfaces to restore the previous behaviour.

    • tunnel network (tunnel_net_name): previously mapped to compute and network groups. Now mapped to compute and controller_network_group (default network) groups.

    • storage network (storage_net_name): previously mapped to compute, controllers, network and storage groups. Now mapped to compute, controllers, storage networks unconditionally, and controller_network_group (default network) group when kolla_enable_manila is true.

    • storage management network (storage_mgmt_net_name): unchanged.

    • overcloud inspection network (inspection_net_name): previously mapped to controllers group. Now mapped to controller_ironic_inspector_group (default controllers) when kolla_enable_ironic is true.

    • overcloud cleaning network (cleaning_net_name): previously mapped to controllers group. Now mapped to controller_ironic_conductor_group (default controllers) when kolla_enable_ironic is true.

  • Use the public-openrc.sh generated by Kolla Ansible instead of generating our own. This may result in minor changes to this file.

Bug Fixes

  • Fixed Dell SONiC switch config indentation. Also made sure that VLAN interfaces are defined first as others might depend on them. Related bug: LP#2168529

  • Fixed a vault password validation bug that caused errors when using ANSIBLE_VAULT_PASSWORD_FILE. Users would encounter an error: The vault-ids default,default are available to encrypt. Specify the vault-id to encrypt with --encrypt-vault-id. The issue occurred because the vault password helper was being invoked unnecessarily when only ANSIBLE_VAULT_PASSWORD_FILE was set. LP#2160369

  • Fixes wrong values of OS_AUTH_URL in public-openrc.sh when using a single external frontend in HAProxy. LP#2168467