[Openstack-operators] Flat network with linux bridge plugin

Daniele Venzano daniele.venzano at eurecom.fr
Wed Apr 8 08:00:12 UTC 2015

Well, I found a way to make it work.

Yes, you need a bridge (brctl addbr ...).

You need to create it by hand and add the interfaces (physical and dnsmasq namespace) to it.

The linuxbridge agent installed on the network node does not do anything.


The problem with this is that the interface for the namespace is created after an arbitrary amount of time by one of the neutron daemons, so you cannot simply put the bridge creation in one of the boot scripts, but you have to wait for the interface to appear.



From: Sam Morrison [mailto:sorrison at gmail.com] 
Sent: Wednesday 08 April 2015 05:46
To: Daniele Venzano
Cc: openstack-operators at lists.openstack.org
Subject: Re: [Openstack-operators] Flat network with linux bridge plugin


Hi Daniele,


I’ve started playing with neutron too and have the exact same issue. Did you find a solution?







On 18 Feb 2015, at 8:47 pm, Daniele Venzano <Daniele.Venzano at eurecom.fr> wrote:




I’m trying to configure a very simple Neutron setup.


On the compute nodes I want a linux bridge connected to a physical interface on one side and the VMs on the other side. This I have, by using the linux bridge agent and a physnet1:em1 mapping in the config file.


On the controller side I need the dhcp and metadata agents. I installed and configured them. They start, no errors in logs. I see a namespace with a ns-* interface in it for dhcp. Outside the namespace I see a tap* interface without IP address, not connected to anything.

I installed the linux bridge agent also on the controller node, hoping it would create the bridge between the physnet interface and the dhcp namespace tap interface, but it just sits there and does nothing.


So: I have VMs sending DHCP requests. I see the requests on the controller node, but the dhcp namespace is not connected to anything.

I can provide logs and config files, but probably I just need a hint in the right direction.


On the network controller:

Do I need a bridge to connect the namespace to the physical interface?

Should this bridge be created by me by hand, or by the linuxbridge agent? Should I run the linuxbridge agent on the network controller?


I do not want/have a l3 agent. I want to have just one shared network for all tenants, very simple.




OpenStack-operators mailing list
 <mailto:OpenStack-operators at lists.openstack.org> OpenStack-operators at lists.openstack.org
 <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150408/b4c90a62/attachment.html>

More information about the OpenStack-operators mailing list