Re: [ovs-dev] [PATCH v2] ovn-controller: Fix duplicated flows in table 32.

Hi Darrell, Sorry for late response. I posted v3 just now. On Wed, Dec 14, 2016 at 12:19 PM, Darrell Ball wrote: > > ERROR log level is not appropriate since we always filter adding the extra flows anyways > > and it amount to extra processing and filtering. > > We anyways

Re: [ovs-dev] [PATCH v2] ovn-controller: Fix duplicated flows in table 32.

From: Han Zhou <zhou...@gmail.com> Date: Wednesday, December 14, 2016 at 11:53 AM To: Darrell Ball <db...@vmware.com> Cc: "d...@openvswitch.org" <d...@openvswitch.org> Subject: Re: [ovs-dev] [PATCH v2] ovn-controller: Fix duplicated flows in table 32. On Wed, Dec

Re: [ovs-dev] [PATCH v2] ovn-controller: Fix duplicated flows in table 32.

On Wed, Dec 14, 2016 at 9:36 AM, Darrell Ball wrote: > > > > On 12/13/16, 11:15 PM, "ovs-dev-boun...@openvswitch.org on behalf of Han Zhou" wrote: > > In commit 475f0a2c it introduced a priority 150 flow for

[ovs-dev] [PATCH v2] ovn-controller: Fix duplicated flows in table 32.

In commit 475f0a2c it introduced a priority 150 flow for filtering the sending of traffic received from vxlan tunnels back out tunnels. However, it added the flow for every remote port processing, which results in continuous logs about duplicated flows. We only need to install this flow once per