[ovn] external port always be scheduled on a single gateway
Bug #1922824 reported by
Liu Xie
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Unassigned |
Bug Description
At the moment, all external ports will be scheduled on a single gateway node since there’s only one HA Chassis Group for all of those ports.[1]
I think this issue could be solved like l3-ha [2].
[1]https:/
[2]https:/
description: | updated |
tags: | added: ovn |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
To post a comment you must log in.
Hi,
That´s correct, currently all external ports are scheduled on a single node because in OVN they are all included in a single HA_Chassis_Group (called default_ ha_chassis_ group).
But, this will soon change (I expect) with a patch adding support for Network AZs for the ML2/OVN driver [0] (sorry for the lacking of commit message there, I expect to finish this patch in the next days, atm it´s WIP).
But with that patch I want to create a HA Chassis Group per netowrk [1] where the external ports will be placed to. That way, we will no longer have a single node holding all the external ports in it.
[0] https:/ /review. opendev. org/c/openstack /neutron/ +/762550 /review. opendev. org/c/openstack /neutron/ +/762550/ 6/neutron/ plugins/ ml2/drivers/ ovn/mech_ driver/ ovsdb/ovn_ client. py
[1] https:/