neutron/neutron/scheduler
Rodolfo Alonso Hernandez 413044f253 [OVN] The L3 scheduler does not use all chassis by default
Any OVN scheduler, inheriting from ``OVNGatewayScheduler``, calls
``_schedule_gateway`` to make the decision of in what chassis the
router gatweway should be located. Before this patch, if the list
of candidates was empty, the scheduler used all available chassis
as candidate list. This patch is removing this default behaviour.
In a deployment, only those chassis marked explicitly with
"ovn-cms-options=enable-chassis-as-gw" can be used as gateway
chassis.

After enabling this patch, any existing router gateway port will
preserve the assigned chassis; any new router gateway will be
scheduled only on the chassis configured as gateways.

If a router gateway port cannot find any chassis to be scheduled,
the "neutron-ovn-invalid-chassis" will be used instead and a
warning message will be printed in the logs.

Closes-Bug: #2019217
Change-Id: If0f843463edfd7edc5c897cc098de31444f9d81b
2023-05-25 15:26:31 +02:00
..
__init__.py Empty files should not contain copyright or license 2014-10-20 00:50:32 +00:00
base_resource_filter.py Do not fail if the agent load is not bumped 2021-08-25 13:06:28 +00:00
base_scheduler.py Improve scheduling L3/DHCP agents, missing lower binding indexes 2023-02-08 13:14:19 +01:00
dhcp_agent_scheduler.py Improve scheduling L3/DHCP agents, missing lower binding indexes 2023-02-08 13:14:19 +01:00
l3_agent_scheduler.py Filter out unsatisfied routers in SQL 2023-03-29 21:25:10 +08:00
l3_ovn_scheduler.py [OVN] The L3 scheduler does not use all chassis by default 2023-05-25 15:26:31 +02:00