On Tue, Dec 12, 2017 at 01:26:33PM -0800, Kevin Lin wrote:
> Hi again,
>
> We’re trying to scale up our OVN deployment and we’re seeing some worrying
> log messages.
> The topology is 32 containers connected to another 32 containers on 10
> different ports. This is running on 17 machines (one
You're right that my patch was a bit of a short term hack. It
addressed a particular case where we could easily discard flows when
we know they could never match (because of the logical port included
in the match).
Use of conjunctive matches is a better more general solution to the
explosion of
Thanks for the replies!
We’re using v2.8.1.
I don’t completely understand Russell’s patch, but I don’t think our ACLs were
taking advantage of it. Do the ACLs need to be “tagged” with port information
in order for it to be useful?
Before, our ACLs were in terms of L3 and above. I brought down
Hey, which version are you using?, There are a couple of patches that
Russell submitted recently to avoid flows not necessary on specific
chassis, and I know Ben was looking at improving the bundle logic on
ovn-controller to also reduce the number of flows generated for address
sets.
On Tue, Dec
