[RFE] API to get driver properties for a dynamic driver + non-default interfaces

Bug #1671549 reported by Ruby Loo on 2017-03-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
In Progress
Ruby Loo

Bug Description

Ironic doesn't provide any REST API to get access to the driver properties associated with a dynamic driver (hardware type) and non-default interfaces.

'GET /v1/drivers/<driver-or-hardware-type_name>/properties' returns the driver-related information that needs to be specified via node.driver_info[].

For classic drivers, this GET returns all the driver-related properties that are needed for setting the node's driver-related information.

However, for dynamic drivers (or hardware types), the GET returns the driver-related information associated with that hardware type AND its default interfaces. A node that uses a particular hardware type may not necessarily also use that hardware type's default interfaces. There is no API that will return all the driver-related information needed for this node.

For example, the difference between the response for 'agent_ipmitool' (classic) and 'ipmi' (dynamic) drivers is that the response for ipmi contains everything as agent_ipmitool, EXCEPT that ipmi is missing:

- 'image_http_proxy'
- 'image_https_proxy
- 'image_no_proxy',
- 'ipmi_terminal_console'.

This is because ipmi's default console interface is 'no-console' and default deploy interface is 'iscsi', while agent_ipmitool uses 'direct' for the deploy interface (which uses the image_* information) and ipmitool-shellinabox as the console interface (which uses

So for a node that has driver = 'impi' and console_interface = 'ipmitool-shellinabox', there is no way via the API to get the 'ipmi_terminal_console' driver property.

Ruby Loo (rloo) wrote :
Vladyslav Drok (vdrok) wrote :

Set the importance to wishlist as per our rfe process. I'm +1 on this.

Changed in ironic:
status: New → Triaged
importance: High → Wishlist
Ruby Loo (rloo) wrote :

wrt the tags; sorry -- was looking at the wrong rfe :-(

tags: added: rfe-approved
removed: rfe
tags: added: rfe
removed: rfe-approved

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

Changed in ironic:
status: Triaged → In Progress
Ruby Loo (rloo) on 2017-11-14
tags: added: needs-spec
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers