We saw auto_schedule_routers took over 40 seconds
for a DVR enabled environment with option
auto_schedule_routers enabled.
Adding new arguments to get_router_agents_count and
dealing with routers separately depending on whether
it is a regular router or HA. The benefits are
we do not need to loop over every router available in
environment. Another reason for doing this is that
get_router_agents_count is used solely to heal
routers with less than required agents so number of
routers with less agents is small for most of the times.
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/842141 /opendev. org/openstack/ neutron/ commit/ d4654e3011d22b6 d789215fcaa1f15 f2d7b9a99a
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit d4654e3011d22b6 d789215fcaa1f15 f2d7b9a99a
Author: ushen <email address hidden>
Date: Tue May 17 18:50:44 2022 +0800
Filter out unsatisfied routers in SQL
We saw auto_schedule_ routers took over 40 seconds schedule_ routers enabled.
for a DVR enabled environment with option
auto_
Adding new arguments to get_router_ agents_ count and router_ agents_ count is used solely to heal
dealing with routers separately depending on whether
it is a regular router or HA. The benefits are
we do not need to loop over every router available in
environment. Another reason for doing this is that
get_
routers with less than required agents so number of
routers with less agents is small for most of the times.
Related-Bug: #1973656
Change-Id: Ic29275815a8c32 cee7a6470509687 a18fa594514