----- Original Message ----- > > *From:* Ian Wells [mailto: ijw.ubuntu at cack.org.uk ] > *Sent:* Wednesday, > > March 25, 2015 2:18 AM > > That spec ensures that you can tell what the > > plugin is doing. You can ask > for a VLAN transparent network, but the > > cloud may tell you it can't make > one. > > If you want to use a VLAN > > trunk using the current code, I recommend VXLAN > or GRE along with the > > Linuxbridge driver, both of which support VLAN > transparent networking. > > If they're configured and you ask for a VLAN trunk > you'll be told you > > got one. > The linuxbridge agent does not support GRE. > I tried sending tagged packets over linuxbridge+VxLAN and it did not work - I > didn't look into it any further.
This was a strong premise of the spec when it was under discussion, that we at least some part of the reference implementation (LB + VXLAN was cited) that works. If it doesn't, I think it's problematic to introduce new API without a reference implementation. > I also tried over linuxbridge+FLAT - this works when the physical switch > ports are trunks - they would need to permit all VLAN ids to be fully "VLAN > transparent". > I think linuxbridge+VLAN would work too, as along as the switch ports are > also configured for Q-in-Q. > Currently the linuxbridge mechanism driver cannot know if a Neutron network > is VLAN transparent or not. > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
