[RFE] expose which conductor instance is managing given Ironic node

[Pavlo Shchelokovskyy]

Currently there is now way to detect this programmatically.

Problem: there are many conductor nodes, and node deploy fails. Which conductor node should operator log into to check the logs?

Possible ways to address this:

1) create a new API endpoint e.g. 'v1/service' that can report which conductor is managing given node. Additionally it can also report aliveness of all Ironic conductors and on which hosts they are running (similar to nova service-list)

2) expose conductor_affinity in node-show (but resolve it to hostname first).

Option 2) is probably quicker to implement, but option 1) has more benefits for operators.

[Dmitry Tantsur (divius)]

+1, I'd go for option #2, as we already have some conductor reporting in /v1/drivers

[Jim Rollenhagen (jim-rollenhagen)]

I'd prefer folks just use centralized logging. This is an internal implementation detail. I'm not saying "no" right now, but I'm leaning that way. Curious to hear other real-world use cases for this.

[Ruby Loo (rloo)]

I like #1 because of its flexibility to providing more information in the future.

Seems like a question for operators? Would it be worth asking on the mailing list?

[Madhuri Kumari (madhuri-rai07)]

I am assigning this bug to myself. I have posted similar bug for this https://bugs.launchpad.net/ironic/+bug/1686670

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/474512

[Madhuri Kumari (madhuri-rai07)]

This bug talking about exposing the ironic-conductor services by adding a new API endpoint /service which is a subset of service management API which is proposed in bug #1526759

[OpenStack Infra (hudson-openstack)]

Change abandoned by "Dmitry Tantsur <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/ironic/+/474512
Reason: This has been implement in the form of /v1/conductors