Method | URI | Description |
---|---|---|
POST | /v2/{tenant_id}/flavors/{flavor_id}/os-extra_specs | Creates extra-specs or keys for the specified flavor. |
Normal response codes: 200
This table shows the URI parameters for the create flavor extra specs request:
Name | Type | Description |
---|---|---|
| String | The ID for the tenant or account in a multi-tenancy cloud. |
| String | The ID of the flavor of interest to you. |
Example 3.71. Create flavor extra specs: JSON request
{ "extra_specs": { "key1": "value1", "key2": "value2" } }
Example 3.72. Create flavor extra specs: XML request
<?xml version="1.0" encoding="UTF-8" ?> <extra_specs> <key1>value1</key1> <key2>value2</key2> </extra_specs>
This operation does not require a request body.
Example 3.73. Create flavor extra specs: JSON response
{ "extra_specs": { "key1": "value1", "key2": "value2" } }
Example 3.74. Create flavor extra specs: XML response
<?xml version='1.0' encoding='UTF-8'?> <extra_specs> <key2>value2</key2> <key1>value1</key1> </extra_specs>
This operation does not return a response body.