agent/linux/bridge_lib: Not all methods of BridgeDevice respect namespaces

[Adriaan Schmidt]

Looking at agent/linux/bridge_lib.py, I see that most methods of BridgeDevice use calls to brctl, using a namespace wrapper. They work as expected.

However, some methods (get_interface_bridge, owns_interface, get_interfaces) retrieve information from the file system, and do not work if the bridge device lives in a namespace.

[Brian Haley (brian-haley)]

Yes, it looks like those methods don't deal with namespaces, but from what I know, the linux bridge agent does not run in a namespace, so this isn't causing a problem. Do you have a case where there is a namespace?

[Adriaan Schmidt (adriaan-schmidt)]

I'm writing a device_driver for neutron-vpnaas, similar to the proposed (but then abandoned) SSLVPN (https://wiki.openstack.org/wiki/Neutron/VPNaaS/SSLVPN). This starts an OpenVPN process inside a router namespace, which allows clients to connect to Neutron networks.

For me it is important that the clients are in the same broadcast domain as the instances. So, the current VPNaaS solutions based on IPSEC and policy-based routing don't work for me. My current solution is to configure OpenVPN to use a tap device, and connect this to the router internal port via a bridge, all inside the router namespace.

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]