[API] POST v1/nodes didn't return incorrect content

[Lin Yang]

According to api-ref, https://github.com/openstack/rsc/blob/master/api-ref/source/mockup/composed-node-create-response.json

when do post to v1/nodes to compose node, api should return following response.

{
  "uuid" : "eeeecccc-dddd-ffff-aaaa-uuuukkkk",
  "name" : "Test-node-1",
  "links" : [
    {
      "rel" : "self",
      "href" : "https://127.0.0.1/v1/nodes/eeeecccc-dddd-ffff-aaaa-uuuukkkk"
    },
    {
      "href" : "https://127.0.0.1/v1/nodes/eeeecccc-dddd-ffff-aaaa-uuuukkkk",
      "rel" : "bookmark"
    }
  ]
}

But current it only return "Location" in response header. For example,

{"node": "https://127.0.0.1:8442/redfish/v1/Nodes/2"}

[Ananth Narayan S (ananth-narayan)]

Lin,
Wondering if the API response needs to be this elaborate. I understand this API response is mimicking OpenStack APIs, but if there are fields that we could simplify, I suggest we could do that.
Thoughts?

[OpenStack Infra (hudson-openstack)]

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

[Lin Yang (lin-a-yang)]

Usually when user create a resource through api, I think it would be better to give back a brief info about the new resource. Otherwise user have to issue another GET request. Make sense?

Because the api spec is critical part for valence, I suggest all of us review the api-ref again before we go any further.

[chesterkuo (chester-kuo)]

the Response of data defined in the api-ref are common used in the OpenStack component , I will suggest we keep this format and extend if we have others needs.

Second , for the error response if any patch/get/post cmd file , suggest we can follow Openstack,

http://specs.openstack.org/openstack/api-wg/guidelines/errors.html

This is generic one and easy to understand, if we plan to add other Orchestation software plug-in this can be applied also.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Lin Yang (<email address hidden>) on branch: master
Review: https://review.openstack.org/398768
Reason: This has been fixed in another patch.