2025.1 Series Release Notes

3.18.2

Bug Fixes

• Fixed the validation of router external_gateway_info field. Each extension adding a new validator amends the previous definition, but doesn’t overwrite it.

3.17.0

New Features

• The qinq extension adds a qinq attribute to the network resource. This new attribute can be used in a similar way to vlan_transparent but networks created with qinq set will use 0x8a88 ethertype for the double vlan tagged traffic. Attributes qinq and vlan_transparent can’t be used together for the same network.

3.16.0

New Features

• Add the API extension uplink-status-propagation-updatable to make the port field propagate_uplink_status updatable. Now it is possible to send a port PUT request to update the value defined during the creation. This change will have an effect in the ML2/SR-IOV agent that will need to update the VF status accordingly.

• Add API extension quota-check-limit-default. This is a shim extension that indicates if Neutron quota engine checks the resource usage before updating any quota limit. That makes the extension quota-check-limit to be the default Neutron quota engine behaviour and aligns it with other projects. To enforce a quota limit without checking the resource usage, now it is needed to pass the CLI parameter « –force ».

• The port-trusted-vif extension adds trusted attribute to the port resource. This new attribute allows to set through the API SR-IOV port to be trusted. This was previosly only possible through the binding:profile attribute of the port resource but that was invalid and now is not possible. Value of that new field will be populated in the port’s binding:profile.

Deprecation Notes

• The neutron_lib.rpc:get_notifier default value for service argument (None) is deprecated. The argument will be required in a future release.