Managed Object - VsanVdsSystem(vim.vsan.VsanVdsSystem)

See also
ComputeResource, Task, VirtualMachine, VsanVdsMigrationPlan
Since
vSAN API 6.6


Managed Object Description

vSAN optimized methods for performing VDS related operations, especially migrations from VSS to VDS. In every vCenter server there is a singleton instance of this class with the Managed Object ID of 'vsan-vds-system'.

Properties

Name Type Description
None

Methods

Methods defined in this Managed Object
VsanRollbackVdsToVss, VsanVdsGetMigrationPlan, VsanVdsMigrateVss

VsanRollbackVdsToVss(rollbackVdsToVss)

Rollback the change committed by the VsanVdsMigrateVss.
Required Privileges
System.Read

Parameters

NameTypeDescription
_thisManagedObjectReference A reference to the VsanVdsSystem used to make the method call.
taskManagedObjectReference
to a Task

The task associated with the change committed by the VsanVdsMigrateVss

Return Value

Type Description
xsd:booleanAlways return True

Faults

Type Description
NotFoundTask not found
RuntimeFaultThrown if any type of runtime fault is thrown that is not covered by the other faults; for example, a communication error.
VsanFaultAny unexpected runtime error.

Events

Type
None

Show WSDL type definition



VsanVdsGetMigrationPlan(vsanVdsGetMigrationPlan)

Computes a migration plan to convert the VSS instances per host in the cluster to a newly created VDS. The VDS preserves all settings of the VSS, and all consumers (vmknics, VM vNICs, pNICs) are considered as part of the migration. The VSS vSwitch and portgroup instances across the hosts are matched to each other by common name. It is expected that hosts have a uniform configuration, and issues will be raised in the migration plan if deviations are found. Any deviations will still be carried over, but may require renaming of portgroups and additional VDS portgroups to resolve the conflicts. The migration plan is defined to be safe, i.e., the effective data path for all impacted VMs, vmknics and so on are going to be using the same settings as before the migration. The only change will be in any additional pNICs added as part of the migration. Note: This API can also be used to create a new VDS without any portgroups, but with the physical NICs attached, and with good settings for vSAN, by simply passing the vswitchName as NULL.
Required Privileges
System.Read

Parameters

NameTypeDescription
_thisManagedObjectReference A reference to the VsanVdsSystem used to make the method call.
clusterManagedObjectReference
to a ComputeResource

Hosts of this cluster will be migrated to the new VDS
vswitchName*xsd:string

Name of the original VSS vSwitch

Since vSAN API 6.6
vdsNamexsd:string

Name of the new VDS
vmnicDevices*xsd:string[]

Physical NICs that are currently unused to be attached to the new vDS.

Since vSAN API 6.6
infraVm*ManagedObjectReference[]
to a VirtualMachine[]

Infrastructure VMs that will be handled specially during mirgaion.

Since vSAN API 6.6
*Need not be set

Return Value

Type Description
VsanVdsMigrationPlanDetailed migration plan.

Faults

Type Description
NotFoundwhen specified cluster doesn't exist.
RuntimeFaultThrown if any type of runtime fault is thrown that is not covered by the other faults; for example, a communication error.
VsanFaultAny unexpected runtime error.

Events

Type
None

Show WSDL type definition



VsanVdsMigrateVss(vsanVdsMigrateVss)

Perform a migration to convert the VSS instances per host in the cluster to a newly created VDS. The VDS preserves all settings of the VSS, and all consumers (vmknics, VM vNICs, pNICs) are considered as part of the migration. The VSS vSwitch and portgroup instances across the hosts are matched to each other by common name. It is expected that hosts have a uniform configuration, and issues will be raised in the migration plan if deviations are found. Any deviations will still be carried over, but may require renaming of portgroups and additional VDS portgroups to resolve the conflicts. The migration plan is defined to be safe, i.e., the effective data path for all impacted VMs, vmknics and so on are going to be using the same settings as before the migration. The only change will be in any additional pNICs added as part of the migration. Note: This API can also be used to create a new VDS without any portgroups, but with the physical NICs attached, and with good settings for vSAN, by simply passing the vswitchName as NULL. If a migration plan is passed in, the API makes sure that no changes have happened and that the migration plan is still current. This can be used to make sure that the migration plan that the user reviewed doesn't deviate from the actual migration performed. If there are any inaccessible or orphaned VMs found the migration will not be performed. This is a safety measure as such VMs may loose their networking. If there are any inaccessible hosts in the cluster the migration will fail.
Required Privileges
System.Read

Parameters

NameTypeDescription
_thisManagedObjectReference A reference to the VsanVdsSystem used to make the method call.
clusterManagedObjectReference
to a ComputeResource

Hosts of this cluster will be migrated to the new VDS
migrationPlan*VsanVdsMigrationPlan

Detailed migration plan

Since vSAN API 6.6
vswitchName*xsd:string

Name of the original VSS vswitch

Since vSAN API 6.6
vdsNamexsd:string

Name of the new VDS
vmnicDevices*xsd:string[]

Physical NICs that are currently unused to be attached to the new VDS.

Since vSAN API 6.6
infraVm*ManagedObjectReference[]
to a VirtualMachine[]

Infrastructure VMs that will be handled specially during mirgaion.

Since vSAN API 6.6
*Need not be set

Return Value

Type Description
ManagedObjectReference
to a Task
The task associated with the migration

Faults

Type Description
NotFoundwhen specified cluster doesn't exist.
RuntimeFaultThrown if any type of runtime fault is thrown that is not covered by the other faults; for example, a communication error.
VsanFaultAny unexpected runtime error.

Events

Type
None

Show WSDL type definition