Oleg Bondarev 0496f95a13 Remove bindings of DVR routers to L3 agents on compute nodes ... As described in the spec there is no need to explicitly bind DVR router to each l3 agent running on compute nodes where there are dvr serviceable ports - this brings complexity to the code, makes it less readable and very hard to maintain (one could see how many bugs were filed and fixed regarding dvr scheduling stuff already). Also this brings scalability problems as time needed for router scheduling grows linearly with the number of compute nodes. The idea is to align dvr scheduling with legacy router scheduling: only schedule SNAT portion of the router and use DB queries whenever we need to know which compute nodes should host the router. Implements blueprint improve-dvr-l3-agent-binding Change-Id: I82c8d256c56bb16cdc1b1232ebb660d09909f9c6		2016-02-01 17:06:50 -07:00
..
__init__.py	Empty files should not contain copyright or license	2014-10-20 00:50:32 +00:00
base_resource_filter.py	DHCP Service LoadBalancing Scheduler	2015-03-18 10:13:53 -07:00
base_scheduler.py	Fix alignment in message and remove unused module	2015-11-26 08:16:45 +00:00
dhcp_agent_scheduler.py	Move i18n to _i18n, as per oslo_i18n guidelines	2015-12-01 19:29:10 -07:00
l3_agent_scheduler.py	Remove bindings of DVR routers to L3 agents on compute nodes	2016-02-01 17:06:50 -07:00