server migration

A server migration provides a way to move an instance from one host to another. There are four types of migration operation supported: live migration, cold migration, resize and evacuation.

Compute v2

server migration list

List server migrations

openstack server migration list
    [--sort-column SORT_COLUMN]
    [--sort-ascending | --sort-descending]
    [--server <server>]
    [--host <host>]
    [--status <status>]
    [--type <type>]
    [--marker <marker>]
    [--limit <limit>]
    [--changes-since <changes-since>]
    [--changes-before <changes-before>]
    [--project <project>]
    [--project-domain <project-domain>]
    [--user <user>]
    [--user-domain <user-domain>]

--sort-column SORT_COLUMN

specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated

--sort-ascending

sort the column(s) in ascending order

--sort-descending

sort the column(s) in descending order

--server <server>

Filter migrations by server (name or ID)

--host <host>

Filter migrations by source or destination host

--status <status>

Filter migrations by status

--type <type>

Filter migrations by type

--marker <marker>

The last migration of the previous page; displays list of migrations after ‘marker’. Note that the marker is the migration UUID. (supported with –os-compute-api-version 2.59 or above)

--limit <limit>

Maximum number of migrations to display. Note that there is a configurable max limit on the server, and the limit that is used will be the minimum of what is requested here and what is configured in the server. (supported with –os-compute-api-version 2.59 or above)

--changes-since <changes-since>

List only migrations changed later or equal to a certain point of time. The provided time should be an ISO 8061 formatted time, e.g. 2016-03-04T06:27:59Z. (supported with –os-compute-api-version 2.59 or above)

--changes-before <changes-before>

List only migrations changed earlier or equal to a certain point of time. The provided time should be an ISO 8061 formatted time, e.g. 2016-03-04T06:27:59Z. (supported with –os-compute-api-version 2.66 or above)

--project <project>

Filter migrations by project (name or ID) (supported with –os-compute-api-version 2.80 or above)

--project-domain <project-domain>

Domain the project belongs to (name or ID). This can be used in case collisions between project names exist.

--user <user>

Filter migrations by user (name or ID) (supported with –os-compute-api-version 2.80 or above)

--user-domain <user-domain>

Domain the user belongs to (name or ID). This can be used in case collisions between user names exist.