@Slawek,
Thanks for the feedback. I know quota. But for a public cloud, the user (tenant) may be free to register. Then they will have some free quota. The unrestricted growth of tenant number will let the router number or any other free resource reach a unbearable number of cluster.
For the second, yes, a scheduling mechanism based on some physical resource will be needed, for intance physical NIC bandwidth ratio. LeastRoutersScheduler can not work, since we do not have a maximum quantity for l3-agent. So router still is free to schedule to any l3-agent.
@Slawek, eduler can not work, since we do not have a maximum quantity for l3-agent. So router still is free to schedule to any l3-agent.
Thanks for the feedback. I know quota. But for a public cloud, the user (tenant) may be free to register. Then they will have some free quota. The unrestricted growth of tenant number will let the router number or any other free resource reach a unbearable number of cluster.
For the second, yes, a scheduling mechanism based on some physical resource will be needed, for intance physical NIC bandwidth ratio. LeastRoutersSch