Compute

Version:
2.96

This is a reference for the OpenStack Compute API which is provided by the Nova project. To learn more about the OpenStack Compute API concepts, please refer to the API guide.

version

This fetches all the information about all known major API versions in the deployment. Links to more specific information will be provided for each API version, as well as information about supported min and max microversions.

Normal Response Codes: 200

Responses

200

Ok

404

Error

Responses

200

Ok

404

Error

extensions

Lists all extensions to the API.

Normal response codes: 200

Error response codes: unauthorized(401)

Responses

200

Ok

Shows details for an extension, by alias.

Normal response codes: 200

Error response codes: unauthorized(401), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

extension

body

object

An extension object.

extension.alias

body

string

A short name by which this extension is also known.

extension.description

body

string

Text describing this extension’s purpose.

extension.name

body

string

Name of the extension.

extension.namespace

body

string

A URL pointing to the namespace for this extension.

extension.updated

body

string

The date and time when the resource was updated. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

404

Error

flavors

Show and manage server flavors.

Lists all flavors accessible to your project.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

400

Error

Creates a flavor.

Creating a flavor is typically only available to administrators of a cloud because this has implications for scheduling efficiently in the cloud.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), conflict(409)

Request

Responses

201

Ok

Name

Location

Type

Description

flavor

body

object

The ID and links for the flavor for your server instance. A flavor is a combination of memory, disk size, and CPUs.

flavor.name

body

string

The display name of a flavor.

flavor.id

body

string

The ID of the flavor. While people often make this look like an int, this is really a string.

flavor.ram

body

[‘integer’, ‘string’]

The amount of RAM a flavor has, in MiB.

flavor.vcpus

body

[‘integer’, ‘string’]

The number of virtual CPUs that will be allocated to the server.

flavor.disk

body

[‘integer’, ‘string’]

The size of the root disk that will be created in GiB. If 0 the root disk will be set to exactly the size of the image used to deploy the instance. However, in this case the scheduler cannot select the compute host based on the virtual image size. Therefore, 0 should only be used for volume booted instances or for testing purposes. Volume-backed instances can be enforced for flavors with zero root disk via the os_compute_api:servers:create:zero_disk_flavor policy rule.

flavor.OS-FLV-EXT-DATA:ephemeral

body

[‘integer’, ‘string’]

The size of the ephemeral disk that will be created, in GiB. Ephemeral disks may be written over on server state changes. So should only be used as a scratch space for applications that are aware of its limitations. Defaults to 0.

flavor.swap

body

[‘integer’, ‘string’]

The size of a dedicated swap disk that will be allocated, in MiB. If 0 (the default), no dedicated swap disk will be created. Currently, the empty string (‘’) is used to represent 0. As of microversion 2.75 default return value of swap is 0 instead of empty string.

flavor.rxtx_factor

body

[‘number’, ‘string’]

The receive / transmit factor (as a float) that will be set on ports if the network backend supports the QOS extension. Otherwise it will be ignored. It defaults to 1.0.

flavor.os-flavor-access:is_public

body

[‘boolean’, ‘string’]

Whether the flavor is public (available to all projects) or scoped to a set of projects. Default is True if not specified.

flavor.extra_specs

body

object

A dictionary of the flavor’s extra-specs key-and-value pairs. This will only be included if the user is allowed by policy to index flavor extra_specs.

New in version 2.61

400

Error

409

Error

Lists flavors with details.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

400

Error

Shows details for a flavor.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

flavor

body

object

The ID and links for the flavor for your server instance. A flavor is a combination of memory, disk size, and CPUs.

flavor.name

body

string

The display name of a flavor.

flavor.id

body

string

The ID of the flavor. While people often make this look like an int, this is really a string.

flavor.ram

body

[‘integer’, ‘string’]

The amount of RAM a flavor has, in MiB.

flavor.vcpus

body

[‘integer’, ‘string’]

The number of virtual CPUs that will be allocated to the server.

flavor.disk

body

[‘integer’, ‘string’]

The size of the root disk that will be created in GiB. If 0 the root disk will be set to exactly the size of the image used to deploy the instance. However, in this case the scheduler cannot select the compute host based on the virtual image size. Therefore, 0 should only be used for volume booted instances or for testing purposes. Volume-backed instances can be enforced for flavors with zero root disk via the os_compute_api:servers:create:zero_disk_flavor policy rule.

flavor.OS-FLV-EXT-DATA:ephemeral

body

[‘integer’, ‘string’]

The size of the ephemeral disk that will be created, in GiB. Ephemeral disks may be written over on server state changes. So should only be used as a scratch space for applications that are aware of its limitations. Defaults to 0.

flavor.swap

body

[‘integer’, ‘string’]

The size of a dedicated swap disk that will be allocated, in MiB. If 0 (the default), no dedicated swap disk will be created. Currently, the empty string (‘’) is used to represent 0. As of microversion 2.75 default return value of swap is 0 instead of empty string.

flavor.rxtx_factor

body

[‘number’, ‘string’]

The receive / transmit factor (as a float) that will be set on ports if the network backend supports the QOS extension. Otherwise it will be ignored. It defaults to 1.0.

flavor.os-flavor-access:is_public

body

[‘boolean’, ‘string’]

Whether the flavor is public (available to all projects) or scoped to a set of projects. Default is True if not specified.

flavor.extra_specs

body

object

A dictionary of the flavor’s extra-specs key-and-value pairs. This will only be included if the user is allowed by policy to index flavor extra_specs.

New in version 2.61

404

Error

Updates a flavor description.

This API is available starting with microversion 2.55.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

200

Ok

Name

Location

Type

Description

flavor

body

object

The ID and links for the flavor for your server instance. A flavor is a combination of memory, disk size, and CPUs.

flavor.name

body

string

The display name of a flavor.

flavor.id

body

string

The ID of the flavor. While people often make this look like an int, this is really a string.

flavor.ram

body

[‘integer’, ‘string’]

The amount of RAM a flavor has, in MiB.

flavor.vcpus

body

[‘integer’, ‘string’]

The number of virtual CPUs that will be allocated to the server.

flavor.disk

body

[‘integer’, ‘string’]

The size of the root disk that will be created in GiB. If 0 the root disk will be set to exactly the size of the image used to deploy the instance. However, in this case the scheduler cannot select the compute host based on the virtual image size. Therefore, 0 should only be used for volume booted instances or for testing purposes. Volume-backed instances can be enforced for flavors with zero root disk via the os_compute_api:servers:create:zero_disk_flavor policy rule.

flavor.OS-FLV-EXT-DATA:ephemeral

body

[‘integer’, ‘string’]

The size of the ephemeral disk that will be created, in GiB. Ephemeral disks may be written over on server state changes. So should only be used as a scratch space for applications that are aware of its limitations. Defaults to 0.

flavor.swap

body

[‘integer’, ‘string’]

The size of a dedicated swap disk that will be allocated, in MiB. If 0 (the default), no dedicated swap disk will be created. Currently, the empty string (‘’) is used to represent 0. As of microversion 2.75 default return value of swap is 0 instead of empty string.

flavor.rxtx_factor

body

[‘number’, ‘string’]

The receive / transmit factor (as a float) that will be set on ports if the network backend supports the QOS extension. Otherwise it will be ignored. It defaults to 1.0.

flavor.os-flavor-access:is_public

body

[‘boolean’, ‘string’]

Whether the flavor is public (available to all projects) or scoped to a set of projects. Default is True if not specified.

flavor.extra_specs

body

object

A dictionary of the flavor’s extra-specs key-and-value pairs. This will only be included if the user is allowed by policy to index flavor extra_specs.

New in version 2.61

404

Error

Deletes a flavor.

This is typically an admin only action. Deleting a flavor that is in use by existing servers is not recommended as it can cause incorrect data to be returned to the user under some operations.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

202

Ok

404

Error

Empty body for delete action

Request

Responses

201

Ok

202

Ok

400

Error

403

Error

404

Error

409

Error

Request

Responses

201

Ok

202

Ok

400

Error

403

Error

404

Error

409

Error

Request

Responses

201

Ok

202

Ok

400

Error

403

Error

404

Error

409

Error

Adds flavor access to a tenant and flavor.

Specify the addTenantAccess action and the tenant in the request body.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Ok

400

Error

403

Error

404

Error

409

Error

Removes flavor access from a tenant and flavor.

Specify the removeTenantAccess action and the tenant in the request body.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Ok

400

Error

403

Error

404

Error

409

Error

Lists all extra specs for a flavor, by ID.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

extra_specs

body

object

A dictionary of the flavor’s extra-specs key-and-value pairs. It appears in the os-extra-specs’ “create” REQUEST body, as well as the os-extra-specs’ “create” and “list” RESPONSE body.

404

Error

Creates extra specs for a flavor, by ID.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

Name

Location

Type

Description

extra_specs

body

object

A dictionary of the flavor’s extra-specs key-and-value pairs. It appears in the os-extra-specs’ “create” REQUEST body, as well as the os-extra-specs’ “create” and “list” RESPONSE body.

400

Error

404

Error

409

Error

Shows an extra spec, by key, for a flavor, by ID.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Example (JSON Request)

{'hw:numa_nodes': '1'}
404

Error

Updates an extra spec, by key, for a flavor, by ID.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403) itemNotFound(404), conflict(409)

Request

Responses

200

Ok

Example (JSON Request)

{'hw:numa_nodes': '1'}
400

Error

404

Error

409

Error

Deletes an extra spec, by key, for a flavor, by ID.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

204

Ok

404

Error

Lists flavor access information.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

images

List images.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

400

Error

List images with details.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

400

Error

Shows details for an image.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

Deletes an image.

Normal response codes: 204

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

204

Ok

403

Error

404

Error

List metadata of an image.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

403

Error

404

Error

Create an image metadata.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

201

Ok

400

Error

403

Error

404

Error

Update an image metadata

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

200

Ok

400

Error

403

Error

404

Error

Shows metadata item, by key, for an image.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

403

Error

404

Error

Creates or updates a metadata item, by key, for an image.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

200

Ok

400

Error

403

Error

404

Error

Deletes a metadata item, by key, for an image.

Normal response codes: 204

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

204

Ok

403

Error

404

Error

limits

Shows rate and absolute limits for the project.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Name

Location

Type

Description

absolute

body

object

Name/value pairs that set quota limits within a deployment and Name/value pairs of resource usage.

absolute.maxServerGroupMembers

body

integer

The number of allowed members for each server group.

absolute.maxServerGroups

body

integer

The number of allowed server groups for each tenant.

absolute.maxServerMetamaxServerMeta

body

integer

The number of allowed metadata items for each server.

absolute.maxTotalCores

body

integer

The number of allowed server cores for each tenant.

absolute.maxTotalInstances

body

integer

The number of allowed servers for each tenant.

absolute.maxTotalKeypairs

body

integer

The number of allowed key pairs for each user.

absolute.maxTotalRAMSize

body

integer

The amount of allowed server RAM, in MiB, for each tenant.

absolute.totalCoresUsed

body

integer

The number of used server cores in each tenant. If reserved query parameter is specified and it is not 0, the number of reserved server cores are also included.

absolute.totalInstancesUsed

body

integer

The number of servers in each tenant. If reserved query parameter is specified and it is not 0, the number of reserved servers are also included.

absolute.totalRAMUsed

body

integer

The amount of used server RAM in each tenant. If reserved query parameter is specified and it is not 0, the amount of reserved server RAM is also included.

absolute.totalServerGroupsUsed

body

integer

The number of used server groups in each tenant. If reserved query parameter is specified and it is not 0, the number of reserved server groups are also included.

os-agents

Lists agent builds.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), gone(410)

Responses

200

Ok

410

Error

Creates an agent build.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), conflict(409), gone(410)

Request

Responses

201

Ok

410

Error

Updates an agent build.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), gone(410)

Request

Responses

200

Ok

410

Error

Deletes an existing agent build.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), gone(410)

Responses

204

Ok

410

Error

os-aggregates

Lists all aggregates. Includes the ID, name, and availability zone for each aggregate.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Creates an aggregate. If specifying an option availability_zone, the aggregate is created as an availability zone and the availability zone is visible to normal users.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), conflict(409)

Request

Responses

201

Ok

Name

Location

Type

Description

aggregate

body

object

The host aggregate object.

aggregate.availability_zone

body

string

The availability zone of the host aggregate.

aggregate.created_at

body

string

The date and time when the resource was created. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.deleted

body

boolean

A boolean indicates whether this aggregate is deleted or not, if it has not been deleted, false will appear.

aggregate.deleted_at

body

[‘string’, ‘null’]

The date and time when the resource was deleted. If the resource has not been deleted yet, this field will be null, The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.id

body

integer

The ID of the host aggregate.

aggregate.metadata

body

object

Metadata key and value pairs associated with the aggregate.

aggregate.updated_at

body

[‘string’, ‘null’]

The date and time when the resource was updated, if the resource has not been updated, this field will show as null. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.uuid

body

string

The UUID of the host aggregate.

New in version 2.41
New in version 2.41

400

Error

409

Error

Shows details for an aggregate. Details include hosts and metadata.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

aggregate

body

object

The host aggregate object.

aggregate.availability_zone

body

string

The availability zone of the host aggregate.

aggregate.created_at

body

string

The date and time when the resource was created. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.deleted

body

boolean

A boolean indicates whether this aggregate is deleted or not, if it has not been deleted, false will appear.

aggregate.deleted_at

body

[‘string’, ‘null’]

The date and time when the resource was deleted. If the resource has not been deleted yet, this field will be null, The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.id

body

integer

The ID of the host aggregate.

aggregate.metadata

body

object

Metadata key and value pairs associated with the aggregate.

aggregate.updated_at

body

[‘string’, ‘null’]

The date and time when the resource was updated, if the resource has not been updated, this field will show as null. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.uuid

body

string

The UUID of the host aggregate.

New in version 2.41
New in version 2.41

400

Error

404

Error

Updates either or both the name and availability zone for an aggregate. If the aggregate to be updated has host that already in the given availability zone, the request will fail with 400 error.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

200

Ok

Name

Location

Type

Description

aggregate

body

object

The host aggregate object.

aggregate.availability_zone

body

string

The availability zone of the host aggregate.

aggregate.created_at

body

string

The date and time when the resource was created. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.deleted

body

boolean

A boolean indicates whether this aggregate is deleted or not, if it has not been deleted, false will appear.

aggregate.deleted_at

body

[‘string’, ‘null’]

The date and time when the resource was deleted. If the resource has not been deleted yet, this field will be null, The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.id

body

integer

The ID of the host aggregate.

aggregate.metadata

body

object

Metadata key and value pairs associated with the aggregate.

aggregate.updated_at

body

[‘string’, ‘null’]

The date and time when the resource was updated, if the resource has not been updated, this field will show as null. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.uuid

body

string

The UUID of the host aggregate.

New in version 2.41
New in version 2.41

400

Error

404

Error

409

Error

Deletes an aggregate.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Responses

204

Ok

400

Error

404

Error

Request

Responses

201

Ok

Name

Location

Type

Description

aggregate

body

object

The host aggregate object.

aggregate.availability_zone

body

string

The availability zone of the host aggregate.

aggregate.created_at

body

string

The date and time when the resource was created. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.deleted

body

boolean

A boolean indicates whether this aggregate is deleted or not, if it has not been deleted, false will appear.

aggregate.deleted_at

body

[‘string’, ‘null’]

The date and time when the resource was deleted. If the resource has not been deleted yet, this field will be null, The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.id

body

integer

The ID of the host aggregate.

aggregate.metadata

body

object

Metadata key and value pairs associated with the aggregate.

aggregate.updated_at

body

[‘string’, ‘null’]

The date and time when the resource was updated, if the resource has not been updated, this field will show as null. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.uuid

body

string

The UUID of the host aggregate.

New in version 2.41
New in version 2.41

400

Error

404

Error

409

Error

Request

Responses

201

Ok

Name

Location

Type

Description

aggregate

body

object

The host aggregate object.

aggregate.availability_zone

body

string

The availability zone of the host aggregate.

aggregate.created_at

body

string

The date and time when the resource was created. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.deleted

body

boolean

A boolean indicates whether this aggregate is deleted or not, if it has not been deleted, false will appear.

aggregate.deleted_at

body

[‘string’, ‘null’]

The date and time when the resource was deleted. If the resource has not been deleted yet, this field will be null, The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.id

body

integer

The ID of the host aggregate.

aggregate.metadata

body

object

Metadata key and value pairs associated with the aggregate.

aggregate.updated_at

body

[‘string’, ‘null’]

The date and time when the resource was updated, if the resource has not been updated, this field will show as null. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.uuid

body

string

The UUID of the host aggregate.

New in version 2.41
New in version 2.41

400

Error

404

Error

409

Error

Request

Responses

201

Ok

Name

Location

Type

Description

aggregate

body

object

The host aggregate object.

aggregate.availability_zone

body

string

The availability zone of the host aggregate.

aggregate.created_at

body

string

The date and time when the resource was created. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.deleted

body

boolean

A boolean indicates whether this aggregate is deleted or not, if it has not been deleted, false will appear.

aggregate.deleted_at

body

[‘string’, ‘null’]

The date and time when the resource was deleted. If the resource has not been deleted yet, this field will be null, The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.id

body

integer

The ID of the host aggregate.

aggregate.metadata

body

object

Metadata key and value pairs associated with the aggregate.

aggregate.updated_at

body

[‘string’, ‘null’]

The date and time when the resource was updated, if the resource has not been updated, this field will show as null. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

aggregate.uuid

body

string

The UUID of the host aggregate.

New in version 2.41
New in version 2.41

400

Error

404

Error

409

Error

Requests that a set of images be pre-cached on compute nodes within the referenced aggregate.

This API is available starting with microversion 2.81.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

202

Ok

400

Error

404

Error

os-assisted-volume-snapshots

Creates an assisted volume snapshot.

Normal response codes: 200

Error response codes: badRequest(400),unauthorized(401), forbidden(403)

Request

Responses

201

Ok

Name

Location

Type

Description

snapshot

body

object

A partial representation of a snapshot that is used to create a snapshot.

snapshot.id

body

string

Its the same arbitrary string which was sent in request body.

Note

This string is passed back to user as it is and not being used in Nova internally. So use snapshot_id instead for further operation on this snapshot.

snapshot.volumeId

body

string

The source volume ID.

400

Error

Deletes an assisted volume snapshot.

To make this request, add the delete_info query parameter to the URI, as follows:

DELETE /os-assisted-volume-snapshots/421752a6-acf6-4b2d-bc7a-119f9148cd8c?delete_info=’{“volume_id”: “521752a6-acf6-4b2d-bc7a-119f9148cd8c”}’

Normal response codes: 204

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Responses

204

Ok

400

Error

404

Error

os-availability-zone

Lists availability zone information.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Gets detailed availability zone information. Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

os-baremetal-nodes

Lists the bare metal nodes known by the compute environment.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), notImplemented(501)

Responses

200

Ok

404

Error

501

Error

Request of the os-baremetal-nodes:post operation

Request

Responses

201

Ok

400

Error

Shows details for a bare metal node.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), notImplemented(501)

Responses

200

Ok

404

Error

501

Error

Responses

204

Ok

400

Error

Empty body for add_interface action

Request

Responses

201

Ok

400

Error

Empty body for remove_interface action

Request

Responses

201

Ok

400

Error

os-cells

Lists cells.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), gone(410), notImplemented(501)

Responses

200

Ok

410

Error

Create a new cell.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), gone(410), notImplemented(501)

Request

Responses

201

Ok

410

Error

Retrieve capacities.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), gone(410), notImplemented(501)

Responses

200

Ok

410

Error

Lists cells with details of capabilities.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), gone(410), notImplemented(501)

Responses

200

Ok

410

Error

Retrieve info about the current cell.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), gone(410), notImplemented(501)

Responses

200

Ok

410

Error

Request of the os-cells/sync_instances:post operation

Request

Responses

201

Ok

410

Error

Shows data for a cell.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), gone(410), notImplemented(501)

Responses

200

Ok

410

Error

Update an existing cell.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), gone(410), notImplemented(501)

Request

Responses

200

Ok

410

Error

Remove a cell.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), gone(410), notImplemented(501)

Responses

204

Ok

410

Error

Shows capacities for a cell.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), gone(410), notImplemented(501)

Responses

200

Ok

410

Error

os-certificates

Creates a root certificate.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Request

Responses

201

Ok

410

Error

Return certificate information.

Responses

200

Ok

410

Error

os-cloudpipe

Lists cloudpipes.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound (404)

Responses

200

Ok

410

Error

Creates a cloudpipe.

Normal response codes: 200

Error response codes: badRequest(400),unauthorized(401), forbidden(403)

Request

Responses

201

Ok

410

Error

Configure cloudpipe parameters for the project.

Request

Responses

200

Ok

410

Error

server-consoles

Manage server consoles.

Given the console authentication token for a server, shows the related connection information.

Nova HyperV driver has been removed therefore requests for RDP console connection information will always return an http 400 error. Starting from microversion 2.31 it’s available for all other console types.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

console

body

object

The console object.

console.instance_uuid

body

string

The UUID of the server.

console.host

body

string

The name or ID of the host.

console.port

body

integer

The port number.

console.internal_access_path

body

string

The id representing the internal access path.

400

Error

401

Error

404

Error

The API provides a unified request for creating a remote console. The user can get a URL to connect the console from this API. The URL includes the token which is used to get permission to access the console. Servers may support different console protocols. To return a remote console using a specific protocol, such as VNC, set the protocol parameter to vnc.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), notImplemented(501)

Request

Responses

201

Ok

Name

Location

Type

Description

remote_console

body

object

The remote console object.

remote_console.protocol

body

string

The protocol of remote console. The valid values are vnc, spice, serial and mks. The protocol mks is added since Microversion 2.8.

remote_console.type

body

string

The type of remote console. The valid values are novnc, spice-html5, serial, and webmks. The type webmks is added since Microversion 2.8.

remote_console.url

body

string

The URL is used to connect the console.

400

Error

404

Error

409

Error

501

Error

os-fixed-ips

Shows details for a fixed IP address.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), gone(410)

Responses

200

Ok

410

Error

Empty body for reserve action

Request

Responses

201

Ok

410

Error

Empty body for unreserve action

Request

Responses

201

Ok

410

Error

os-floating-ip-dns

Lists registered DNS domains published by the DNS drivers.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), gone(410), notImplemented(501)

Responses

200

Ok

410

Error

Creates or updates a DNS domain.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), gone(410), notImplemented(501)

Request

Responses

200

Ok

410

Error

Deletes a DNS domain and all associated host entries.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), gone(410), notImplemented(501)

Responses

204

Ok

410

Error

Lists DNS entries for a domain and IP.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), gone(410), notImplemented(501)

Responses

200

Ok

410

Error

Creates or updates a DNS entry.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), gone(410), notImplemented(501)

Request

Responses

200

Ok

410

Error

Deletes a DNS entry.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), gone(410), notImplemented(501)

Responses

204

Ok

410

Error

os-floating-ip-pools

Lists floating IP pools.

Policy defaults enable only users with the administrative role or user who is authorized to operate on tenant <tenant_id> to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

os-floating-ips

Lists floating IP addresses associated with the tenant or account.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Creates, or allocates, a floating IP address for the current project. By default, the floating IP address is allocated from the public pool.

If more than one floating IP address pool is available, use the pool parameter to specify from which pool to allocate the IP address.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

201

Ok

400

Error

403

Error

404

Error

Shows details for a floating IP address, by ID, that is associated with the tenant or account.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

400

Error

404

Error

Deletes, or deallocates, a floating IP address from the current project and returns it to the pool from which it was allocated.

If the IP address is still associated with a running instance, it is automatically disassociated from that instance.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Responses

202

Ok

400

Error

403

Error

404

Error

409

Error

os-floating-ips-bulk

Lists all floating IPs.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), gone(410)

Responses

200

Ok

410

Error

Bulk-creates floating IPs.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), conflict(409), gone(410)

Request

Responses

201

Ok

410

Error

Lists all floating IPs for a host.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), gone(410)

Responses

200

Ok

410

Error

Request of the os-floating-ips-bulk/id:put operation

Request

Responses

200

Ok

410

Error

os-fping

Runs the fping utility to ping instances and reports which instances are alive.

Specify the all_tenants=1 query parameter to ping instances for all tenants. For example:

Specify the include and exclude query parameters to filter the results. For example:

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: serviceUnavailable(503), unauthorized(401), forbidden(403), itemNotFound(404), gone(410)

Responses

200

Ok

410

Error

Runs the fping utility to ping an instance and reports whether the instance is alive.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: serviceUnavailable(503), unauthorized(401), forbidden(403), itemNotFound(404), gone(410)

Responses

200

Ok

410

Error

os-hosts

Lists hosts.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Shows details for a host.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

Enables, disables a host or put a host in maintenance or normal mode.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), NotImplemented(501)

Request

Responses

200

Ok

400

Error

404

Error

501

Error

Reboots a host.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), NotImplemented(501)

Responses

200

Ok

400

Error

404

Error

501

Error

Shuts down a host.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), NotImplemented(501)

Responses

200

Ok

400

Error

404

Error

501

Error

Starts a host.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), NotImplemented(501)

Responses

200

Ok

400

Error

404

Error

501

Error

os-hypervisors

Lists hypervisors.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

400

Error

404

Error

Lists hypervisors details.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

400

Error

404

Error

Shows summary statistics for all enabled hypervisors over all compute nodes.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Shows details for a given hypervisor.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

hypervisor

body

object

The hypervisor object.

hypervisor.cpu_info

body

object

A dictionary that contains cpu information like arch, model, vendor, features and topology. The content of this field is hypervisor specific.

Note

Since version 2.28 cpu_info field is returned as a dictionary instead of string.

Available until version 2.87
Available until version 2.87

hypervisor.current_workload

body

integer

The current_workload is the number of tasks the hypervisor is responsible for. This will be equal or greater than the number of active VMs on the system (it can be greater when VMs are being deleted and the hypervisor is still cleaning up).

Available until version 2.87
Available until version 2.87

hypervisor.disk_available_least

body

integer

The actual free disk on this hypervisor(in GiB). If allocation ratios used for overcommit are configured, this may be negative. This is intentional as it provides insight into the amount by which the disk is overcommitted.

Available until version 2.87
Available until version 2.87

hypervisor.host_ip

body

string

The IP address of the hypervisor’s host.

hypervisor.free_disk_gb

body

integer

The free disk remaining on this hypervisor(in GiB). This does not take allocation ratios used for overcommit into account so this value may be negative.

Available until version 2.87
Available until version 2.87

hypervisor.free_ram_mb

body

integer

The free RAM in this hypervisor(in MiB). This does not take allocation ratios used for overcommit into account so this value may be negative.

Available until version 2.87
Available until version 2.87

hypervisor.hypervisor_hostname

body

string

The hypervisor host name provided by the Nova virt driver. For the Ironic driver, it is the Ironic node uuid.

hypervisor.hypervisor_type

body

string

The hypervisor type.

hypervisor.hypervisor_version

body

integer

The hypervisor version.

hypervisor.local_gb

body

integer

The disk in this hypervisor (in GiB). This does not take allocation ratios used for overcommit into account so there may be disparity between this and the used count.

Available until version 2.87
Available until version 2.87

hypervisor.local_gb_used

body

integer

The disk used in this hypervisor (in GiB).

Available until version 2.87
Available until version 2.87

hypervisor.memory_mb

body

integer

The memory of this hypervisor (in MiB). This does not take allocation ratios used for overcommit into account so there may be disparity between this and the used count.

Available until version 2.87
Available until version 2.87

hypervisor.memory_mb_used

body

integer

The memory used in this hypervisor (in MiB).

Available until version 2.87
Available until version 2.87

hypervisor.running_vms

body

integer

The number of running VMs on this hypervisor.

Available until version 2.87
Available until version 2.87

hypervisor.service

body

object

The hypervisor service object.

hypervisor.service.host

body

string

The name of the host.

hypervisor.service.id

body

[‘integer’, ‘string’]

The id of the service as a uuid.

New in version 2.53

hypervisor.service.disabled_reason

body

[‘string’, ‘null’]

The disable reason of the service, null if the service is enabled or disabled without reason provided.

hypervisor.uptime

body

string

The total uptime of the hypervisor and information about average load. Only reported for active hosts where the virt driver supports this feature.

New in version 2.88
New in version 2.87

hypervisor.vcpus

body

integer

The number of vCPU in this hypervisor. This does not take allocation ratios used for overcommit into account so there may be disparity between this and the used count.

Available until version 2.87
Available until version 2.87

hypervisor.vcpus_used

body

integer

The number of vCPU used in this hypervisor.

Available until version 2.87
Available until version 2.87

hypervisor.id

body

string

The id of the hypervisor. From version 2.53 it is a string as UUID

hypervisor.state

body

string

The state of the hypervisor. One of up or down.

hypervisor.status

body

string

The status of the hypervisor. One of enabled or disabled.

400

Error

404

Error

Search hypervisor by a given hypervisor host name or portion of it.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response code: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

List all servers belong to each hypervisor whose host name is matching a given hypervisor host name or portion of it.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response code: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

Shows the uptime for a given hypervisor.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), NotImplemented(501)

Responses

200

Ok

400

Error

404

Error

501

Error

os-instance_usage_audit_log

Lists usage audits for all servers on all compute hosts where usage auditing is configured.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Name

Location

Type

Description

log

body

object

The object of instance usage audit logs.

errors

body

integer

The number of errors.

instances

body

integer

The number of instances.

message

body

string

The log message of the instance usage audit task.

state

body

string

The state of the instance usage audit task. DONE or RUNNING.

num_hosts

body

integer

The number of the hosts.

num_hosts_done

body

integer

The number of the hosts whose instance audit tasks have been done.

num_hosts_not_run

body

integer

The number of the hosts whose instance audit tasks have not run.

num_hosts_running

body

integer

The number of the hosts whose instance audit tasks are running.

overall_status

body

string

The overall status of instance audit tasks.

M of N hosts done. K errors.

The M value is the number of hosts whose instance audit tasks have been done in the period. The N value is the number of all hosts. The K value is the number of hosts whose instance audit tasks cause errors. If instance audit tasks have been done at all hosts in the period, the overall status is as follows:

ALL hosts done. K errors.

period_beginning

body

string

The beginning time of the instance usage audit period. For example, 2016-05-01 00:00:00.

period_ending

body

string

The ending time of the instance usage audit period. For example, 2016-06-01 00:00:00.

total_errors

body

integer

The total number of instance audit task errors.

total_instances

body

integer

The total number of VM instances in the period.

Lists usage audits that occurred before a specified time.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

Name

Location

Type

Description

log

body

object

The object of instance usage audit logs.

errors

body

integer

The number of errors.

instances

body

integer

The number of instances.

message

body

string

The log message of the instance usage audit task.

state

body

string

The state of the instance usage audit task. DONE or RUNNING.

num_hosts

body

integer

The number of the hosts.

num_hosts_done

body

integer

The number of the hosts whose instance audit tasks have been done.

num_hosts_not_run

body

integer

The number of the hosts whose instance audit tasks have not run.

num_hosts_running

body

integer

The number of the hosts whose instance audit tasks are running.

overall_status

body

string

The overall status of instance audit tasks.

M of N hosts done. K errors.

The M value is the number of hosts whose instance audit tasks have been done in the period. The N value is the number of all hosts. The K value is the number of hosts whose instance audit tasks cause errors. If instance audit tasks have been done at all hosts in the period, the overall status is as follows:

ALL hosts done. K errors.

period_beginning

body

string

The beginning time of the instance usage audit period. For example, 2016-05-01 00:00:00.

period_ending

body

string

The ending time of the instance usage audit period. For example, 2016-06-01 00:00:00.

total_errors

body

integer

The total number of instance audit task errors.

total_instances

body

integer

The total number of VM instances in the period.

400

Error

os-keypairs

Lists keypairs that are associated with the account.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

400

Error

Imports (or generates) a keypair.

Normal response codes: 200, 201

Error response codes: badRequest(400), unauthorized(401), forbidden(403), conflict(409)

Request

Responses

201

Ok

Name

Location

Type

Description

keypair

body

object

Keypair object

keypair.user_id

body

string

The user_id for a keypair.

keypair.deleted

body

boolean

A boolean indicates whether this keypair is deleted or not. The value is always false (not deleted).

keypair.created_at

body

string

The date and time when the resource was created.

keypair.deleted_at

body

[‘string’, ‘null’]

It is always null.

keypair.updated_at

body

[‘string’, ‘null’]

It is always null.

keypair.id

body

integer

The keypair ID.

keypair.name

body

string

The name for the keypair.

keypair.public_key

body

string

The keypair public key.

keypair.fingerprint

body

string

The fingerprint for the keypair.

keypair.type

body

string

The type of the keypair. Allowed values are ssh or x509.

New in version 2.2
New in version 2.2

keypair.private_key

body

string

If you do not provide a public key on create, a new keypair will be built for you, and the private key will be returned during the initial create call. Make sure to save this, as there is no way to get this private key again in the future.

Available until version 2.91
Available until version 2.91

400

Error

403

Error

409

Error

Shows details for a keypair that is associated with the account.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

keypair

body

object

Keypair object

keypair.user_id

body

string

The user_id for a keypair.

keypair.deleted

body

boolean

A boolean indicates whether this keypair is deleted or not. The value is always false (not deleted).

keypair.created_at

body

string

The date and time when the resource was created. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

keypair.deleted_at

body

[‘string’, ‘null’]

It is always null.

keypair.updated_at

body

[‘string’, ‘null’]

It is always null.

keypair.id

body

integer

The keypair ID.

keypair.name

body

string

The name for the keypair.

keypair.public_key

body

string

The keypair public key.

keypair.fingerprint

body

string

The fingerprint for the keypair.

keypair.type

body

string

The type of the keypair. Allowed values are ssh or x509.

New in version 2.2
New in version 2.2

404

Error

Deletes a keypair.

Normal response codes: 202, 204

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

202

Ok

204

Ok

404

Error

os-migrations

Lists migrations.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Starting from microversion 2.59, the response is sorted by created_at and id in descending order.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

400

Error

os-networks

Lists networks for the project.

Policy defaults enable all users to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Creates a network.

Policy defaults enable only users with the administrative role or the owner of the network to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), conflict(409), gone(410), notImplemented(501)

Request

Responses

201

Ok

410

Error

Adds a network to a project.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), gone(410), notImplemented(501)

Request

Responses

201

Ok

410

Error

Shows details for a network.

Policy defaults enable all users to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

Deletes a network.

Policy defaults enable only users with the administrative role or the owner of the network to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), gone(410)

Responses

204

Ok

410

Error

Empty body for disassociate action

Request

Responses

201

Ok

410

Error

Empty body for disassociate_host action

Request

Responses

201

Ok

410

Error

Empty body for disassociate_project action

Request

Responses

201

Ok

410

Error

Empty body for associate_host action

Request

Responses

201

Ok

410

Error

quota-class-sets-os-quota-class-sets

Show, Create or Update the quotas for a Quota Class. Nova supports implicit ‘default’ Quota Class only.

Show the quota for the Quota Class.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Name

Location

Type

Description

quota_class_set

body

object

A quota_class_set object.

quota_class_set.id

body

string

The ID of the quota class. Nova supports the default Quota Class only.

quota_class_set.instances

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.cores

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.ram

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.floating_ips

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.fixed_ips

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.metadata_items

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.key_pairs

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.security_groups

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.security_group_rules

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.injected_files

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.injected_file_content_bytes

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.injected_file_path_bytes

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.server_groups

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.server_group_members

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_class_set.networks

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

Update the quotas for the Quota Class.

If the requested Quota Class is not found in the DB, then the API will create the one. Only ‘default’ quota class is valid and used to set the default quotas, all other quota class would not be used anywhere.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Request

Responses

200

Ok

400

Error

quota-sets-os-quota-sets

Permits administrators, depending on policy settings, to view default quotas, view details for quotas, revert quotas to defaults, and update the quotas for a project or a project and user.

Show the quota for a project or a project and a user.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

Name

Location

Type

Description

quota_set

body

object

A quota_set object.

quota_set.id

body

string

The UUID of the tenant/user the quotas listed for.

quota_set.instances

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.cores

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.ram

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.floating_ips

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.fixed_ips

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.metadata_items

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.key_pairs

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.security_groups

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.security_group_rules

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.injected_files

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.injected_file_content_bytes

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.injected_file_path_bytes

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.server_groups

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.server_group_members

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.networks

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

400

Error

Update the quotas for a project or a project and a user.

Users can force the update even if the quota has already been used and the reserved quota exceeds the new quota. To force the update, specify the "force": True attribute in the request body, the default value is false.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Request

Responses

200

Ok

Name

Location

Type

Description

quota_set

body

object

A quota_set object.

quota_set.id

body

string

The UUID of the tenant/user the quotas listed for.

quota_set.instances

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.cores

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.ram

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.floating_ips

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.fixed_ips

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.metadata_items

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.key_pairs

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.security_groups

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.security_group_rules

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.injected_files

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.injected_file_content_bytes

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.injected_file_path_bytes

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.server_groups

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.server_group_members

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.networks

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

400

Error

Reverts the quotas to default values for a project or a project and a user.

To revert quotas for a project and a user, specify the user_id query parameter.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403)

Responses

202

Ok

Show the detail of quota for a project or a project and a user.

To show a quota for a project and a user, specify the user_id query parameter.

Normal response codes: 200

Error response codes: badrequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

Name

Location

Type

Description

quota_set

body

object

A quota_set object.

quota_set.id

body

string

The UUID of the tenant/user the quotas listed for.

quota_set.instances

body

object

The object of detailed servers quota, including in_use, limit and reserved number of instances.

quota_set.instances.in_use

body

integer

quota_set.instances.limit

body

integer

quota_set.instances.reserved

body

integer

quota_set.cores

body

object

The object of detailed cores quota, including in_use, limit and reserved number of cores.

quota_set.cores.in_use

body

integer

quota_set.cores.limit

body

integer

quota_set.cores.reserved

body

integer

quota_set.ram

body

object

The object of detailed key ram quota, including in_use, limit and reserved number of ram.

quota_set.ram.in_use

body

integer

quota_set.ram.limit

body

integer

quota_set.ram.reserved

body

integer

quota_set.floating_ips

body

object

The object of detailed floating ips quota, including in_use, limit and reserved number of floating ips.

Available until version 2.35
Available until version 2.35

quota_set.floating_ips.in_use

body

integer

quota_set.floating_ips.limit

body

integer

quota_set.floating_ips.reserved

body

integer

quota_set.fixed_ips

body

object

The object of detailed fixed ips quota, including in_use, limit and reserved number of fixed ips.

Available until version 2.35
Available until version 2.35

quota_set.fixed_ips.in_use

body

integer

quota_set.fixed_ips.limit

body

integer

quota_set.fixed_ips.reserved

body

integer

quota_set.metadata_items

body

object

The object of detailed key metadata items quota, including in_use, limit and reserved number of metadata items.

quota_set.metadata_items.in_use

body

integer

quota_set.metadata_items.limit

body

integer

quota_set.metadata_items.reserved

body

integer

quota_set.key_pairs

body

object

The object of detailed key pairs quota, including in_use, limit and reserved number of key pairs.

Note

in_use field value for keypair quota details is always zero. In Nova, key_pairs are a user-level resource, not a project- level resource, so for legacy reasons, the keypair in-use information is not counted.

quota_set.key_pairs.in_use

body

integer

quota_set.key_pairs.limit

body

integer

quota_set.key_pairs.reserved

body

integer

quota_set.security_groups

body

object

The object of detailed security groups, including in_use, limit and reserved number of security groups.

Available until version 2.35
Available until version 2.35

quota_set.security_groups.in_use

body

integer

quota_set.security_groups.limit

body

integer

quota_set.security_groups.reserved

body

integer

quota_set.security_group_rules

body

object

The object of detailed security group rules quota, including in_use, limit and reserved number of security group rules.

Available until version 2.35
Available until version 2.35

quota_set.security_group_rules.in_use

body

integer

quota_set.security_group_rules.limit

body

integer

quota_set.security_group_rules.reserved

body

integer

quota_set.injected_files

body

object

The object of detailed injected files quota, including in_use, limit and reserved number of injected files.

Available until version 2.56
Available until version 2.56

quota_set.injected_files.in_use

body

integer

quota_set.injected_files.limit

body

integer

quota_set.injected_files.reserved

body

integer

quota_set.injected_files_content_bytes

body

object

The object of detailed injected file content bytes quota, including in_use, limit and reserved number of injected file content bytes.
Available until version 2.56

quota_set.injected_files_content_bytes.in_use

body

integer

quota_set.injected_files_content_bytes.limit

body

integer

quota_set.injected_files_content_bytes.reserved

body

integer

quota_set.injected_files_path_bytes

body

object

The object of detailed injected file path bytes quota, including in_use, limit and reserved number of injected file path bytes.
Available until version 2.56

quota_set.injected_files_path_bytes.in_use

body

integer

quota_set.injected_files_path_bytes.limit

body

integer

quota_set.injected_files_path_bytes.reserved

body

integer

quota_set.server_groups

body

object

The object of detailed server groups, including in_use, limit and reserved number of server groups.

quota_set.server_groups.in_use

body

integer

quota_set.server_groups.limit

body

integer

quota_set.server_groups.reserved

body

integer

quota_set.server_group_members

body

object

The object of detailed server group members, including in_use, limit and reserved number of server group members.

quota_set.server_group_members.in_use

body

integer

quota_set.server_group_members.limit

body

integer

quota_set.server_group_members.reserved

body

integer

quota_set.networks

body

object

The number of private networks that can be created per project.

Available until version 2.35
Available until version 2.35

quota_set.networks.in_use

body

integer

quota_set.networks.limit

body

integer

quota_set.networks.reserved

body

integer

400

Error

Lists the default quotas for a project.

Normal response codes: 200

Error response codes: badrequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

Name

Location

Type

Description

quota_set

body

object

A quota_set object.

quota_set.id

body

string

The UUID of the tenant/user the quotas listed for.

quota_set.instances

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.cores

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.ram

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.floating_ips

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.fixed_ips

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.metadata_items

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.key_pairs

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.security_groups

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.security_group_rules

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.injected_files

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.injected_file_content_bytes

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.injected_file_path_bytes

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.server_groups

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.server_group_members

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

quota_set.networks

body

[‘integer’, ‘string’]

The number of allowed injected files for the quota class.

Available until version 2.56

400

Error

os-security-group-default-rules

Lists default security group rules.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), gone(410), notImplemented(501)

Responses

200

Ok

410

Error

Creates a default security group rule.

If you specify a source port ( from_port ) or destination port ( to_port ) value, you must specify an IP protocol ( ip_protocol ) value. Otherwise, the operation returns the Bad Request (400) response code.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), conflict(409), gone(410), notImplemented(501)

Request

Responses

201

Ok

410

Error

Shows details for a security group rule.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), gone(410), notImplemented(501)

Responses

200

Ok

410

Error

Deletes a security group rule.

Normal response codes: 204

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), gone(410), notImplemented(501)

Responses

204

Ok

410

Error

os-security-group-rules

Creates a rule for a security group. Either cidr or group_id must be specified when creating a rule.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Request

Responses

201

Ok

400

Error

403

Error

404

Error

Deletes a security group rule.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Responses

202

Ok

400

Error

404

Error

409

Error

os-security-groups

Lists security groups.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

Creates a security group.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Request

Responses

201

Ok

400

Error

403

Error

Shows details for a security group.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

400

Error

404

Error

Updates a security group.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

200

Ok

400

Error

404

Error

Deletes a security group.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Responses

202

Ok

400

Error

404

Error

os-server-external-events

Creates one or more external events, which the API dispatches to the host a server is assigned to. If the server is not currently assigned to a host the event will not be delivered.

You will receive back the list of events that you submitted, with an updated code and status indicating their level of success.

Normal response codes: 200, 207

A 200 will be returned if all events succeeded, 207 will be returned if any events could not be processed. The code attribute for the event will explain further what went wrong.

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Request

Responses

200

Ok

403

Error

os-server-groups

Lists all server groups for the tenant.

Administrative users can use the all_projects query parameter to list all server groups for all projects.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Creates a server group.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), conflict(409)

Request

Responses

201

Ok

Name

Location

Type

Description

server_group

body

object

The server group object.

server_group.id

body

string

The UUID of the server group.

server_group.metadata

body

object

Metadata key and value pairs. The maximum size for each metadata key and value pair is 255 bytes. It’s always empty and only used for keeping compatibility.

Available until version 2.63
Available until version 2.63

server_group.name

body

string

The name of the server group.

server_group.policy

body

string

The policy field represents the name of the policy. The current valid policy names are:

  • anti-affinity - servers in this group must be scheduled to different hosts.

  • affinity - servers in this group must be scheduled to the same host.

  • soft-anti-affinity - servers in this group should be scheduled to different hosts if possible, but if not possible then they should still be scheduled instead of resulting in a build failure.

  • soft-affinity - servers in this group should be scheduled to the same host if possible, but if not possible then they should still be scheduled instead of resulting in a build failure.

New in version 2.64
New in version 2.64

server_group.project_id

body

string

The project ID who owns the server group.

New in version 2.13
New in version 2.13

server_group.rules

body

object

The rules field, which is a dict, can be applied to the policy. Currently, only the max_server_per_host rule is supported for the anti-affinity policy. The max_server_per_host rule allows specifying how many members of the anti-affinity group can reside on the same compute host. If not specified, only one member from the same anti-affinity group can reside on a given host.

New in version 2.64
New in version 2.64

server_group.rules.max_server_per_host

body

[‘integer’, ‘string’]

server_group.user_id

body

string

The user ID who owns the server group.

New in version 2.13
New in version 2.13

400

Error

403

Error

409

Error

Shows details for a server group.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

server_group

body

object

The server group object.

server_group.id

body

string

The UUID of the server group.

server_group.metadata

body

object

Metadata key and value pairs. The maximum size for each metadata key and value pair is 255 bytes. It’s always empty and only used for keeping compatibility.

Available until version 2.63
Available until version 2.63

server_group.name

body

string

The name of the server group.

server_group.policy

body

string

The policy field represents the name of the policy. The current valid policy names are:

  • anti-affinity - servers in this group must be scheduled to different hosts.

  • affinity - servers in this group must be scheduled to the same host.

  • soft-anti-affinity - servers in this group should be scheduled to different hosts if possible, but if not possible then they should still be scheduled instead of resulting in a build failure.

  • soft-affinity - servers in this group should be scheduled to the same host if possible, but if not possible then they should still be scheduled instead of resulting in a build failure.

New in version 2.64
New in version 2.64

server_group.project_id

body

string

The project ID who owns the server group.

New in version 2.13
New in version 2.13

server_group.rules

body

object

The rules field, which is a dict, can be applied to the policy. Currently, only the max_server_per_host rule is supported for the anti-affinity policy. The max_server_per_host rule allows specifying how many members of the anti-affinity group can reside on the same compute host. If not specified, only one member from the same anti-affinity group can reside on a given host.

New in version 2.64
New in version 2.64

server_group.rules.max_server_per_host

body

[‘integer’, ‘string’]

server_group.user_id

body

string

The user ID who owns the server group.

New in version 2.13
New in version 2.13

404

Error

Deletes a server group.

Normal response codes: 204

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

204

Ok

404

Error

os-services

Lists all running Compute services.

Provides details why any services were disabled.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Update a compute service to enable or disable scheduling, including recording a reason why a compute service was disabled from scheduling. Set or unset the forced_down flag for the service. This operation is only allowed on services whose binary is nova-compute.

This API is available starting with microversion 2.53.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

200

Ok

Name

Location

Type

Description

service

body

object

Object representing a compute service.

service.zone

body

string

The availability zone name.

service.binary

body

string

The binary name of the service.

service.disabled_reason

body

string

The reason for disabling a service.

service.host

body

string

The name of the host.

service.id

body

[‘integer’, ‘string’]

The id of the service as a uuid.

service.forced_down

body

boolean

Whether or not this service was forced down manually by an administrator after the service was fenced. This value is useful to know that some 3rd party has verified the service should be marked down.
New in version 2.11

service.name

body

string

Service name

service.state

body

string

The state of the service. One of up or down.

service.status

body

string

The status of the service. One of enabled or disabled.

service.updated_at

body

string

The date and time when the resource was updated. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

400

Error

404

Error

Deletes a service. If it’s a nova-compute service, then the corresponding host will be removed from all the host aggregates as well.

Attempts to delete a nova-compute service which is still hosting instances will result in a 409 HTTPConflict response. The instances will need to be migrated or deleted before a compute service can be deleted.

Similarly, attempts to delete a nova-compute service which is involved in in-progress migrations will result in a 409 HTTPConflict response. The migrations will need to be completed, for example confirming or reverting a resize, or the instances will need to be deleted before the compute service can be deleted.

Normal response codes: 204

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Responses

204

Ok

400

Error

404

Error

409

Error

os-simple-tenant-usage

Lists usage statistics for all tenants.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

400

Error

Shows usage statistics for a tenant.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

400

Error

os-snapshots

Lists snapshots.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Creates a new snapshot.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Request

Responses

201

Ok

400

Error

403

Error

Lists all snapshots with details.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Shows details for a given snapshot.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

Deletes a snapshot from the account.

This operation is asynchronous. You must list snapshots repeatedly to determine whether the snapshot was deleted.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

202

Ok

404

Error

os-tenant-networks

Lists all project networks.

Policy defaults enable only users with the administrative role or the owner of the network to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Creates a project network.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), conflict(409), gone(410), serviceUnavailable(503)

Example Create Project Network: JSON request

Request

Responses

201

Ok

410

Error

Shows details for a project network.

Policy defaults enable only users with the administrative role or the owner of the network to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

Deletes a project network.

Policy defaults enable only users with the administrative role or the owner of the network to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), gone(410)

Responses

204

Ok

410

Error

os-volumes

Lists the volumes associated with the account.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Creates a new volume.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

201

Ok

400

Error

403

Error

404

Error

Lists all volumes with details.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403)

Responses

200

Ok

Shows details for a given volume.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

Deletes a volume.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

202

Ok

400

Error

404

Error

os-volumes_boot

Returns a list of server names and ids for a given user.

Responses

200

Ok

400

Error

403

Error

Creates a new server for a given user.

Request

Responses

202

Ok

400

Error

403

Error

409

Error

Returns a list of server details for a given user.

Responses

200

Ok

400

Error

403

Error

Returns server details by server id.

Responses

200

Ok

404

Error

Update server then pass on to version-specific controller.

Request

Responses

200

Ok

404

Error

Destroys a server.

Responses

204

Ok

404

Error

409

Error

Empty body for confirmResize action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for revertResize action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for os-start action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for os-stop action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for resetNetwork action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for injectNetworkInfo action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for restore action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for forceDelete action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for unlock action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for pause action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for unpause action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for os-getRDPConsole action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for unrescue action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for addSecurityGroup action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for removeSecurityGroup action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for shelve action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for shelveOffload action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for suspend action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Empty body for resume action

Request

Responses

201

Ok

202

Ok

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

servers

Lists IDs, names, and links for servers.

By default the servers are filtered using the project ID associated with the authenticated request.

Servers contain a status attribute that indicates the current server state. You can filter on the server status when you complete a list servers request. The server status is returned in the response body. The possible server status values are:

There is whitelist for valid filter keys. Any filter key other than from whitelist will be silently ignored.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

400

Error

403

Error

Creates a server.

The progress of this operation depends on the location of the requested image, network I/O, host load, selected flavor, and other factors.

To check the progress of the request, make a GET /servers/{id} request. This call returns a progress attribute, which is a percentage value from 0 to 100.

The Location header returns the full URL to the newly created server and is available as a self and bookmark link in the server representation.

When you create a server, the response shows only the server ID, its links, and the admin password. You can get additional attributes through subsequent GET requests on the server.

Include the block_device_mapping_v2 parameter in the create request body to boot a server from a volume.

Include the key_name parameter in the create request body to add a keypair to the server when you create it. To create a keypair, make a create keypair request.

Preconditions

Asynchronous postconditions

Troubleshooting

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

202

Ok

400

Error

403

Error

409

Error

For each server, shows server details including config drive, extended status, and server usage information.

The extended status information appears in the OS-EXT-STS:vm_state, OS-EXT-STS:power_state, and OS-EXT-STS:task_state attributes.

The server usage information appears in the OS-SRV-USG:launched_at and OS-SRV-USG:terminated_at attributes.

HostId is unique per account and is not globally unique.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403)

Responses

200

Ok

400

Error

403

Error

Shows details for a server.

Includes server details including configuration drive, extended status, and server usage information.

The extended status information appears in the OS-EXT-STS:vm_state, OS-EXT-STS:power_state, and OS-EXT-STS:task_state attributes.

The server usage information appears in the OS-SRV-USG:launched_at and OS-SRV-USG:terminated_at attributes.

HostId is unique per account and is not globally unique.

Preconditions

The server must exist.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

server

body

object

A server object.

server.accessIPv4

body

string

IPv4 address that should be used to access this server. May be automatically set by the provider.

server.accessIPv6

body

string

IPv6 address that should be used to access this server. May be automatically set by the provider.

server.addresses

body

object

The addresses for the server. Servers with status BUILD hide their addresses information.

server.OS-EXT-AZ:availability_zone

body

string

The availability zone name.

New in version 2.75

server.OS-EXT-SRV-ATTR:host

body

string

The name of the compute host on which this instance is running. Appears in the response for administrative users only.

New in version 2.75

server.config_drive

body

string

Indicates whether or not a config drive was used for this server. The value is True or an empty string. An empty string stands for False.

New in version 2.75

server.created

body

string

The date and time when the resource was created. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

server.description

body

string

The description of the server. Before microversion 2.19 this was set to the server name.

New in version 2.19

server.OS-DCF:diskConfig

body

string

Disk configuration. The value is either:

  • AUTO. The API builds the server with a single partition the size of the target flavor disk. The API automatically adjusts the file system to fit the entire partition.

  • MANUAL. The API builds the server by using the partition scheme and file system that is in the source image. If the target flavor disk is larger, The API does not partition the remaining disk space.

server.fault

body

object

A fault object. Only displayed when the server status is ERROR or DELETED and a fault occurred.

server.fault.code

body

integer

The error response code.

server.fault.created

body

string

The date and time when the exception was raised. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

server.fault.message

body

string

The error message.

server.fault.details

body

string

The stack trace. It is available if the response code is not 500 or you have the administrator privilege

server.flavor

body

object

Before microversion 2.47 this contains the ID and links for the flavor used to boot the server instance. This can be an empty object in case flavor information is no longer present in the system.

As of microversion 2.47 this contains a subset of the actual flavor information used to create the server instance, represented as a nested dictionary.

server.flavor.id

body

string

The UUID of the server.
Available until version 2.46

server.flavor.vcpus

body

integer

The number of virtual CPUs that were allocated to the server.

New in version 2.47
New in version 2.47

server.flavor.ram

body

integer

The amount of RAM a flavor has, in MiB.

New in version 2.47
New in version 2.47

server.flavor.disk

body

integer

The size of the root disk that was created in GiB.

New in version 2.47
New in version 2.47

server.flavor.ephemeral

body

integer

The size of the ephemeral disk that was created, in GiB.

New in version 2.47
New in version 2.47

server.flavor.swap

body

integer

The size of a dedicated swap disk that was allocated, in MiB.

New in version 2.47
New in version 2.47

server.flavor.original_name

body

string

The display name of a flavor.

New in version 2.47
New in version 2.47

server.flavor.extra_specs

body

object

A dictionary of the flavor’s extra-specs key-and-value pairs. This will only be included if the user is allowed by policy to index flavor extra_specs.

New in version 2.47
New in version 2.47

server.hostId

body

string

An ID string representing the host. This is a hashed value so will not actually look like a hostname, and is hashed with data from the project_id, so the same physical host as seen by two different project_ids, will be different. It is useful when within the same project you need to determine if two instances are on the same or different physical hosts for the purposes of availability or performance.

server.host_status

body

[‘string’, ‘null’]

The host status. Values where next value in list can override the previous:

  • UP if nova-compute up.

  • UNKNOWN if nova-compute not reported by servicegroup driver.

  • DOWN if nova-compute forced down.

  • MAINTENANCE if nova-compute is disabled.

  • Empty string indicates there is no host for server.

This attribute appears in the response only if the policy permits. By default, only administrators can get this parameter.

New in version 2.75
New in version 2.16

server.OS-EXT-SRV-ATTR:hostname

body

string

The hostname of the instance reported in the metadata service. This parameter only appears in responses for administrators until microversion 2.90, after which it is shown for all users.

Note

This information is published via the metadata service and requires application such as cloud-init to propagate it through to the instance.

New in version 2.75
New in version 2.3

server.OS-EXT-SRV-ATTR:hypervisor_hostname

body

string

The hypervisor host name provided by the Nova virt driver. For the Ironic driver, it is the Ironic node uuid. Appears in the response for administrative users only.

New in version 2.75

server.id

body

string

Id of the server

server.image

body

object

The UUID and links for the image for your server instance. The image object will be an empty string when you boot the server from a volume.

server.image.id

body

string

The image ID

server.OS-EXT-SRV-ATTR:instance_name

body

string

The instance name. The Compute API generates the instance name from the instance name template. Appears in the response for administrative users only.

New in version 2.75

server.locked

body

boolean

True if the instance is locked otherwise False.

New in version 2.9
New in version 2.9

server.OS-EXT-SRV-ATTR:kernel_id

body

string

The UUID of the kernel image when using an AMI. Will be null if not. By default, it appears in the response for administrative users only.

New in version 2.75
New in version 2.3

server.key_name

body

string

The name of associated key pair, if any.

New in version 2.75

server.OS-EXT-SRV-ATTR:launch_index

body

integer

When servers are launched via multiple create, this is the sequence in which the servers were launched. By default, it appears in the response for administrative users only.

New in version 2.75
New in version 2.3

server.OS-SRV-USG:launched_at

body

string

The date and time when the server was launched.

The date and time stamp format is ISO 8601:

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00.

The hh±:mm value, if included, is the time zone as an offset from UTC. If the deleted_at date and time stamp is not set, its value is null.

New in version 2.75

server.metadata

body

object

A dictionary of metadata key-and-value pairs, which is maintained for backward compatibility.

server.name

body

string

The server name.

server.OS-EXT-STS:power_state

body

integer

The power state of the instance. This is an enum value that is mapped as:

0: NOSTATE
1: RUNNING
3: PAUSED
4: SHUTDOWN
6: CRASHED
7: SUSPENDED

New in version 2.75

server.progress

body

integer

A percentage value of the operation progress. This parameter only appears when the server status is ACTIVE, BUILD, REBUILD, RESIZE, VERIFY_RESIZE or MIGRATING.

server.tenant_id

body

string

The UUID of the tenant in a multi-tenancy cloud.

server.OS-EXT-SRV-ATTR:ramdisk_id

body

string

The UUID of the ramdisk image when using an AMI. Will be null if not. By default, it appears in the response for administrative users only.

New in version 2.75
New in version 2.3

server.OS-EXT-SRV-ATTR:reservation_id

body

string

The reservation id for the server. This is an id that can be useful in tracking groups of servers created with multiple create, that will all have the same reservation_id. By default, it appears in the response for administrative users only.

New in version 2.75
New in version 2.3

server.OS-EXT-SRV-ATTR:root_device_name

body

string

The root device name for the instance By default, it appears in the response for administrative users only.

New in version 2.75
New in version 2.3

server.status

body

string

The server status.

server.OS-EXT-STS:task_state

body

string

The task state of the instance.

New in version 2.75

server.OS-SRV-USG:terminated_at

body

string

The date and time when the server was deleted.

The date and time stamp format is ISO 8601:

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. If the deleted_at date and time stamp is not set, its value is null.

New in version 2.75

server.trusted_image_certificates

body

[‘array’, ‘null’]

A list of trusted certificate IDs, that were used during image signature verification to verify the signing certificate. The list is restricted to a maximum of 50 IDs. The value is null if trusted certificate IDs are not set.

New in version 2.63
New in version 2.63

server.updated

body

string

The date and time when the resource was updated. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

server.OS-EXT-SRV-ATTR:user_data

body

string

The user_data the instance was created with. By default, it appears in the response for administrative users only.

New in version 2.75
New in version 2.3

server.user_id

body

string

The user ID of the user who owns the server.

server.OS-EXT-STS:vm_state

body

string

The VM state.

New in version 2.75

404

Error

Updates the editable attributes of an existing server.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

200

Ok

Name

Location

Type

Description

server

body

object

A server object.

server.accessIPv4

body

string

IPv4 address that should be used to access this server. May be automatically set by the provider.

server.accessIPv6

body

string

IPv6 address that should be used to access this server. May be automatically set by the provider.

server.addresses

body

object

The addresses for the server. Servers with status BUILD hide their addresses information.

server.OS-EXT-AZ:availability_zone

body

string

The availability zone name.

New in version 2.75

server.OS-EXT-SRV-ATTR:host

body

string

The name of the compute host on which this instance is running. Appears in the response for administrative users only.

New in version 2.75

server.config_drive

body

string

Indicates whether or not a config drive was used for this server. The value is True or an empty string. An empty string stands for False.

New in version 2.75

server.created

body

string

The date and time when the resource was created. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

server.description

body

string

The description of the server. Before microversion 2.19 this was set to the server name.

New in version 2.19

server.OS-DCF:diskConfig

body

string

Disk configuration. The value is either:

  • AUTO. The API builds the server with a single partition the size of the target flavor disk. The API automatically adjusts the file system to fit the entire partition.

  • MANUAL. The API builds the server by using the partition scheme and file system that is in the source image. If the target flavor disk is larger, The API does not partition the remaining disk space.

server.fault

body

object

A fault object. Only displayed when the server status is ERROR or DELETED and a fault occurred.

server.fault.code

body

integer

The error response code.

server.fault.created

body

string

The date and time when the exception was raised. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

server.fault.message

body

string

The error message.

server.fault.details

body

string

The stack trace. It is available if the response code is not 500 or you have the administrator privilege

server.flavor

body

object

Before microversion 2.47 this contains the ID and links for the flavor used to boot the server instance. This can be an empty object in case flavor information is no longer present in the system.

As of microversion 2.47 this contains a subset of the actual flavor information used to create the server instance, represented as a nested dictionary.

server.flavor.id

body

string

The UUID of the server.
Available until version 2.46

server.flavor.vcpus

body

integer

The number of virtual CPUs that were allocated to the server.

New in version 2.47
New in version 2.47

server.flavor.ram

body

integer

The amount of RAM a flavor has, in MiB.

New in version 2.47
New in version 2.47

server.flavor.disk

body

integer

The size of the root disk that was created in GiB.

New in version 2.47
New in version 2.47

server.flavor.ephemeral

body

integer

The size of the ephemeral disk that was created, in GiB.

New in version 2.47
New in version 2.47

server.flavor.swap

body

integer

The size of a dedicated swap disk that was allocated, in MiB.

New in version 2.47
New in version 2.47

server.flavor.original_name

body

string

The display name of a flavor.

New in version 2.47
New in version 2.47

server.flavor.extra_specs

body

object

A dictionary of the flavor’s extra-specs key-and-value pairs. This will only be included if the user is allowed by policy to index flavor extra_specs.

New in version 2.47
New in version 2.47

server.hostId

body

string

An ID string representing the host. This is a hashed value so will not actually look like a hostname, and is hashed with data from the project_id, so the same physical host as seen by two different project_ids, will be different. It is useful when within the same project you need to determine if two instances are on the same or different physical hosts for the purposes of availability or performance.

server.host_status

body

[‘string’, ‘null’]

The host status. Values where next value in list can override the previous:

  • UP if nova-compute up.

  • UNKNOWN if nova-compute not reported by servicegroup driver.

  • DOWN if nova-compute forced down.

  • MAINTENANCE if nova-compute is disabled.

  • Empty string indicates there is no host for server.

This attribute appears in the response only if the policy permits. By default, only administrators can get this parameter.

New in version 2.75
New in version 2.16

server.OS-EXT-SRV-ATTR:hostname

body

string

The hostname of the instance reported in the metadata service. This parameter only appears in responses for administrators until microversion 2.90, after which it is shown for all users.

Note

This information is published via the metadata service and requires application such as cloud-init to propagate it through to the instance.

New in version 2.75
New in version 2.3

server.OS-EXT-SRV-ATTR:hypervisor_hostname

body

string

The hypervisor host name provided by the Nova virt driver. For the Ironic driver, it is the Ironic node uuid. Appears in the response for administrative users only.

New in version 2.75

server.id

body

string

Id of the server

server.image

body

object

The UUID and links for the image for your server instance. The image object will be an empty string when you boot the server from a volume.

server.image.id

body

string

The image ID

server.OS-EXT-SRV-ATTR:instance_name

body

string

The instance name. The Compute API generates the instance name from the instance name template. Appears in the response for administrative users only.

New in version 2.75

server.locked

body

boolean

True if the instance is locked otherwise False.

New in version 2.9
New in version 2.9

server.OS-EXT-SRV-ATTR:kernel_id

body

string

The UUID of the kernel image when using an AMI. Will be null if not. By default, it appears in the response for administrative users only.

New in version 2.75
New in version 2.3

server.key_name

body

string

The name of associated key pair, if any.

New in version 2.75

server.OS-EXT-SRV-ATTR:launch_index

body

integer

When servers are launched via multiple create, this is the sequence in which the servers were launched. By default, it appears in the response for administrative users only.

New in version 2.75
New in version 2.3

server.OS-SRV-USG:launched_at

body

string

The date and time when the server was launched.

The date and time stamp format is ISO 8601:

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00.

The hh±:mm value, if included, is the time zone as an offset from UTC. If the deleted_at date and time stamp is not set, its value is null.

New in version 2.75

server.metadata

body

object

A dictionary of metadata key-and-value pairs, which is maintained for backward compatibility.

server.name

body

string

The server name.

server.OS-EXT-STS:power_state

body

integer

The power state of the instance. This is an enum value that is mapped as:

0: NOSTATE
1: RUNNING
3: PAUSED
4: SHUTDOWN
6: CRASHED
7: SUSPENDED

New in version 2.75

server.progress

body

integer

A percentage value of the operation progress. This parameter only appears when the server status is ACTIVE, BUILD, REBUILD, RESIZE, VERIFY_RESIZE or MIGRATING.

server.tenant_id

body

string

The UUID of the tenant in a multi-tenancy cloud.

server.OS-EXT-SRV-ATTR:ramdisk_id

body

string

The UUID of the ramdisk image when using an AMI. Will be null if not. By default, it appears in the response for administrative users only.

New in version 2.75
New in version 2.3

server.OS-EXT-SRV-ATTR:reservation_id

body

string

The reservation id for the server. This is an id that can be useful in tracking groups of servers created with multiple create, that will all have the same reservation_id. By default, it appears in the response for administrative users only.

New in version 2.75
New in version 2.3

server.OS-EXT-SRV-ATTR:root_device_name

body

string

The root device name for the instance By default, it appears in the response for administrative users only.

New in version 2.75
New in version 2.3

server.status

body

string

The server status.

server.OS-EXT-STS:task_state

body

string

The task state of the instance.

New in version 2.75

server.OS-SRV-USG:terminated_at

body

string

The date and time when the server was deleted.

The date and time stamp format is ISO 8601:

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. If the deleted_at date and time stamp is not set, its value is null.

New in version 2.75

server.trusted_image_certificates

body

[‘array’, ‘null’]

A list of trusted certificate IDs, that were used during image signature verification to verify the signing certificate. The list is restricted to a maximum of 50 IDs. The value is null if trusted certificate IDs are not set.

New in version 2.63
New in version 2.63

server.updated

body

string

The date and time when the resource was updated. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

server.OS-EXT-SRV-ATTR:user_data

body

string

The user_data the instance was created with. By default, it appears in the response for administrative users only.

New in version 2.75
New in version 2.3

server.user_id

body

string

The user ID of the user who owns the server.

server.OS-EXT-STS:vm_state

body

string

The VM state.

New in version 2.75

404

Error

Deletes a server.

By default, the instance is going to be (hard) deleted immediately from the system, but you can set reclaim_instance_interval > 0 to make the API soft delete the instance, so that the instance won’t be deleted until the reclaim_instance_interval has expired since the instance was soft deleted. The instance marked as SOFT_DELETED can be recovered via restore action before it’s really deleted from the system.

Preconditions

Asynchronous postconditions

Troubleshooting

Normal response codes: 204

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Responses

204

Ok

404

Error

409

Error

Confirms a pending resize action for a server.

Specify the confirmResize action in the request body.

After you make this request, you typically must keep polling the server status to determine whether the request succeeded. A successfully confirming resize operation shows a status of ACTIVE or SHUTOFF and a migration status of confirmed. You can also see the resized server in the compute node that OpenStack Compute manages.

Preconditions

You can only confirm the resized server where the status is VERIFY_RESIZE.

If the server is locked, you must have administrator privileges to confirm the server.

Troubleshooting

If the server status remains VERIFY_RESIZE, the request failed. Ensure you meet the preconditions and run the request again. If the request fails again, the server status should be ERROR and a migration status of error. Investigate the compute back end or ask your cloud provider. There are some options for trying to correct the server status:

Note that the cloud provider may still need to cleanup any orphaned resources on the source hypervisor.

Normal response codes: 204

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Cancels and reverts a pending resize action for a server.

Specify the revertResize action in the request body.

Preconditions

You can only revert the resized server where the status is VERIFY_RESIZE and the OS-EXT-STS:vm_state is resized.

If the server is locked, you must have administrator privileges to revert the resizing.

Asynchronous Postconditions

After you make this request, you typically must keep polling the server status to determine whether the request succeeded. A reverting resize operation shows a status of REVERT_RESIZE and a task_state of resize_reverting. If successful, the status will return to ACTIVE or SHUTOFF. You can also see the reverted server in the compute node that OpenStack Compute manages.

Troubleshooting

If the server status remains VERIFY_RESIZE, the request failed. Ensure you meet the preconditions and run the request again. If the request fails again, investigate the compute back end.

The server is not reverted in the compute node that OpenStack Compute manages.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Reboots a server.

Specify the reboot action in the request body.

Preconditions

The preconditions for rebooting a server depend on the type of reboot.

You can only SOFT reboot a server when its status is ACTIVE.

You can only HARD reboot a server when its status is one of:

If the server is locked, you must have administrator privileges to reboot the server.

Asynchronous Postconditions

After you successfully reboot a server, its status changes to ACTIVE.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Resizes a server.

Specify the resize action in the request body.

Preconditions

You can only resize a server when its status is ACTIVE or SHUTOFF.

If the server is locked, you must have administrator privileges to resize the server.

Asynchronous Postconditions

A successfully resized server shows a VERIFY_RESIZE status and finished migration status. If the cloud has configured the resize_confirm_window option of the Compute service to a positive value, the Compute service automatically confirms the resize operation after the configured interval.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Rebuilds a server.

Specify the rebuild action in the request body.

This operation recreates the root disk of the server.

With microversion 2.93, we support rebuilding volume backed instances which will reimage the volume with the provided image. For microversion < 2.93, this operation keeps the contents of the volume given the image provided is same as the image with which the volume was created else the operation will error out.

Preconditions

The server status must be ACTIVE, SHUTOFF or ERROR.

Asynchronous Postconditions

If the server was in status SHUTOFF before the rebuild, it will be stopped and in status SHUTOFF after the rebuild, otherwise it will be ACTIVE if the rebuild was successful or ERROR if the rebuild failed.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Creates an image from a server.

Specify the createImage action in the request body.

After you make this request, you typically must keep polling the status of the created image to determine whether the request succeeded.

If the operation succeeds, the created image has a status of active and the server status returns to the original status. You can also see the new image in the image back end that OpenStack Image service manages.

Preconditions

The server must exist.

You can only create a new image from the server when its status is ACTIVE, SHUTOFF, SUSPENDED or PAUSED (PAUSED is only supported for image-backed servers).

The project must have sufficient volume snapshot quota in the block storage service when the server has attached volumes. If the project does not have sufficient volume snapshot quota, the API returns a 403 error.

Asynchronous Postconditions

A snapshot image will be created in the Image service.

In the image-backed server case, volume snapshots of attached volumes will not be created. In the volume-backed server case, volume snapshots will be created for all volumes attached to the server and then those will be represented with a block_device_mapping image property in the resulting snapshot image in the Image service. If that snapshot image is used later to create a new server, it will result in a volume-backed server where the root volume is created from the snapshot of the original root volume. The volumes created from the snapshots of the original other volumes will be attached to the server.

Troubleshooting

If the image status remains uploading or shows another error status, the request failed. Ensure you meet the preconditions and run the request again. If the request fails again, investigate the image back end.

If the server status does not go back to an original server’s status, the request failed. Ensure you meet the preconditions, or check if there is another operation that causes race conditions for the server, then run the request again. If the request fails again, investigate the compute back end or ask your cloud provider.

If the request fails due to an error on OpenStack Compute service, the image is purged from the image store that OpenStack Image service manages. Ensure you meet the preconditions and run the request again. If the request fails again, investigate OpenStack Compute service or ask your cloud provider.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

Name

Location

Type

Description

image_id

body

string

The UUID for the resulting image snapshot.
New in version 2.45

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Starts a stopped server and changes its status to ACTIVE.

Specify the os-start action in the request body.

Preconditions

The server status must be SHUTOFF.

If the server is locked, you must have administrator privileges to start the server.

Asynchronous Postconditions

After you successfully start a server, its status changes to ACTIVE.

Troubleshooting

If the server status does not change to ACTIVE, the start operation failed. Ensure that you meet the preconditions and run the request again. If the request fails again, investigate whether another operation is running that causes a race condition.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Stops a running server and changes its status to SHUTOFF.

Specify the os-stop action in the request body.

Preconditions

The server status must be ACTIVE or ERROR.

If the server is locked, you must have administrator privileges to stop the server.

Asynchronous Postconditions

After you successfully stop a server, its status changes to SHUTOFF. This API operation does not delete the server instance data and the data will be available again after os-start action.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Resets networking on a server.

Specify the resetNetwork action in the request body.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), gone(410)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Injects network information into a server.

Specify the injectNetworkInfo action in the request body.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Resets the state of a server.

Specify the os-resetState action and the state in the request body.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Changes the administrative password for a server.

Specify the changePassword action in the request body.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), notImplemented(501)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Shows console output for a server.

This API returns the text of the console since boot. The content returned may be large. Limit the lines of console text, beginning at the tail of the content, by setting the optional length parameter in the request body.

The server to get console log from should set export LC_ALL=en_US.UTF-8 in order to avoid incorrect unicode error.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), notFound(404), conflict(409), methodNotImplemented(501)

Request

Responses

201

Ok

Name

Location

Type

Description

output

body

string

The console output as a string. Control characters will be escaped to create a valid JSON string.

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Creates a back up of a server.

Specify the createBackup action in the request body.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

Name

Location

Type

Description

image_id

body

string

The UUID for the resulting image snapshot.
New in version 2.45

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Restores a previously soft-deleted server instance. You cannot use this method to restore deleted instances.

Specify the restore action in the request body.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Force-deletes a server before deferred cleanup.

Specify the forceDelete action in the request body.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Evacuates a server from a failed host to a new host.

Preconditions

Starting from API version 2.68, the force parameter is no longer accepted as this could not be meaningfully supported by servers with complex resource allocations.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

Name

Location

Type

Description

adminPass

body

string

An administrative password to access the evacuated instance. If you set enable_instance_password configuration option to False, the API wouldn’t return the adminPass field in response.

Available until version 2.13

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Adds a floating IP address to a server, which associates that address with the server.

A pool of floating IP addresses, configured by the cloud administrator, is available in OpenStack Compute. The project quota defines the maximum number of floating IP addresses that you can allocate to the project. After you create (allocate) a floating IPaddress for a project, you can associate that address with the server. Specify the addFloatingIp action in the request body.

If an instance is connected to multiple networks, you can associate a floating IP address with a specific fixed IP address by using the optional fixed_address parameter.

Preconditions

The server must exist.

You can only add a floating IP address to the server when its status is ACTIVE or STOPPED

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Removes, or disassociates, a floating IP address from a server.

The IP address is returned to the pool of IP addresses that is available for all projects. When you remove a floating IP address and that IP address is still associated with a running instance, it is automatically disassociated from that instance.

Specify the removeFloatingIp action in the request body.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Locks a server.

Specify the lock action in the request body.

Most actions by non-admin users are not allowed to the server after this operation is successful and the server is locked. See the “Lock, Unlock” item in Server actions for the restricted actions. But administrators can perform actions on the server even though the server is locked. Note that from microversion 2.73 it is possible to specify a reason when locking the server.

The unlock action will unlock a server in locked state so additional actions can be performed on the server by non-admin users.

You can know whether a server is locked or not and the locked_reason (if specified, from the 2.73 microversion) by the List Servers Detailed API or the Show Server Details API.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file. Administrators can overwrite owner’s lock.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Unlocks a locked server.

Specify the unlock action in the request body.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Migrates a server to a host.

Specify the migrate action in the request body.

Up to microversion 2.55, the scheduler chooses the host. Starting from microversion 2.56, the host parameter is available to specify the destination host. If you specify null or don’t specify this parameter, the scheduler chooses a host.

Asynchronous Postconditions

A successfully migrated server shows a VERIFY_RESIZE status and finished migration status. If the cloud has configured the resize_confirm_window option of the Compute service to a positive value, the Compute service automatically confirms the migrate operation after the configured interval.

There are two different policies for this action, depending on whether the host parameter is set. Both defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403) itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Live-migrates a server to a new host without rebooting.

Specify the os-migrateLive action in the request body.

Use the host parameter to specify the destination host. If this param is null, the scheduler chooses a host. If a scheduled host is not suitable to do migration, the scheduler tries up to migrate_max_retries rescheduling attempts.

Starting from API version 2.25, the block_migration parameter could be to auto so that nova can decide value of block_migration during live migration.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Starting from REST API version 2.34 pre-live-migration checks are done asynchronously, results of these checks are available in instance-actions. Nova responds immediately, and no pre-live-migration checks are returned. The instance will not immediately change state to ERROR, if a failure of the live-migration checks occurs.

Starting from API version 2.68, the force parameter is no longer accepted as this could not be meaningfully supported by servers with complex resource allocations.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403) itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Adds a fixed IP address to a server instance, which associates that address with the server. The fixed IP address is retrieved from the network that you specify in the request.

Specify the addFixedIp action and the network ID in the request body.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Removes, or disassociates, a fixed IP address from a server.

Specify the removeFixedIp action in the request body.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Pauses a server. Changes its status to PAUSED.

Specify the pause action in the request body.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), notImplemented(501)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Unpauses a paused server and changes its status to ACTIVE.

Specify the unpause action in the request body.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), notImplemented(501)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Gets a VNC console for a server.

Specify the os-getVNCConsole action in the request body.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), notImplemented(501)

Request

Responses

201

Ok

Name

Location

Type

Description

console

body

object

The remote console object.

console.type

body

string

The type of RDP console. The only valid value is rdp-html5.

console.url

body

string

The URL used to connect to the RDP console.

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Gets a SPICE console for a server.

Specify the os-getSPICEConsole action in the request body.

The only supported connection type is spice-html5. The type parameter should be set to spice-html5.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), notImplemented(501)

Request

Responses

201

Ok

Name

Location

Type

Description

console

body

object

The remote console object.

console.type

body

string

The type of RDP console. The only valid value is rdp-html5.

console.url

body

string

The URL used to connect to the RDP console.

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Gets an RDP console for a server.

The only supported connect type is rdp-html5. The type parameter should be set as rdp-html5.

Specify the os-getRDPConsole action in the request body.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), notImplemented(501)

Request

Responses

201

Ok

Name

Location

Type

Description

console

body

object

The remote console object.

console.type

body

string

The type of RDP console. The only valid value is rdp-html5.

console.url

body

string

The URL used to connect to the RDP console.

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Gets a serial console for a server.

Specify the os-getSerialConsole action in the request body.

The only supported connection type is serial. The type parameter should be set as serial.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), notImplemented(501)

Request

Responses

201

Ok

Name

Location

Type

Description

console

body

object

The remote console object.

console.type

body

string

The type of RDP console. The only valid value is rdp-html5.

console.url

body

string

The URL used to connect to the RDP console.

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Puts a server in rescue mode and changes its status to RESCUE.

Specify the rescue action in the request body.

If you specify the rescue_image_ref extended attribute, the image is used to rescue the instance. If you omit an image reference, the base image reference is used by default.

Asynchronous Postconditions

After you successfully rescue a server and make a GET /servers/​{server_id}​ request, its status changes to RESCUE.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), notImplemented(501)

Request

Responses

201

Ok

Name

Location

Type

Description

adminPass

body

string

An administrative password to access the evacuated instance. If you set enable_instance_password configuration option to False, the API wouldn’t return the adminPass field in response.

Available until version 2.13

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Unrescues a server. Changes status to ACTIVE.

Specify the unrescue action in the request body.

Preconditions

The server must exist.

You can only unrescue a server when its status is RESCUE.

Asynchronous Postconditions

After you successfully unrescue a server and make a GET /servers/​{server_id}​ request, its status changes to ACTIVE.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), notImplemented(501)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Adds a security group to a server.

Specify the addSecurityGroup action in the request body.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Removes a security group from a server.

Specify the removeSecurityGroup action in the request body.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Shelves a server.

Specify the shelve action in the request body.

All associated data and resources are kept but anything still in memory is not retained. To restore a shelved instance, use the unshelve action. To remove a shelved instance, use the shelveOffload action.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Preconditions

The server status must be ACTIVE, SHUTOFF, PAUSED, or SUSPENDED.

If the server is locked, you must have administrator privileges to shelve the server.

Asynchronous Postconditions

After you successfully shelve a server, its status changes to SHELVED and the image status is ACTIVE. The server instance data appears on the compute node that the Compute service manages.

If you boot the server from volumes or set the shelved_offload_time option to 0, the Compute service automatically deletes the instance on compute nodes and changes the server status to SHELVED_OFFLOADED.

Troubleshooting

If the server status does not change to SHELVED or SHELVED_OFFLOADED, the shelve operation failed. Ensure that you meet the preconditions and run the request again. If the request fails again, investigate whether another operation is running that causes a race condition.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Shelf-offloads, or removes, a shelved server.

Specify the shelveOffload action in the request body.

Data and resource associations are deleted. If an instance is no longer needed, you can remove that instance from the hypervisor to minimize resource usage.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Preconditions

The server status must be SHELVED.

If the server is locked, you must have administrator privileges to shelve-offload the server.

Asynchronous Postconditions

After you successfully shelve-offload a server, its status changes to SHELVED_OFFLOADED. The server instance data appears on the compute node.

Troubleshooting

If the server status does not change to SHELVED_OFFLOADED, the shelve-offload operation failed. Ensure that you meet the preconditions and run the request again. If the request fails again, investigate whether another operation is running that causes a race condition.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Unshelves, or restores, a shelved server.

Specify the unshelve action in the request body.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Preconditions

Unshelving a server without parameters requires its status to be SHELVED or SHELVED_OFFLOADED.

Unshelving a server with availability_zone and/or host parameters requires its status to be only SHELVED_OFFLOADED otherwise HTTP 409 conflict response is returned.

If a server is locked, you must have administrator privileges to unshelve the server.

As of microversion 2.91, you can unshelve to a specific compute node if you have PROJECT_ADMIN privileges. This microversion also gives the ability to pin a server to an availability_zone and to unpin a server from any availability_zone.

When a server is pinned to an availability_zone, the server move operations will keep the server in that availability_zone. However, when the server is not pinned to any availability_zone, the move operations can move the server to nodes in different availability_zones.

The behavior according to unshelve parameters will follow the below table.

Asynchronous Postconditions

After you successfully unshelve a server, its status changes to ACTIVE. The server appears on the compute node.

The shelved image is deleted from the list of images returned by an API call.

Troubleshooting

If the server status does not change to ACTIVE, the unshelve operation failed. Ensure that you meet the preconditions and run the request again. If the request fails again, investigate whether another operation is running that causes a race condition.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Suspends a server and changes its status to SUSPENDED.

Specify the suspend action in the request body.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Resumes a suspended server and changes its status to ACTIVE.

Specify the resume action in the request body.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

202

Accepted

204

Ok

400

Error

401

Error

403

Error

404

Error

409

Error

410

Error

501

Error

Lists all consoles for a server.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), gone(410)

Responses

200

Ok

410

Error

Creates a console for a server.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), gone(410)

Request

Responses

201

Ok

410

Error

Shows console details for a server.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), gone(410)

Responses

200

Ok

410

Error

Deletes a console for a server.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), gone(410)

Responses

204

Ok

410

Error

Shows basic usage data for a server.

Policy defaults enable only users with the administrative role. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), notfound(404), conflict(409), notimplemented(501)

Responses

200

Ok

Name

Location

Type

Description

driver

body

string

The driver on which the VM is running. Possible values are:

  • libvirt

  • xenapi

  • vmwareapi

  • ironic

New in version 2.48
New in version 2.48

config_drive

body

boolean

Indicates whether or not a config drive was used for this server.

New in version 2.48
New in version 2.48

hypervisor

body

string

The hypervisor on which the VM is running. Examples for libvirt driver may be: qemu, kvm or xen.

New in version 2.48
New in version 2.48

hypervisor_os

body

string

The hypervisor OS.

New in version 2.48
New in version 2.48

id

body

string

Id of the resource

name

body

string

Name

num_cpus

body

integer

The number of vCPUs.

New in version 2.48
New in version 2.48

num_disks

body

integer

The number of disks.

New in version 2.48
New in version 2.48

num_nics

body

integer

The number of vNICs.

New in version 2.48
New in version 2.48

state

body

string

A string enum denoting the current state of the VM. Possible values are:

  • pending

  • running

  • paused

  • shutdown

  • crashed

  • suspended

New in version 2.48
New in version 2.48

uptime

body

integer

The amount of time in seconds that the VM has been running.

New in version 2.48
New in version 2.48

400

Error

404

Error

409

Error

501

Error

Lists IP addresses that are assigned to an instance.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

addresses

body

object

The addresses information for the server.

404

Error

Shows IP addresses details for a network label of a server instance.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

Lists all metadata for a server.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

metadata

body

object

Metadata key and value pairs. The maximum size for each metadata key and value pair is 255 bytes.

404

Error

Create or update one or more metadata items for a server.

Creates any metadata items that do not already exist in the server, replaces exists metadata items that match keys. Does not modify items that are not in the request.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

Name

Location

Type

Description

metadata

body

object

Metadata key and value pairs. The maximum size for each metadata key and value pair is 255 bytes.

403

Error

404

Error

409

Error

Replaces one or more metadata items for a server.

Creates any metadata items that do not already exist in the server. Removes and completely replaces any metadata items that already exist in the server with the metadata items in the request.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

200

Ok

Name

Location

Type

Description

metadata

body

object

Metadata key and value pairs. The maximum size for each metadata key and value pair is 255 bytes.

403

Error

404

Error

409

Error

Shows details for a metadata item, by key, for a server.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

meta

body

object

Metadata key and value pairs. The maximum size for each metadata key and value pair is 255 bytes.

404

Error

Creates or replaces a metadata item, by key, for a server.

Creates a metadata item that does not already exist in the server. Replaces existing metadata items that match keys with the metadata item in the request.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

200

Ok

400

Error

403

Error

404

Error

409

Error

Deletes a metadata item, by key, from a server.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 204

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Responses

204

Ok

404

Error

409

Error

Lists actions for a server.

Action information of deleted instances can be returned for requests starting with microversion 2.21.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

400

Error

404

Error

Shows details for a server action.

Action details of deleted instances can be returned for requests later than microversion 2.21.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

instanceAction

body

object

The instance action object.

instanceAction.action

body

string

The name of the action.

instanceAction.message

body

[‘string’, ‘null’]

The related error message for when an action fails.

instanceAction.project_id

body

string

The ID of the project which initiated the server action.

instanceAction.request_id

body

string

The request id generated when execute the API of this action.

instanceAction.start_time

body

string

The date and time when the action was started.

instanceAction.user_id

body

string

The ID of the user which initiated the server action.

instanceAction.updated_at

body

string

The date and time when the instance action or the action event of instance action was updated. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

New in version 2.58
New in version 2.58

404

Error

Lists port interfaces that are attached to a server.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), NotImplemented(501)

Responses

200

Ok

404

Error

501

Error

Creates a port interface and uses it to attach a port to a server.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), computeFault(500), NotImplemented(501)

Request

Responses

201

Ok

Name

Location

Type

Description

interfaceAttachment

body

object

The interface attachment.

interfaceAttachment.mac_addr

body

string

The MAC address.

interfaceAttachment.net_id

body

string

The network ID.

interfaceAttachment.port_id

body

string

The port ID.

interfaceAttachment.port_state

body

string

The port state.

interfaceAttachment.tag

body

[‘string’, ‘null’]

The device tag applied to the virtual network interface or null.

New in version 2.70
New in version 2.70

400

Error

403

Error

404

Error

409

Error

500

Error

501

Error

Shows details for a port interface that is attached to a server.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

interfaceAttachment

body

object

The interface attachment.

interfaceAttachment.mac_addr

body

string

The MAC address.

interfaceAttachment.net_id

body

string

The network ID.

interfaceAttachment.port_id

body

string

The port ID.

interfaceAttachment.port_state

body

string

The port state.

interfaceAttachment.tag

body

[‘string’, ‘null’]

The device tag applied to the virtual network interface or null.

New in version 2.70
New in version 2.70

403

Error

404

Error

Detaches a port interface from a server.

Normal response codes: 202

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), NotImplemented(501)

Responses

202

Ok

400

Error

404

Error

409

Error

501

Error

Shows the administrative password for a server.

This operation calls the metadata service to query metadata information and does not read password information from the server itself.

The password saved in the metadata service is typically encrypted using the public SSH key injected into this server, so the SSH private key is needed to read the password.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

password

body

string

The password returned from metadata server.

404

Error

Clears the encrypted administrative password for a server, which removes it from the database.

This action does not actually change the instance server password.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 204

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

204

Ok

404

Error

Lists the virtual interfaces for an instance.

Policy defaults enable only users with the administrative role or the owner of the server to perform this operation. Change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), gone(410)

Responses

200

Ok

410

Error

List volume attachments for an instance.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

Attach a volume to an instance.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

201

Ok

Name

Location

Type

Description

volumeAttachment

body

object

A dictionary representation of a volume attachment containing the fields device, id, serverId and volumeId.

volumeAttachment.device

body

string

Name of the device in the attachment object, such as, /dev/vdb.

volumeAttachment.id

body

string

The volume ID of the attachment.

Available until version 2.88
Available until version 2.88

volumeAttachment.serverId

body

string

The UUID of the server.

volumeAttachment.volumeId

body

string

The UUID of the attached volume.

volumeAttachment.tag

body

[‘string’, ‘null’]

The device tag applied to the volume block device or null.

New in version 2.70
New in version 2.70

volumeAttachment.delete_on_termination

body

boolean

A flag indicating if the attached volume will be deleted when the server is deleted.

New in version 2.79
New in version 2.79

volumeAttachment.attachment_id

body

string

The UUID of the associated volume attachment in Cinder.

New in version 2.89
New in version 2.89

volumeAttachment.bdm_uuid

body

string

The UUID of the block device mapping record in Nova for the attachment.

New in version 2.89
New in version 2.89

400

Error

403

Error

404

Error

409

Error

Show a detail of a volume attachment.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

volumeAttachment

body

object

A dictionary representation of a volume attachment containing the fields device, id, serverId and volumeId.

volumeAttachment.device

body

string

Name of the device in the attachment object, such as, /dev/vdb.

volumeAttachment.id

body

string

The volume ID of the attachment.

Available until version 2.88
Available until version 2.88

volumeAttachment.serverId

body

string

The UUID of the server.

volumeAttachment.volumeId

body

string

The UUID of the attached volume.

volumeAttachment.tag

body

[‘string’, ‘null’]

The device tag applied to the volume block device or null.

New in version 2.70
New in version 2.70

volumeAttachment.delete_on_termination

body

boolean

A flag indicating if the attached volume will be deleted when the server is deleted.

New in version 2.79
New in version 2.79

volumeAttachment.attachment_id

body

string

The UUID of the associated volume attachment in Cinder.

New in version 2.89
New in version 2.89

volumeAttachment.bdm_uuid

body

string

The UUID of the block device mapping record in Nova for the attachment.

New in version 2.89
New in version 2.89

404

Error

Update a volume attachment.

Policy default role is ‘rule:system_admin_or_owner’, its scope is [system, project], which allow project members or system admins to change the fields of an attached volume of a server. Policy defaults enable only users with the administrative role to change volumeId via this operation. Cloud providers can change these permissions through the policy.json file.

Updating, or what is commonly referred to as “swapping”, volume attachments with volumes that have more than one read/write attachment, is not supported.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

202

Ok

Name

Location

Type

Description

volumeAttachment

body

object

A dictionary representation of a volume attachment containing the fields device, id, serverId and volumeId.

volumeAttachment.device

body

string

Name of the device in the attachment object, such as, /dev/vdb.

volumeAttachment.id

body

string

The volume ID of the attachment.

Available until version 2.88
Available until version 2.88

volumeAttachment.serverId

body

string

The UUID of the server.

volumeAttachment.volumeId

body

string

The UUID of the attached volume.

volumeAttachment.tag

body

[‘string’, ‘null’]

The device tag applied to the volume block device or null.

New in version 2.70
New in version 2.70

volumeAttachment.delete_on_termination

body

boolean

A flag indicating if the attached volume will be deleted when the server is deleted.

New in version 2.79
New in version 2.79

volumeAttachment.attachment_id

body

string

The UUID of the associated volume attachment in Cinder.

New in version 2.89
New in version 2.89

volumeAttachment.bdm_uuid

body

string

The UUID of the block device mapping record in Nova for the attachment.

New in version 2.89
New in version 2.89

400

Error

404

Error

409

Error

Detach a volume from an instance.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Responses

202

Ok

400

Error

403

Error

404

Error

409

Error

Lists security groups for a server.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

Shows NUMA topology information for a server.

Policy defaults enable only users with the administrative role or the owners of the server to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), notfound(404), forbidden(403)

Responses

200

Ok

404

Error

server-migrations

Lists in-progress live migrations for a given server.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

Show details for an in-progress live migration for a given server.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

Name

Location

Type

Description

migration

body

object

The server migration object.

migration.created_at

body

string

The date and time when the resource was created. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

migration.updated_at

body

string

The date and time when the resource was updated. The date and time stamp format is ISO 8601

CCYY-MM-DDThh:mm:ss±hh:mm

For example, 2015-08-27T09:49:58-05:00. The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

migration.dest_compute

body

string

The target compute for a migration.

migration.dest_host

body

string

The target host for a migration.

migration.dest_node

body

string

The target node for a migration.

migration.id

body

integer

The ID of the server migration.

migration.source_compute

body

string

The source compute for a migration.

migration.source_node

body

string

The source node for a migration.

migration.status

body

string

The current status of the migration.

migration.project_id

body

[‘string’, ‘null’]

The ID of the project which initiated the server migration. The value may be null for older migration records.

New in version 2.80
New in version 2.80

migration.user_id

body

[‘string’, ‘null’]

The ID of the user which initiated the server migration. The value may be null for older migration records.

New in version 2.80
New in version 2.80

migration.uuid

body

string

The UUID of the migration.

New in version 2.59
New in version 2.59

migration.disk_processed_bytes

body

integer

The amount of disk, in bytes, that has been processed during the migration.

migration.disk_remaining_bytes

body

integer

The amount of disk, in bytes, that still needs to be migrated.

migration.disk_total_bytes

body

integer

The total amount of disk, in bytes, that needs to be migrated.

migration.memory_processed_bytes

body

integer

The amount of memory, in bytes, that has been processed during the migration.

migration.memory_remaining_bytes

body

integer

The amount of memory, in bytes, that still needs to be migrated.

migration.memory_total_bytes

body

integer

The total amount of memory, in bytes, that needs to be migrated.

migration.server_uuid

body

string

The UUID of the server.

404

Error

Abort an in-progress live migration.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Preconditions

The server OS-EXT-STS:task_state value must be migrating.

If the server is locked, you must have administrator privileges to force the completion of the server migration.

For microversions from 2.24 to 2.64 the migration status must be running, for microversion 2.65 and greater, the migration status can also be queued and preparing.

Asynchronous Postconditions

After you make this request, you typically must keep polling the server status to determine whether the request succeeded. You may also monitor the migration using:

Troubleshooting

If the server status remains MIGRATING for an inordinate amount of time, the request may have failed. Ensure you meet the preconditions and run the request again. If the request fails again, investigate the compute back end.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Responses

202

Ok

400

Error

404

Error

409

Error

Force an in-progress live migration for a given server to complete.

Specify the force_complete action in the request body.

Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the policy.json file.

Preconditions

The server OS-EXT-STS:vm_state value must be active and the server OS-EXT-STS:task_state value must be migrating.

If the server is locked, you must have administrator privileges to force the completion of the server migration.

The migration status must be running.

Asynchronous Postconditions

After you make this request, you typically must keep polling the server status to determine whether the request succeeded.

Troubleshooting

If the server status remains MIGRATING for an inordinate amount of time, the request may have failed. Ensure you meet the preconditions and run the request again. If the request fails again, investigate the compute back end. More details can be found in the admin guide.

Normal response codes: 202

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409)

Request

Responses

202

Ok

400

Error

403

Error

404

Error

409

Error

server-tags

Lists all tags for a server.

Normal response codes: 200

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

404

Error

Replaces all tags on specified server with the new set of tags.

Normal response codes: 200

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Request

Responses

200

Ok

404

Error

409

Error

Deletes all tags from the specified server.

Normal response codes: 204

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

204

Ok

404

Error

409

Error

Checks tag existence on the server. If tag exists response with 204 status code will be returned. Otherwise returns 404.

Normal response codes: 204

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

204

Ok

404

Error

Adds a single tag to the server if server has no specified tag. Response code in this case is 201.

If the server has specified tag just returns 204.

Normal response codes: 201, 204

Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404)

Responses

200

Ok

400

Error

404

Error

409

Error

Deletes a single tag from the specified server.

Normal response codes: 204

Error response codes: unauthorized(401), forbidden(403), itemNotFound(404)

Responses

204

Ok

404

Error

409

Error