Send "update" instead of "remove" notification for dvr rescheduling
Bug #1781179 reported by
Kailun Qin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Kailun Qin |
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_
The same mechanism should be aligned and applied to dvr rescheduling as well.
Changed in neutron: | |
assignee: | nobody → Kailun Qin (kailun.qin) |
tags: | added: rfe |
summary: |
[RFE] Send "update" instead of "remove" notification for dvr - unscheduling + rescheduling |
Changed in neutron: | |
importance: | Undecided → Medium |
tags: |
added: l3-dvr removed: rfe |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/581658
Review: https:/