Current Series Release Notes

26.0.0.0rc1-83

New Features

• Updated RBAC rules so that they allow the service role to pass the following policies by default:

  • get_subnet

  • get_network_ip_availability

  • create_port:allowed_address_pairs

  • create_port:allowed_address_pairs:mac_address

  • create_port:allowed_address_pairs:ip_address

  • update_port:allowed_address_pairs

  • update_port:allowed_address_pairs:mac_address

  • update_port:allowed_address_pairs:ip_address

  This allows for integration with the Octavia project using the service role instead of the admin role for integration with Neutron.

• Added service role to the create_port:device_id and update_port:device_id policies to allow service users for other OpenStack projects to complete Secure RBAC.

Known Issues

• The ML2/OVN Placement initial configuration is executed now in the Neutron API process and removed from the maintenance worker; since the migration to WSGI, now the API and the maintenance worker are different processes. When an OVN Chassis creation event is received, the configuration is read, a PlacementState object created and sent to the Placement API.

Upgrade Notes

• Default RBAC policies for get_subnet, get_network_ip_availability, create_port:allowed_address_pairs, create_port:allowed_address_pairs:mac_address, create_port:allowed_address_pairs:ip_address, update_port:allowed_address_pairs, update_port:allowed_address_pairs:mac_address and update_port:allowed_address_pairs:ip_address have been updated to allow the service role.

Bug Fixes

• The OVN QoS floating IP rule has precedence over the OVN QoS router rule. If both are present in the same router and port (the one assigned to the floating IP), the floating IP rule will now apply. For more information, see bug 2110018.

Other Notes

• The ML2/OVN Placement extension now removes any existing resource provider deleted from the updated local node configuration. If the resource provider has allocations, Placement will return an exception and it will not be deleted.