On Tue, Apr 03, 2018 at 09:48:55PM -0300, Flavio Leitner wrote:
> On Sat, Mar 31, 2018 at 01:23:20PM -0700, Ben Pfaff wrote:
> > On Thu, Mar 29, 2018 at 11:05:25PM -0300, Flavio Leitner wrote:
> > > Today Open vSwitch doesn't know about network namespaces (netns), but
> > > users are moving internal ports to other namespaces. Although packets
> > > are still flowing, the daemon fails to find out basic port information,
> > > like if it is UP or DOWN, for instance.
> > >
> > > This patchset rely on a new kernel vport API recently accepted to find
> > > out the new network namespace ID of a bridge's port. This information
> > > along with the port's name recorded in the database is used to match the
> > > corresponding netlink messages.
> > >
> > > This patchset also leverages another kernel API that allows the daemon
> > > to listen to all netlink messages from all netns which has an ID assigned
> > > into it. This and the previous change allows the userspace to track ports
> > > in other network namespaces.
> > >
> > > If any of the APIs aren't available, it falls back to the older APIs to
> > > not break backwards compatibility.
> > I applied this to master. Thank you!
> > I have a request: please submit a patch to add something to NEWS to
> > explain the new features.
> Will do.
I sent out a patch:
dev mailing list