Admin should be able to manually select the active instance of a HA router
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
The admin can see where is the active replica of an HA router. Once this bug: https:/
Is solved, the admin will be able to manually move HA routers from one agent to the next. Combining the two, it gives a decent if not ideal way to move the master by unscheduling it from the master node thereby moving it a backup:
For example if hosts A and B are hosting router R, and router R is active on host A, you can unschedule it from host A, invoking a failover and causing B to become the new active replica. You then schedule it to host A once more and it'll host the router again, this time as standby.
This RFE is about adding the ability to manually move the master state of a router from one agent to another explicitly. I think this can only be done with an API modification, or even a new API verb just for HA routers. I think that any API modifications need a slim spec and an RFE bug is not enough.
Changed in neutron: | |
importance: | Undecided → Wishlist |
Changed in neutron: | |
importance: | Wishlist → Medium |
tags: | added: api |
Changed in neutron: | |
assignee: | nobody → yong sheng gong (gongysh) |
Changed in neutron: | |
importance: | Medium → Low |
tags: |
added: rfe-approved removed: rfe |
Changed in neutron: | |
importance: | Low → Wishlist |
Changed in neutron: | |
milestone: | none → mitaka-1 |
Changed in neutron: | |
milestone: | mitaka-1 → mitaka-2 |
Changed in neutron: | |
assignee: | yong sheng gong (gongysh) → Hong Hui Xiao (xiaohhui) |
status: | Triaged → In Progress |
Changed in neutron: | |
status: | In Progress → Incomplete |
assignee: | Hong Hui Xiao (xiaohhui) → nobody |
milestone: | mitaka-2 → none |
Changed in neutron: | |
assignee: | nobody → Hong Hui Xiao (xiaohhui) |
status: | Incomplete → In Progress |
Changed in neutron: | |
status: | Won't Fix → New |
Gongysh I updated the bug description since a lot of things have changed since I reported this.