Indeed fixing unscheduled router is useful but IMO it does not quite fits with the
option name "router_auto_schedule", by its name, it more sounds like users/operators choose to
schedule router to agent on their own.
I am bringing this option up is because the logic to find an unscheduled router is rather expensive and could causes heavy burden on database each time l3 agent reboots.
IMO creating new routers while all l3 agents are down are pretty rare situations so the cost of
this option IMO might not be quite paid off...
Indeed fixing unscheduled router is useful but IMO it does not quite fits with the auto_schedule" , by its name, it more sounds like users/operators choose to
option name "router_
schedule router to agent on their own.
I am bringing this option up is because the logic to find an unscheduled router is rather expensive and could causes heavy burden on database each time l3 agent reboots.
IMO creating new routers while all l3 agents are down are pretty rare situations so the cost of
this option IMO might not be quite paid off...