Current Series Release Notes¶
32.0.0.0rc1-52¶
Prelude¶
Group definitions for OpenStack-Ansible were changed by replacing dashes with underscores. Please check the Upgrade section for more detatails on how this affects you.
New Features¶
Ansible Core version was switched to 2.19 series.
Upgrade Notes¶
In order to configure SPICE frontend/backend on the loadbalancer use
nova_console_type_mappinginstead ofnova_console_type.For example:
nova_console_type_mapping: x86_64: spice ppc64le: novnc aarch64: serialconsole
Variable
nova_console_typeis compute-specific and is not used to calculate configuration for the Load Balancer.
Group
metering-group_containerhas been renamed toceilometer_compute_containerfor general consistency across group naming logic
All OpenStack-Ansible groups, conf.d and openstack_user_config.yml definitions were renamed by replacing all existing dashes with underscores. This change was made in order to comply with Ansible groups naming convention, which has been introduced back in Ansible 2.8. While old definitions should work after the upgrade, it is still recommended to replace group names with underscores inside of the
openstack_user_config.ymland conf.d files, as well as theopenstack_inventory.json, as the dynamic_inventory will not perform the conversion. Please note, that old group names can be also referenced inopenstack_user_config.ymlinside of the``provider_networks`` ->group_binds. So please ensure, that network bindings are also updated and contain group names only with underscores in their names. Ansible will issue a warning in case invalid group names are present in theopenstack_inventory.json, but will proceed with the replacement of dashes with underscores. You can ignore these warning messages and return the previous behavior by addingANSIBLE_TRANSFORM_INVALID_GROUP_CHARS=ignoreto/etc/openstack_deploy/user.rcor silence warnings and accept conversion to the new group names by addingANSIBLE_TRANSFORM_INVALID_GROUP_CHARS=silentlyto the/etc/openstack_deploy/user.rc. Change of the value for ANSIBLE_TRANSFORM_INVALID_GROUP_CHARS may affect environments, where deploy hosts are also used actively to run 3rd party Ansible roles and playbooks. You can read more about the variable and it’s effect on Ansible Community Documentation
Bug Fixes¶
OpenStack-Ansible and venv version detection is fixed for environments which were upgraded from pre-Flamingo releases.
32.0.0.0rc1¶
New Features¶
Added support for
conditionkey forceph_extra_componentsmapping, which could be used to define a more narrow conditions when component should be having ceph mappings.
Introduced variable
ceph_cinder_backup_enabledwhich can be manually overriden to enable provisionment of Ceph client tocinder-backupservice. Previously logic for this has been hardcoded and not easily overridable.
Added coordination support to the Aodh service. In case zookeeper is present in deployment, service will be configured to use it for coordination. Operators are able to supply arbitrary coordination url via
aodh_coordination_urlvariable.
Erlang version was updated to 27.3.x series.
RabbitMQ version was upgraded to version 4.1.4
Added variable
venv_install_toolwhich has default value ofpip. You can define it touvto leverage package installation inside of the venv usinguvtool instead ofpip. Wheels build and venv creation is still managed viapipandvenvrespectively.
Upgrade Notes¶
Variable
networking_ovn_bgp_install_branchhas been renamed tonetworking_ovn_bgp_git_install_branchin order to match existing naming convention.
With removal of eventlet mode for
neutron-serverin Neutron, the only supported mode for the service is uWSGI. All deployments using eventlet will be migrated to uWSGI mode forneutron-server. With that multiple extra mandatory services will be started together withneutron-server, likeneutron-rpc-server,neutron-periodic-workersandneutron-ovn-maintenance-workerfor OVN-based deployments.
Deprecation Notes¶
Variable
neutron_use_uwsgihas been removed and has no effect, since eventlet mode forneutron-serverhas been dropped in 2025.2 (Flamingo). uWSGI is the only supported mode at the moment.
Variable
octavia_legacy_policywas removed and has no effect anymore. In case you was using the variable and it was set toTrue, you can incorporate policy changes this variable was implementing to youroctavia_policy_overrides. You may find rules controlled by this variable via the link
Remove
SHOW_KEYSTONE_V2_RCconfig option, which was deprecated since the Stein release. It is now safe to remove this option.
Bug Fixes¶
Fixes SHA pinning and installation of
ovn-bgp-agent, as SHA pinning and role were using different variable names.
URI to Shibboleth mirror has been fixed for EL-based distributions.
Other Notes¶
Debian/Ubuntu Repository for RabbitMQ has changed from ppa1.rabbitmq.com to deb1.rabbitmq.com and deb2.rabbitmq.com.