yahoo-eng-team team mailing list archive

[Kailun Qin <1781179@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Currently, the normal method to reschedule a router is to send a
"removed" notification to the old l3 agent followed by an "added"
notification targeting the new agent.

However for DVR, this is too harsh as the old agent may still need to
keep the router in a non-master role to service any VM ports that exist
on that host while the new agent handles the master role of the router
(i.e., the centralized components of the router). Besides, the current
implementation in remove_router_from_l3_agent also verifies if there are
DVR serviceable ports owned by this agent. If so, then the router should
be retained.

The same mechanism should be aligned and applied to dvr rescheduling as
well.

** Affects: neutron
     Importance: Undecided
     Assignee: Kailun Qin (kailun.qin)
         Status: New


** Tags: rfe

** Changed in: neutron
     Assignee: (unassigned) => Kailun Qin (kailun.qin)

** Tags added: rfe

** Summary changed:

- [RFE] Send "update" instead of "remove" notification for dvr unscheduling
+ [RFE] Send "update" instead of "remove" notification for dvr rescheduling

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

Title:
  [RFE] Send "update" instead of "remove" notification for dvr
  rescheduling

Status in neutron:
  New

Bug description:
  Currently, the normal method to reschedule a router is to send a
  "removed" notification to the old l3 agent followed by an "added"
  notification targeting the new agent.

  However for DVR, this is too harsh as the old agent may still need to
  keep the router in a non-master role to service any VM ports that
  exist on that host while the new agent handles the master role of the
  router (i.e., the centralized components of the router). Besides, the
  current implementation in remove_router_from_l3_agent also verifies if
  there are DVR serviceable ports owned by this agent. If so, then the
  router should be retained.

  The same mechanism should be aligned and applied to dvr rescheduling
  as well.

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