As Tuskar API user I would like to get the rack of a node when I get a node resource

Registered by Martyn Taylor

As Tuskar API user I would like to get the rack of a node when I get a node resource

ce. - 3
so nodes will exist as a top-level resource type (right now only exposed via racks)
It makes sense that for now, when you retrieve a node (GET /v1/nodes/1 for eg) it *will* be associated with a rack (i.e. nodes can't just exist w/out being associated)
this will be read-only right now - can't delete/update/create nodes via this API mechanism. Only GET /nodes and GET /nodes/1
will need to update Rack resource (cos right now rack -> nodes gives the baremetal ID, we would need to replace that with the tuskar-internal node id)

This is too fine grained: https://wiki.openstack.org/wiki/Blueprints - blueprints are for significant features (vs the individual steps in planning things where etherpad is great)

Blueprint information

Status:
Complete
Approver:
Martyn Taylor
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Matt Wagner
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Robert Collins

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:return-rack-in-node-resource,n,z

Addressed by: https://review.openstack.org/47435
    Expose Nodes as a top-level object

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.