yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #95462
[Bug 2101162] [NEW] [OVN] Use HA_Chassis_Group for tunnelled gateway network LRPs
Public bug reported:
Since [1][2][3] it is possible to set a tunnelled network as a gateway
network for a router. The router will be pinned to a chassis in order to
bind the gateway ``Logical_Router_Port`` (GW LRP) to this chassis. In
[3], a HA implementation was done using the list provided by a router
associated ``HA_Chassis_Group``.
However, this implementation requires Neutron to update the pinned
chassis manually when a change in the HA_Chassis_Group happens; for
example, when a ``Chassis`` is removed from the database. But if a node
fails and the ``Chassis`` is not removed from the database, this HA
implementation will fail.
This bug proposes a more robust method that is not to pin the
``Logical_Router`` but to assign the ``HA_Chassis_Group`` to the GW LRP.
That provides a more robust HA support as long as OVN checks the chassis
interfaces, if one fails, it changes the GW LRP binding.
[1]https://bugs.launchpad.net/neutron/+bug/2052821
[2]https://review.opendev.org/c/openstack/neutron/+/909194
[3]https://review.opendev.org/c/openstack/neutron/+/909437
Jira reference: https://issues.redhat.com/browse/OSPRH-12265
** Affects: neutron
Importance: Medium
Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez)
** Changed in: neutron
Importance: Undecided => Medium
** Description changed:
Since [1][2][3] it is possible to set a tunnelled network as a gateway
network for a router. The router will be pinned to a chassis in order to
bind the gateway ``Logical_Router_Port`` (GW LRP) to this chassis. In
[3], a HA implementation was done using the list provided by a router
associated ``HA_Chassis_Group``.
However, this implementation requires Neutron to update the pinned
chassis manually when a change in the HA_Chassis_Group happens; for
example, when a ``Chassis`` is removed from the database. But if a node
fails and the ``Chassis`` is not removed from the database, this HA
implementation will fail.
This bug proposes a more robust method that is not to pin the
``Logical_Router`` but to assign the ``HA_Chassis_Group`` to the GW LRP.
That provides a more robust HA support as long as OVN checks the chassis
interfaces, if one fails, it changes the GW LRP binding.
[1]https://bugs.launchpad.net/neutron/+bug/2052821
[2]https://review.opendev.org/c/openstack/neutron/+/909194
[3]https://review.opendev.org/c/openstack/neutron/+/909437
+
+ Jira reference: https://issues.redhat.com/browse/OSPRH-12265
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2101162
Title:
[OVN] Use HA_Chassis_Group for tunnelled gateway network LRPs
Status in neutron:
New
Bug description:
Since [1][2][3] it is possible to set a tunnelled network as a gateway
network for a router. The router will be pinned to a chassis in order
to bind the gateway ``Logical_Router_Port`` (GW LRP) to this chassis.
In [3], a HA implementation was done using the list provided by a
router associated ``HA_Chassis_Group``.
However, this implementation requires Neutron to update the pinned
chassis manually when a change in the HA_Chassis_Group happens; for
example, when a ``Chassis`` is removed from the database. But if a
node fails and the ``Chassis`` is not removed from the database, this
HA implementation will fail.
This bug proposes a more robust method that is not to pin the
``Logical_Router`` but to assign the ``HA_Chassis_Group`` to the GW
LRP. That provides a more robust HA support as long as OVN checks the
chassis interfaces, if one fails, it changes the GW LRP binding.
[1]https://bugs.launchpad.net/neutron/+bug/2052821
[2]https://review.opendev.org/c/openstack/neutron/+/909194
[3]https://review.opendev.org/c/openstack/neutron/+/909437
Jira reference: https://issues.redhat.com/browse/OSPRH-12265
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2101162/+subscriptions