Open Stack

----- Original Message -----
> From: "Jens Rosenboom" <j.rosenboom at x-ion.de>
> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
> Sent: Friday, April 10, 2015 1:47:42 PM
> Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network
> to Neutron migration work]
> 
> 2015-04-10 12:29 GMT+02:00 Attila Fazekas < afazekas at redhat.com > :
> 
> 
> 
> 
> 
> 
> ----- Original Message -----
> > From: "Jens Rosenboom" < j.rosenboom at x-ion.de >
> > To: "OpenStack Development Mailing List (not for usage questions)" <
> > openstack-dev at lists.openstack.org >
> > Sent: Friday, April 10, 2015 10:18:38 AM
> > Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in
> > DevStack [was: Status of the nova-network
> > to Neutron migration work]
> > 
> > 2015-04-10 9:05 GMT+02:00 Attila Fazekas < afazekas at redhat.com > :
> > 
> > 
> > Hi,
> > 
> > I do not recommend Linux bridge as default for devstack.
> > 
> > I think most developer does not have a switch configured with trunk ports,
> > or tricks for faking it in a visualized environment.
> > 
> > 
> > ​I would argue this to be a non issue. Most developers will only run single
> > node setups anyway.
> > If they setup multiple nodes connected with a switch that happens not to be
> > VLAN aware, it will
> > most likely still be VLAN transparent at the same time, so things still
> > will
> > just work. This
> > also includes the propably most common case of multiple qemu instances
> > connected via a Linuxbridge
> > device on the host.
> 
> It is for untagged traffic only.
> 
> ​Can you please be more specific here? For me, if I have a setup like
> 
> vm1:eth0 <-> host:br0 <-> vm2:eth0
> 
> then I can use e.g. eth0.100 between the two VMs just fine.​
> ​ This is for a plain
> libvirt based setup on my workstation, not within OpenStack.​
> 

Did you defined a br.100 next to the br0 ?
http://blog.davidvassallo.me/2012/05/05/kvm-brctl-in-linux-bringing-vlans-to-the-guests/

The usual issue with libvirt and libvirt based tools they automatically
add filtering rules against tagged traffic, so first usually 
you had to convince the system to do not do it.

In Openstack the tagged traffic also frequently filtered because.:
The double tagging not supported by the hardware and/or by the plugin.
You cannot create your own virtual vlan aware switch on the API,
the Openstack L2 segments by default are not vlan aware.


> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>