2025.1 Series Release Notes

3.18.2

Bug Fixes

  • Fixed the validation of routerexternal_gateway_info field. Eachextension adding a new validator amends the previous definition, butdoesn’t overwrite it.

3.17.0

New Features

  • Theqinq extension adds aqinq attribute to the networkresource. This new attribute can be used in a similar way tovlan_transparent but networks created withqinq set will use0x8a88 ethertype for the double vlan tagged traffic.Attributesqinq andvlan_transparent can’t be used togetherfor the same network.

3.16.0

New Features

  • Add the API extensionuplink-status-propagation-updatable to make theport fieldpropagate_uplink_status updatable. Now it is possible to senda port PUT request to update the value defined during the creation. Thischange will have an effect in the ML2/SR-IOV agent that will need to updatethe VF status accordingly.

  • Add API extensionquota-check-limit-default. This is a shim extensionthat indicates if Neutron quota engine checks the resource usage beforeupdating any quota limit. That makes the extensionquota-check-limitto be the default Neutron quota engine behaviour and aligns it with otherprojects. To enforce a quota limit without checking the resource usage,now it is needed to pass the CLI parameter “–force”.

  • Theport-trusted-vif extension addstrusted attribute to the portresource. This new attribute allows to set through the APISR-IOV portto betrusted. This was previosly only possible through thebinding:profile attribute of the port resource but that was invalid andnow is not possible.Value of that new field will be populated in the port’sbinding:profile.

Deprecation Notes

  • Theneutron_lib.rpc:get_notifier default value forservice argument(None) is deprecated. The argument will be required in a futurerelease.