VmVmAntiAffinity
Specification of a VM placement policy that anti-affines a group of VMs among themselves.
Since: vSphere API Release 9.1.0.0
{
"_typeName": "string",
"antiAffinedVmsTag": {
"_typeName": "string",
"nameId": {
"_typeName": "string",
"tag": "string",
"category": "string"
},
"uuid": "string"
},
"policyStrictness": "string",
"policyTopology": "string"
}Name of the vSphere tag identifying the VMs that need to be anti-affined with each other.
When this type of placement policy is specified for a VM, (via vmPlacementPolicies or vmPlacementPolicies), then that VM is anti-affined to all the other VMs that have antiAffinedVmsTag. This means that DRS will attempt to place all the VMs with antiAffinedVmsTag tag on different target hosts/clusters/ vSphereZones (where the topology of the target is specified by policyTopology).
For example - VmVmAntiAffinity placement policy with antiAffinedVmsTag equal to "prod-workloads" would mean that all the VMs that have a vSphere tag with the name "prod-workloads" should be placed on different target hosts/clusters/vSphereZones (as indicated by policyTopology).
Specifies the strictness of this VmVmAntiAffinity placement policy while placing a VM for which this policy is specified.
For details, see VmPlacementPolicyVmPlacementPolicyStrictnessEnum
If this field is left unset, then the default value of PreferredDuringPlacementPreferredDuringExecution will be assumed.
Specifies the topology for enforcing this VmVmAntiAffinity placement policy while placing a VM for which this policy is specified.
For possible values, see VmPlacementPolicyVmPlacementPolicyTopologyEnum.
For example: - If this is set to VSphereZone, the VMs that have antiAffinedVmsTag tag attached to them should be placed in different vSphere Zones. - If this is set to Host, the VMs that have antiAffinedVmsTag tag attached to them should be placed on different ESXi hosts (but they may be placed in the same vSphere Zone).
If this field is left unset, then the default value of Host will be assumed.