Activity log for bug #1439901
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2015-04-03 00:06:30 | Ruby Loo | bug | added bug | ||
| 2015-06-18 00:09:26 | Sinval | ironic: assignee | Sinval (sinvalneto01) | ||
| 2015-06-19 06:10:26 | Sinval | ironic: status | Confirmed | In Progress | |
| 2015-06-23 02:57:55 | Tan Lin | bug | added subscriber Tan Lin | ||
| 2016-09-14 16:01:43 | Dmitry Tantsur | ironic: assignee | Sinval (sinvalneto01) | ||
| 2016-09-14 16:01:53 | Dmitry Tantsur | ironic: status | In Progress | Triaged | |
| 2016-09-14 16:02:02 | Dmitry Tantsur | tags | api | ||
| 2016-10-18 17:28:05 | Ruby Loo | summary | node name isn't supported in the REST API for creating a port | [RFE] node name isn't supported in the REST API for creating a port | |
| 2016-10-18 17:28:21 | Ruby Loo | tags | api | api rfe | |
| 2016-10-18 17:35:47 | Jay Faulkner | tags | api rfe | api rfe-approved | |
| 2016-10-18 17:43:08 | Ruby Loo | description | A port can be created via a POST /v1/ports, with 'node_uuid' and 'address' specified in the body. Now that we have logical node names, we should allow the port creation to accept the name of the node instead of the UUID of the node. Eg, add 'node' with either a UUID or name as its value, and deprecate 'node_uuid'. | A port can be created via a POST /v1/ports, with 'node_uuid' and 'address' specified in the body. Now that we have logical node names, we should allow the port creation to accept the name of the node instead of the UUID of the node. Eg, add 'node' with either a UUID or name as its value, and deprecate 'node_uuid'. Although a node name could be specified, the port would continue to be associated with a node UUID in the db; that won't change. | |
| 2016-10-18 19:45:03 | Ruby Loo | ironic: assignee | Anup (anup-d-navare) |
