[RFE] return node_uuid for port-list and portgroup-list

Bug #1703434 reported by Ruby Loo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
Triaged
Wishlist
Ruby Loo

Bug Description

We recently added two new resources, volume_connectors and volume_targets. By default, the REST API for listing these resources will return the node_uuid field. (That is, no need to explicitly specify the node_uuid field or to set detail=True in the request.)

For ports [2] and portgroups [3], the REST API to list them only returns the node_uuid field if that field is explicitly requested or if detail=True is specified in the API request. We discussed this in the ironic weekly meeting [1] and agreed that it would be good to return the node_uuid in these cases too.

I didn't look, but the changes to address this might need to be in ironic and ironicclient (OSC) code. Since we want to have feature parity between ironic & OSC in Pike, I don't think we should address this until Queens.

[1] http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-07-10-17.00.log.html#l-191

[2] https://developer.openstack.org/api-ref/baremetal/?expanded=list-portgroups-detail,list-ports-detail
[3] https://developer.openstack.org/api-ref/baremetal/?expanded=list-portgroups-detail

Tags: rfe-approved
Revision history for this message
Ruby Loo (rloo) wrote :

I'm assigning this to myself to prevent people submitting patches for this before Queens :-)

Revision history for this message
Julia Kreger (juliaashleykreger) wrote :

Marking approved as there seems to be agreement from Today's IRC meeting that this should be the case.

tags: added: rte-approved
Ruby Loo (rloo)
tags: added: rfe-approved
removed: rfe rte-approved
Revision history for this message
Afonne-CID (cidelight) wrote :

Is this still valid!

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

Other bug subscribers

Remote bug watches

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