ovs agent: provision_local_vlan shouldn't set-up flooding flows when l2pop is activated

[Francois Eleouet]

When l2-population option is activated, provision_local_vlan shoudln't set up a flow to flood packets on every tunnel ports. This is not a big issue as corresponding flow is overwritten as soon as the first fdb_add call is recieved, but it is anyway unecessary and should be removed.

[Romil Gupta (romilg)]

Investigating

[ding bo (longddropt)]

Not sure it is a bug, because if a port which is not managed by neutron(thus is not visible by neutron), we still need the broadcasting flow to make it reachable. Anyway, the patch is here if needed:https://review.openstack.org/#/c/230917/

[kbaikov (kbaikov)]

I have the same thing almost:

https://review.openstack.org/#/c/226875/

a bit more succinct i guess.

On Mon, Oct 5, 2015 at 11:41 AM ding bo <[e-mail]> wrote:

> Not sure it is a bug, because if a port which is not managed by
> neutron(thus is not visible by neutron), we still need the broadcasting
> flow to make it reachable. Anyway, the patch is here if
> needed:https://review.openstack.org/#/c/230917/
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1312257
>
> Title:
> ovs agent: provision_local_vlan shouldn't set-up flooding flows when
> l2pop is activated
>
> Status in neutron:
> New
>
> Bug description:
> When l2-population option is activated, provision_local_vlan shoudln't
> set up a flow to flood packets on every tunnel ports. This is not a
> big issue as corresponding flow is overwritten as soon as the first
> fdb_add call is recieved, but it is anyway unecessary and should be
> removed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/neutron/+bug/1312257/+subscriptions
>

[Launchpad Janitor (janitor)]

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