Open Stack

Hi API-SIG, neutron and tagging-related folks,

This email ask opinions on tagging when creating a resource.

We received a feature request to support tagging when creating a resource
[1].
Neutron supports bulk creation of resources but the current tagging API
recommended
by the API-SIG does not define tagging when creating a resource.
As a result, if we want to create 100 ports with specific tags,
we need 1 (bulk creation) +100 (taggins per resource) API calls.

It sounds nice to me to support tagging when creating a resource to address
the above problem.
What in my mind is to specify 'tags' attribute in a body of POST request
like:

 {'port':
    {'name': 'foo',
     'network_id': <network-id>,
     'tags': ['red', 'blue']
     }
  }

I don't know the reason why the current API-SIG recommended tagging API does
not support this model. The current tagging API defines "tags" as a
subresource.
Is there any reason this model was adopted?

Best Regards,
Akihiro Motoki (irc: amotoki)

[1] https://bugs.launchpad.net/neutron/+bug/1815933 [RFE] Allow
bulk-tagging of resources
[2] https://specs.openstack.org/openstack/api-wg/guidelines/tags.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190225/8fd5a32a/attachment.html>