I guess we're talking about JSON data types [1] in the api-ref. There is no "UUID" type in JSON. Which means, for "tenant_id" (and others) it has to be a JSON data type "string" which is a valid UUID. IOW, I think the api-ref uses the correct type.
References: [1] http://www.tutorialspoint.com/json/json_data_types.htm ** Changed in: nova Status: New => Invalid ** Changed in: nova Assignee: Gage Hugo (gagehugo) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1583701 Title: api-ref docs: use correct type for UUIDs Status in OpenStack Compute (nova): Invalid Bug description: Description =========== In http://developer.openstack.org/api-ref/compute/ there many cases where the Type is a string instead of a uuid. For example tenant_id: Name In Type Description tenant_id path string The UUID of the tenant in a multi-tenancy cloud. should be: Name In Type Description tenant_id path uuid The UUID of the tenant in a multi-tenancy cloud. Also: Name In Type Description servers body array List of server objects. id body string The UUID of the server. Name In Type Description servers body array List of server objects. id body uuid The UUID of the server. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1583701/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
