Magnum should allow to disable a conductor service like other openstack components.
Bug #1607228 reported by
rajiv
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Magnum |
In Progress
|
Medium
|
rajiv | ||
| python-magnumclient |
Triaged
|
Medium
|
rajiv | ||
Bug Description
Currently magnum has only service list option but there must be an option to enable/disable a service. In case someone wants to take off a node from the cluster for maintenances purpose and later on join the same node into the cluster.
| Changed in magnum: | |
| assignee: | nobody → rajiv (rajiv-kumar) |
| Changed in python-magnumclient: | |
| assignee: | nobody → rajiv (rajiv-kumar) |
| description: | updated |
| Changed in magnum: | |
| status: | New → Triaged |
| Changed in python-magnumclient: | |
| status: | New → Triaged |
| Changed in magnum: | |
| importance: | Undecided → Medium |
| Changed in python-magnumclient: | |
| importance: | Undecided → Medium |
Revision history for this message
| Eli Qiao (taget-9) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to magnum (master) | #2 |
| Changed in magnum: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on magnum (master) | #3 |
To post a comment you must log in.
This is confusing.
I suggest that in this bug we fix that "magnum service-list not show disabled" as https:/
You may need 2 patch to fix it:
1. for magnum-api, add disabled value to magnum service-list return, this may need a microversion, since you may modify the response of an API. For microversion, need to wait for the discussion result .
2. for python-
As I commented on https:/
also need microversion and also a python-magnumclient patch.
Eli.