Ironic

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

Bug #1616878 reported by Pavlo Shchelokovskyy
This bug report is a duplicate of:  Bug #1526759: [RFE] Add service management API. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
In Progress
Wishlist
Madhuri Kumari

Bug Description

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.

Tags: rfe
Pavlo Shchelokovskyy (pshchelo)
summary: - expose which conductor instance is managing given Ironic node
+ [RFE} expose which conductor instance is managing given Ironic node
summary: - [RFE} expose which conductor instance is managing given Ironic node
+ [RFE] expose which conductor instance is managing given Ironic node
Revision history for this message
Dmitry Tantsur (divius) wrote :

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

Changed in ironic:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
Jim Rollenhagen (jim-rollenhagen) wrote :

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.

Revision history for this message
Ruby Loo (rloo) wrote :

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?

Revision history for this message
Madhuri Kumari (madhuri-rai07) wrote :

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

Changed in ironic:
assignee: nobody → Madhuri Kumari (madhuri-rai07)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ironic (master)

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

Changed in ironic:
status: Confirmed → In Progress
Revision history for this message
Madhuri Kumari (madhuri-rai07) wrote :

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on ironic (master)

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.