Current Series Release Notes¶

27.0.0-54¶

Add the extension extraroute-atomic to the ML2/OVN router plugin. This extension does not require any specific implementation.

Removed support for OVN versions under v20.03.0. The “ha_chassis_group” field is expected in the “Logical_Router_Port” Northbound table. For more information, see commit ovn: Support a new Logical_Switch_Port.type - ‘external’.

The new router-enable-snat extension API definition has been added. This extension makes public the router “enable_snat” boolean field. This field can be set during the router creation or updated when adding/updating the router gateways. Although the API allows to define a different value per gateway port (a router can have multiple gateways), only the first one will apply (this is a router level configuration flag).

An new option name trunk_enabled has been added to neutron-openvswitch-agent under OVS group. This new option can be set to False in order to disable loading the trunk extension on agent side. The default value for this option is True to keep backward compatibility with previous deployments. The recommendation is to set this option to False if you do not use the trunk extension, so that the number of queues created by the RPCServer will reduce. This can have a very good impact on large-scale scenario using RabbitMQ message broker.

The WSGI script neutron-api has been removed. Deployment tooling should instead reference the Python module path for this service, neutron.wsgi.api, if their chosen WSGI server supports this (gunicorn, uWSGI) or implement a .wsgi script themselves if not (mod_wsgi).

Usage of tenant_id in the API policy rules is deprecated and will be removed in the 2027.1 release. Please use project_id instead.

The configuration parameters ovn_dhcp4_global_options and ovn_dhcp6_global_options allow multiple values per key, separated by a semi-colon character. E.g.: ntp_server:1.2.3.4,wpad:1.2.3.5;1.2.3.6

Use of DHCPv6 option 59 (bootfile-name) is now supported with OVN. See bug: 2125715.

When OVS agent is restarting, it is now correctly restoring the tunnel outputs openflow rules so tunnels are still working correctly between computes. See bug 1978088 for details.

It is assumed now that OVN supports external ports. This functionality was added in OVN v20.03.0.