Hi Swaminathan Vasudevan,
please check the following docstring
of L3_NAT_dbonly_mixin._check_router_needs_rescheduling:
*def _check_router_needs_rescheduling(self, context, router_id,
gw_info):*
*Checks whether router's l3 agent can handle the given network*
*When external_network_bridge is set, each L3 agent can be
associated*
*with at most one external network. If router's new external
gateway*
*is on other network then the router needs to be rescheduled to the*
*proper l3 agent.*
*If external_network_bridge is not set then the agent*
*can support multiple external networks and rescheduling is not
needed*
So there can still be agents which can handle only one ext net - for such
agents resheduling is needed.
Thanks,
Oleg
On Wed, Dec 17, 2014 at 8:56 PM, Vasudevan, Swaminathan (PNB Roseville)
swaminathan.vasude...@hp.com wrote:
Hi Folks,
*Reschedule router if new external gateway is on other network*
An L3 agent may be associated with just one external network.
If router's new external gateway is on other network then the router
needs to be rescheduled to the proper l3 agent
This patch was introduced when there was no support for L3-agent to handle
multiple external networks.
Do we think we should still retain this original behavior even if we have
support for multiple external networks by single L3-agent.
Can anyone comment on this.
Thanks
Swaminathan Vasudevan
Systems Software Engineer (TC)
HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
