[RFE][L3] l3-agent should have its capacity
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
In Progress
|
Wishlist
|
LIU Yulong |
Bug Description
Recently we meet some scale issue about L3-agent. According to what I'm informed, most cloud service provider does not charge for the neutron virtual router. This can become a headach for the operators. Every tenant may create free routers for doing nothing. But neutron will create many resource for it, especially the HA scenario, there will be namespaces, keepalived processes, and monitor processes. It will absolutely increase the failure risk, especially for agent restart.
So this RFE is aimming to add a scheduling mechanism, and for l3-agent, it will collect and report some resource usage, for instance available bandiwidth. So during the router scheduler process, if there is no more available, the number of routers can be under a controlled range.
Changed in neutron: | |
assignee: | nobody → LIU Yulong (dragon889) |
status: | New → In Progress |
tags: | added: rfe |
tags: |
added: rfe-triaged removed: rfe-confirmed |
First of all, to control number of resources used by tenants, there is quota mechanism. So it can be limited easily. /github. com/openstack/ neutron/ blob/master/ neutron/ scheduler/ l3_agent_ scheduler. py ? Isn't LeastRoutersSch eduler (https:/ /github. com/openstack/ neutron/ blob/master/ neutron/ scheduler/ l3_agent_ scheduler. py#L344) something what You are describing here?
Second - is this rfe about adding new scheduler driver to https:/