MigratingVm

Details of the VM from an AWS source.

Details of the target VM in Compute Engine.

The time the migrating VM was created (this refers to this resource and not to the time it was installed in the source).

Details of the current running replication cycle.

Provides details of future CutoverJobs of a MigratingVm. Set to empty when cutover forecast is unavailable.

The description attached to the migrating VM by the user.

The display name attached to the MigratingVm by the user.

Provides details on the state of the Migrating VM in case of an error in replication.

The group this migrating vm is included in, if any. The group is represented by the full path of the appropriate Group resource.

The labels of the migrating VM.

Details of the last replication cycle. This will be updated whenever a replication cycle is finished and is not to be confused with last_sync which is only updated on successful replication cycles.

The most updated snapshot created time in the source that finished replication.

Required. The migratingVm identifier.

The identifier of the MigratingVm.

The replication schedule policy.

The recent clone jobs performed on the migrating VM. This field holds the vm's last completed clone job and the vm's running clone job, if one exists. Note: To have this field populated you need to explicitly request it via the "view" parameter of the Get/List request.

The recent cutover jobs performed on the migrating VM. This field holds the vm's last completed cutover job and the vm's running cutover job, if one exists. Note: To have this field populated you need to explicitly request it via the "view" parameter of the Get/List request.

A request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).

The unique ID of the VM in the source. The VM's name in vSphere can be changed, so this is not the VM's name but rather its moRef id. This id is of the form vm-.

State of the MigratingVm.

The last time the migrating VM state was updated.

The last time the migrating VM resource was updated.