[OVN] Collocate the external ports in the same chassis as the gateway port
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
In Progress
|
Medium
|
Rodolfo Alonso | ||
Bug Description
This bug is related to the N/S routing capabilities in ML2/OVN.
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 bug 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.
Jira ticket: `https:/
Bugzilla: https:/
| Changed in neutron: | |
| assignee: | nobody → Rodolfo Alonso (rodolfo-alonso-hernandez) |
| importance: | Undecided → Medium |

Fix proposed to branch: master /review. opendev. org/c/openstack /neutron/ +/962155
Review: https:/