Open Stack

Some one posted a bug [1] for vlan arp responder and vlan l2population, which use the merged patch [2] for supporting the same thing in the ofagent



So for DVR for vlan, I think we can continue with the bug fix above.





[1] https://bugs.launchpad.net/neutron/+bug/1413056



[2] https://review.openstack.org/#/c/112947/





________________________________
From: huangdenghui [hdh_1983 at 163.com]
Sent: Sunday, November 29, 2015 4:09 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron][L3][DVR][arp]

If those 200 subnets are VXLAN networks, i think it is a good idea, since L2population already  propagate this configuration to OVS-Agent.

One comment for VLAN network, since DVR also support in VLAN network and L2population is not necessary in it, what is your consideration in this case?




At 2015-11-29 14:15:11, "Wuhongning" <wuhongning at huawei.com> wrote:
>Is it a good idea to add a configuration item for dvr, to disable any arp entry processing, and reuse arp response from L2population?
>
>When no static arp entry is found in qrouter namespace, it would cause a temp arp request, then it reached the br-tun, and replied by the OVS flow table.
>
>In a public cloud like AWS, it allow 200 subnets for each vpc, so sync routes would waste a lot of time
>__________________________________________________________________________
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>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/20151201/a0bdf6e9/attachment.html>