-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
rhos-18.0.0
-
None
-
[OVN] External ports connected to a router should be scheduled in the same GW nodes
-
8
-
False
-
-
False
-
Not Selected
-
Proposed
-
Proposed
-
In Progress
-
Proposed
-
Proposed
-
33% To Do, 33% In Progress, 33% Done
-
-
-
Goal:
In OVN, baremetal ports and SR-IOV ports are considered as external. It is needed to bind these external ports to a chassis to receive/send traffic to the physical ports.
In Neutron ML2/OVN, there are two different strategies to schedule ports:
- Router gateway ports: the OVN L3 scheduler uses a set of Gateway_Chassis registers, associated to different gateway nodes, to provide HA to the router gateway ports. This set of Gateway_Chassis registers are associated 1:1 to a single router. That means, each router will have its own independent set of Gateway_Chassis registers.
- External ports: once created, the ML2/OVN plugin creates a HA_Chassis_Group with different HA_Chassis registers, associated to different gateway chassis. This is similar to the previous strategy (but Gateway_Chassis will be deprecated). A HA_Chassis_Group is created per network.
If an external port is connected to a router, nothing guarantees that the external port is bound to the same chassis as the router gateway port. The goal of this epic is to provide a method to, once an external port (its network) is connected to a router, the scheduler of both resources matches and both ports (external port, router gateway port) are bound to the same chassis.
This feature is needed in U/S master and RHOSO18.
Acceptance Criteria:
Regardless of the strategy adopted and implemented, when an external port is connected to a router, both this external port and the router gateway port must be bound to the same gateway chassis.