Public bug reported:
The aim of this RFE is to refactor the OVS Trunk plugin, in order to
have one single port between the trunk bridge and the integration
bridge. The VLAN filtering will be done by configuring the port with
"vlan_mode=trunk" and defining the corresponding VLAN IDs in the "trunk"
parameter, including VLAN 0 for the untagged traffic that is handled by
the parent port.
This is just an initial idea that should be refined, tested and
presented first as a POC in order to check its validity.
** Affects: neutron
Importance: Wishlist
Status: New
** Changed in: neutron
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2049623
Title:
[RFE] Refactor OVS Trunk plugin to have one single port
Status in neutron:
New
Bug description:
The aim of this RFE is to refactor the OVS Trunk plugin, in order to
have one single port between the trunk bridge and the integration
bridge. The VLAN filtering will be done by configuring the port with
"vlan_mode=trunk" and defining the corresponding VLAN IDs in the
"trunk" parameter, including VLAN 0 for the untagged traffic that is
handled by the parent port.
This is just an initial idea that should be refined, tested and
presented first as a POC in order to check its validity.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2049623/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
