Hi,

We have config option to enable vlan_transparent api extension currently. We will also have similar config option for vlan_qinq (it is now proposed in [1]).

In both cases we have validation by mechanism drivers if option is or is not supported while networks are created.
We can also filter out enabled API extensions by mechanism drivers, see [2] for example.

So I proposed [3] to remove that config option and keep API extension to be loaded always if enabled ML2 drivers supports it. But before I will propose patch for that I would like to ask if there is maybe some use case for this config option really and maybe some of you somehow depends on it. In such case maybe we should keep it like it is now and don't remove it. Please let me know if you are using somehow this option.

[1] https://review.opendev.org/c/openstack/neutron/+/937372
[2] https://github.com/openstack/neutron/blob/559672f777312d00c4358626650cc577e49ec0b6/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py#L237

[3] https://bugs.launchpad.net/neutron/+bug/2092174

--

Slawek Kaplonski

Principal Software Engineer

Red Hat