[openstack-dev] Need of L3-Agent to Router Binding

Eugene Nikanorov enikanorov at mirantis.com
Wed Aug 14 14:42:03 UTC 2013


Hi Rahul,

> In which scenario will I have more than one l3agents installed in my
setup?
You may start l3agent on each of your compute nodes so routers are
distributed across nodes.
It also would allow to implement failover for l3 agents: when some node
with l3 agent fails, router may be rescheduled (bound to another) l3agent

Thanks,
Eugene.


On Wed, Aug 14, 2013 at 6:19 PM, Rahul Sharma <rahulsharmaait at gmail.com>wrote:

> Hi All,
>
> I am having a basic query on the need of l3agent to router binding. If we
> have a look at current code, we keep a binding of "l3agent to the router"
> which it has created. Why do we do that? I am unable to think out the
> possible reason in doing so.
>
> In which scenario will I have more than one l3agents installed in my setup?
>
> I faced an issue because of this while doing HA of the network node. On
> switchover/failover, I have to change the l3agent to router binding so that
> traffic works smoothly. We have a binding for "Network to DHCP-agent" which
> is required. But I am still guessing why I need binding for l3agent to
> router.
>
> Can you please provide some pointers for this. It would be really helpful.
>
> Thanks and Regards
> Rahul Sharma
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130814/71f854e8/attachment.html>


More information about the OpenStack-dev mailing list