yahoo-eng-team team mailing list archive

[Slawek Kaplonski <2092174@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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 think we should deprecate those config options in the E or F cycle
and then remove them completely.

[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

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: api

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2092174

Title:
  Deprecate and remove vlan_transparent config option

Status in neutron:
  New

Bug description:
  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 think we should deprecate those config options in the E or F
  cycle and then remove them completely.

  [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

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2092174/+subscriptions