neutron/releasenotes/notes/change-the-way-how-api-extensions-are-filtered-out-b4449e690cb64480.yaml
Slawek Kaplonski db2207f32d [ML2] Change way how list of supported API extensions is made
Previously if extension was not supported by one of the mech drivers,
but it wasn't filtered out by next mech driver, it was available finally
in the list.
Now, this patch changes that so if extension is disabled by one of the
drivers it isn't available on the list at all.
This will work better e.g. with discoverability of what is available
e.g. when OVN backend is used by Neutron.

Closes-Bug: #1929676
Change-Id: I6a4ff42f47f7ee90365516d37472c09ac87773e5
2021-06-25 07:41:11 +00:00

14 lines
699 B
YAML

---
upgrade:
- |
The way the ML2 plugin filters out API extensions which are not supported
by loaded mechanism drivers has changed.
Before, the API extension was on the list if at least one of the mechanism drivers
supported it, but now the extension needs to be supported by all the mechanism
drivers. If at least one of them filters it out, it will be removed from
the final list of enabled API extensions.
Currently, only the OVN mechanism driver is filtering out some of the ML2
API extensions, thus if that mechanism driver is loaded in Neutron with any other
mechanism driver, the list of the enabled API extensions may be smaller than it
was before.