[RFE] Provides conductor status and node association
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Committed
|
Wishlist
|
Kaifeng Wang |
Bug Description
When using multiple ironic conductors in a deployment, nodes are distributed across conductors by hashring, there is no mechanism to know which conductor is currently serving a node.
Sometimes we need to locate the specific conductor to diagnose the cause of deploy failure, for example:
1. pxe boot failure
2. check deploy log sent by ipa
We also don't know how many conductor is alive or not, though a workaround is to list drivers, the information provided is from driver perspective, not conductors, and conductors not heartbeat in time is filtered out.
The proposal is to add an api endpoint for conductor status, something like /v1/conductors and /v1/conductors/
we can get a full conductor list:
GET /v1/conductors
Host Online Last Seen
compute01 YES 2017-10-18 07:34:07
compute03 YES 2017-10-18 07:35:01
compute06 NO 2017-10-17 14:11:53
which node is serviced by this conductor:
GET /v1/conductors/
online: YES
last seen: 2017-10-18 07:34:07
nodes: c5a379f1-
and add a conductor field to node show:
+------
| Property | Value |
+------
...
| uuid | eecc2a3e-
| conductor | compute01 |
+------
tags: | added: needs-spec |
Changed in ironic: | |
status: | New → Confirmed |
Changed in ironic: | |
assignee: | nobody → Kaifeng Wang (kaifeng) |
Thanks for the RFE. This looks similar to "[RFE] Add service management API" [1], so I'm going to mark this as a duplicate. If it isn't similar, please unduplicate. If it is the same, please help by e.g. reviewing the proposed spec for that.
[1] https:/ /bugs.launchpad .net/ironic/ +bug/1526759