| Method | URI | Description |
|---|---|---|
| PUT | /v2/{tenant_id}/servers/{server_id}/metadata | Creates or replaces metadata for a specified server. |
Replaces items that match the specified keys. If you omit a key that already exists, the key retains its value.
If the number of metadata items exceeds the quota for metadata items, an overLimit (413) fault might be thrown.
Normal response codes: 200
Error response codes: computeFault (400, 500, …), serviceUnavailable (503), badRequest (400), unauthorized (401), forbidden (403), badMethod (405), overLimit (413), itemNotFound (404), badMediaType (415), buildInProgress (409)
This table shows the URI parameters for the create or replace server metadata request:
| Name | Type | Description |
|---|---|---|
| UUID | The tenant ID in a multi-tenancy cloud. |
| UUID | The UUID for the server. |
Example 2.51. Create or replace server metadata: JSON request
{
"metadata":{
"name":"test_server"
}
}Example 2.52. Create or replace server metadata: XML request
<?xml version='1.0' encoding='UTF-8'?>
<metadata xmlns="http://docs.openstack.org/compute/api/v1.1">
<meta key="type">staging_server</meta>
</metadata>
Example 2.53. Create or replace server metadata: JSON response
{
"metadata":{
"name":"test_server",
"server_type":"test"
}
}Example 2.54. Create or replace server metadata: XML response
<?xml version='1.0' encoding='UTF-8'?>
<metadata xmlns="http://docs.openstack.org/compute/api/v1.1">
<meta key="type">staging_server</meta>
</metadata>
