Re-balance command for gateway ports
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-ovn |
In Progress
|
Wishlist
|
Maciej Jozefczyk |
Bug Description
--Update description:
I raise this bug based on a realistic question. When we have two gateways and already a lot of lrouters, one of the ovn-controllers is upgraded, all the gateway-ports are scheduled to the other gateway and we can only rebalance them manually by setting OVN NB.
But,it's not easy to distinguish between different scenarios, I will add a command to do this first, and postpone automatical rebalancing until thorough discussions.
Usually, in a real environment, we have multiple gateway chassis for load balancing. But the gateway ports are not re-balanced when a new chassis is added or an existing chassis is updated for physical mapping. This problem is obvious when there are already multiple lRouters. In a re-balancing strategy, we should try to keep most of the lRouters from being affected.
summary: |
- Re-balance for gateway port + Re-balance for gateway ports |
description: | updated |
summary: |
- Re-balance for gateway ports + Re-balance command for gateway ports |
description: | updated |
Changed in networking-ovn: | |
assignee: | nobody → Maciej Jozefczyk (maciej.jozefczyk) |
Changed in networking-ovn: | |
status: | Confirmed → In Progress |
Hi Jun, I think auto-rebalancing would impact existing traffic. From operational perspective, I would prefer balancing only for newly added lrouters without touching existing lrouters automatically. What do you think?