[RFE] node name isn't supported in the REST API for creating a port

[Ruby Loo]

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.

[Sinval (sinvalneto01)]

Change submitted for review:
https://review.openstack.org/#/c/193439/

[Tan Lin (tan-lin-good)]

Hi Sinval, are you still working on this patch?

[Sinval (sinvalneto01)]

Hi Tan Lin, actually not, feel free to work on it.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Dmitry Tantsur (<email address hidden>) on branch: master
Review: https://review.openstack.org/193439
Reason: Hi! This patch hasn't been updated for more than a year, so I'm abandoning it.

[Ruby Loo (rloo)]

I changed this to be an rfe (or do folks think it isn't) since it affects the API. I'm good with this being rfe-approved w/o needing a spec.

[Jay Faulkner (jason-oldos)]

Approved per conversation in IRC with Lucas and Ruby. We all agree it's a useful thing.

To be clear: this is just an API shortcut, the port will still be associated with the UUID in the DB.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/405586

[Julia Kreger (juliaashleykreger)]

This is still valid. As of 20240202, only a node UUID is permitted.