[Openstack-operators] [grizzly][quantum] Router/DHCP interface OVS port tags not reliably implementing

Édouard Thuleau thuleau at gmail.com
Mon Jan 20 21:23:38 UTC 2014

In fact, OVS agent use a local VLAN (lvid) to isolate network
segmentation onto the compute host.
Traffic outgoing the compute host will use other (on all the data
center network fabric) isolation mechanism (VLAN, GRE, VXLAN...).
When Nova adds a port into the 'br-int' switch, OVS agent asks Neutron
plugin controller to know port's details and sets local VLAN of the
port's segment (choose one if it's the first port or set the lvid
already chosen).


On Mon, Jan 20, 2014 at 12:39 PM, Jesse Pretorius
<jesse.pretorius at gmail.com> wrote:
> On 20 January 2014 10:42, Édouard Thuleau <thuleau at gmail.com> wrote:
>> I met a similar problem but only with VM tap (not with router or DHCP
>> ports).
>> We proposed a fix [1] we attached with an opening bug [2].
>> The fix isn't yet ready (status WIP). Another patch [3] make a lot
>> change on this part of code (OVS agent interface loop). So we prefer
>> to wait it was finished to rebase our proposition on it.
>> [1] https://review.openstack.org/#/c/66375/
>> [2] https://bugs.launchpad.net/nova/+bug/1240849
>> [3] https://review.openstack.org/#/c/61964/
> Thanks Édouard. If I understand your patch [1] correctly, it reviews all
> existing ports and checks for tags. This should work for any tagged ports,
> not just VLAN tagged port, correct?
> If so this patch is a really great addition and really should be backported!
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

More information about the OpenStack-operators mailing list