[ovs-dev] [PATCH v4 3/3] ovn-controller: Allocate ct zones for localnet ports.

[Kyle Mestery]

On Wed, Feb 3, 2016 at 9:14 AM, Russell Bryant <russell at ovn.org> wrote:
> On 02/02/2016 05:19 PM, Ben Pfaff wrote:
>> On Mon, Jan 25, 2016 at 05:02:03PM -0500, Russell Bryant wrote:
>>> Previously, all ct() actions applied to localnet ports used the default
>>> conntrack zone.  We should allocate a ct zone ID for all localnet ports
>>> just like we do for all local VIFs so that none of our connection
>>> tracking interferes with any base system connection tracking in the
>>> default zone.
>>>
>>> Signed-off-by: Russell Bryant <russell at ovn.org>
>>
>> Acked-by: Ben Pfaff <blp at ovn.org>
>>
>
> Thanks!  I pushed this series to master.
>
> I started backporting this to branch-2.5.  There's some conflicts and
> then the test case seems to lock up my laptop.  At that point I wondered
> how much we care about OVN backports to branch-2.5 because we're very
> quickly going to get to where we'd want anyone doing real OVN testing to
> use ovs master again as we add more features and performance enhancements.
>
>From my perspective, we'll be using master, so I'm ok with only
dealing with that. But I can see some benefit to trying to keep things
like this in 2.5 as well, so I defer to your and other's judgement.

> --
> Russell Bryant
> _______________________________________________
> dev mailing list
> dev at openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev