yahoo-eng-team team mailing list archive

[venkata anil <anil.venkata@xxxxxxxxxxxx>]

Public bug reported:

l2pop should use only binding info in db and not port status for db
entries.

Expected:
1) port creation - after binding, l2pop should send add_fdb_entries with new port info.
2) port deletion - after deleting port in db(and binding levels),
   l2pop should send remove_fdb_entries with deleted port info.
3) migration -
   a) after clearing the binding levels from old host,
      l2pop should send remove_fdb_entries with old host and port info.
   b) after binding to new host, l2pop should send add_fdb_entries
      with new host and port info.

With a new change, l2pop should work for only create_port, update_port and delete_port
notifications and ignore get_device_details, update_device_down and
update_device_up notifications.

context for bug is Kevin's comment in patchset 13
https://review.openstack.org/#/c/215467/

** Affects: neutron
     Importance: Undecided
     Assignee: venkata anil (anil-venkata)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => venkata anil (anil-venkata)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1535392

Title:
  l2pop should use only binding info in db and not port status for db
  entries.

Status in neutron:
  New

Bug description:
  l2pop should use only binding info in db and not port status for db
  entries.

  Expected:
  1) port creation - after binding, l2pop should send add_fdb_entries with new port info.
  2) port deletion - after deleting port in db(and binding levels),
     l2pop should send remove_fdb_entries with deleted port info.
  3) migration -
     a) after clearing the binding levels from old host,
        l2pop should send remove_fdb_entries with old host and port info.
     b) after binding to new host, l2pop should send add_fdb_entries
        with new host and port info.

  With a new change, l2pop should work for only create_port, update_port and delete_port
  notifications and ignore get_device_details, update_device_down and
  update_device_up notifications.

  context for bug is Kevin's comment in patchset 13
  https://review.openstack.org/#/c/215467/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1535392/+subscriptions