API request to list resources should return only minimal data
Bug #1227431 reported by
aeva black
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic |
Fix Released
|
High
|
Lucas Alvares Gomes | ||
Bug Description
Requests to list top-level resources should return a "list of resources" with minimal identifying details, not a "set of resources" containing full details of every resource. This is both a UX and performance concern when returning very large numbers of resources in lists.
Chassis:
- uuid
- description
Node:
- uuid
- all four states
- instance_uuid
Port:
- uuid
- MAC address
| Changed in ironic: | |
| importance: | Undecided → High |
| status: | New → Triaged |
Revision history for this message
| aeva black (tenbrae) wrote | #1 |
| Changed in ironic: | |
| assignee: | nobody → Lucas Alvares Gomes (lucasagomes) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to ironic (master) | #2 |
| Changed in ironic: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to ironic (master) | #3 |
| Changed in ironic: | |
| status: | In Progress → Fix Committed |
| Changed in ironic: | |
| milestone: | none → icehouse-1 |
| status: | Fix Committed → Fix Released |
| Changed in ironic: | |
| milestone: | icehouse-1 → 2014.1 |
To post a comment you must log in.
We should do this the same way Nova v2 implements it, eg:
GET /v1/nodes -> list of nodes with minimal info,
GET /v1/nodes/details -> list of nodes with full details (what we return today, or possibly more),
GET /v1/nodes/{UUID} -> full details for the specified node (which we already do).