l2 population fdb updates being sent to all agents

Bug #1647570 reported by Arun Kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Won't Fix
Wishlist
Arun Kumar

Bug Description

l2 population mechanism driver sends out fdb update to all registered agents when a new VM is spawned on an agent for a network (First port activated on current agent in this network)

It should only send out fdb updates to agents which have l2population enabled as this affects performance in large scale deployments.

Tags: l2-pop
Arun Kumar (arooncoomar)
Changed in neutron:
assignee: nobody → Arun Kumar (arooncoomar)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/407373

Changed in neutron:
status: New → In Progress
Changed in neutron:
importance: Undecided → Low
tags: added: l2-pop
Revision history for this message
Kevin Benton (kevinbenton) wrote :

I would rather focus on eliminating the l2pop driver entirely.

Changed in neutron:
importance: Low → Wishlist
status: In Progress → Won't Fix
status: Won't Fix → In Progress
status: In Progress → Won't Fix
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Kevin Benton (<email address hidden>) on branch: master
Review: https://review.openstack.org/407373
Reason: This seems to be targeting a very narrow use case for performance (mixed l2pop enabled/disabled environments) and it shouldn't be causing any side effects. If you are noticing failures without this, those are other bugs that should be addressed directly.

I would like to focus on eliminating the l2pop driver entirely instead.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.