yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #94487
[Bug 2078382] [NEW] [OVN] User defined router flavor with no LSP associated to router interfaces
Public bug reported:
There is at least one OpenStack operator that requires the ability to
create a ML2/OVN user defined router flavor that doesn't have Logical
Switch Ports associated to their router interfaces. This allows a user
defined flavor driver to process traffic bypassing the OVN pipeline. In
this use case, Neutron acts only as an IP address manager for the router
interfaces.
The associated functionality shouldn't conflict with the ML2/OVN
mechanism manager when deleting the associated Neutron ports, which
would happen if the LSP is just removed without making provisions for
the eventual removal of the router interface.
** Affects: neutron
Importance: High
Assignee: Miguel Lavalle (minsel)
Status: New
** Changed in: neutron
Importance: Undecided => High
** Changed in: neutron
Assignee: (unassigned) => Miguel Lavalle (minsel)
** Description changed:
- There is at least one OpenStack operator that requires the ability to create a ML2/OVN user defined router flavor that doesn't have Logical Switch Ports associated to their router interfaces. This allows a user defined flavor driver to process traffic bypassing the OVN pipeline. In this use case,
- Neutron acts only as an IP address manager for the router interfaces.
+ There is at least one OpenStack operator that requires the ability to
+ create a ML2/OVN user defined router flavor that doesn't have Logical
+ Switch Ports associated to their router interfaces. This allows a user
+ defined flavor driver to process traffic bypassing the OVN pipeline. In
+ this use case, Neutron acts only as an IP address manager for the router
+ interfaces.
** Description changed:
There is at least one OpenStack operator that requires the ability to
create a ML2/OVN user defined router flavor that doesn't have Logical
Switch Ports associated to their router interfaces. This allows a user
defined flavor driver to process traffic bypassing the OVN pipeline. In
this use case, Neutron acts only as an IP address manager for the router
interfaces.
+
+ The associated functionality shouldn't conflict with the ML2/OVN
+ mechanism manager when deleting the associated Neutron ports.
** Description changed:
There is at least one OpenStack operator that requires the ability to
create a ML2/OVN user defined router flavor that doesn't have Logical
Switch Ports associated to their router interfaces. This allows a user
defined flavor driver to process traffic bypassing the OVN pipeline. In
this use case, Neutron acts only as an IP address manager for the router
interfaces.
The associated functionality shouldn't conflict with the ML2/OVN
- mechanism manager when deleting the associated Neutron ports.
+ mechanism manager when deleting the associated Neutron ports, which
+ would happen if the LSP is just removed without making provisions for
+ the eventual removal of the router interface.
** Summary changed:
- OVN User defined router flavor with no LSP associated to router interfaces
+ [OVN] User defined router flavor with no LSP associated to router interfaces
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2078382
Title:
[OVN] User defined router flavor with no LSP associated to router
interfaces
Status in neutron:
New
Bug description:
There is at least one OpenStack operator that requires the ability to
create a ML2/OVN user defined router flavor that doesn't have Logical
Switch Ports associated to their router interfaces. This allows a user
defined flavor driver to process traffic bypassing the OVN pipeline.
In this use case, Neutron acts only as an IP address manager for the
router interfaces.
The associated functionality shouldn't conflict with the ML2/OVN
mechanism manager when deleting the associated Neutron ports, which
would happen if the LSP is just removed without making provisions for
the eventual removal of the router interface.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2078382/+subscriptions
Follow ups