[ovs-dev] [PATCH 0/8] Add minimum network namespace support.

Ben Pfaff blp at ovn.org
Fri Nov 3 19:17:35 UTC 2017


On Thu, Nov 02, 2017 at 05:05:01PM -0200, 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 being proposed to netdev 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.

This seems like a very reasonable series to me, although I have not
reviewed it in detail.  Thank you for doing this work.

I'm hoping that Jiri or another Linux networking expert will take a look
at this series before me.  Jiri, are you planning to do that?


More information about the dev mailing list