Esx Settings Clusters Vms Transition MultiSourceEnableSpec

Esx Settings Clusters Vms Transition MultiSourceEnableSpec

The Esx Settings Clusters Vms Transition MultiSourceEnableSpec schema contains properties that describe specification for enablement of multiple EAM managed solutions into single vLCM managed solution.

Supported only for solutions with deployment type Esx Settings Clusters Vms DeploymentType.CLUSTER_VM_SET.

This schema was added in vSphere API 9.1.0.0.

JSON Example

{
    "eam_agency_ids": [
        "string"
    ],
    "solution": {
        "deployment_type": "string",
        "display_name": "string",
        "display_version": "string",
        "vm_name_template": {
            "prefix": "string",
            "suffix": "string"
        },
        "host_solution_spec": {
            "prefer_host_configuration": false,
            "vm_networks": [
                "string"
            ],
            "vm_datastores": [
                "string"
            ]
        },
        "cluster_solution_spec": {
            "vm_count": 0,
            "vm_placement_policies": [
                "string"
            ],
            "vm_networks": {
                "vm_networks": "string"
            },
            "vm_datastores": [
                "string"
            ],
            "devices": {},
            "remediation_policy": "string",
            "alternative_vm_specs": [
                {
                    "selection_criteria": {
                        "selection_type": "string",
                        "extra_config_value": "string"
                    },
                    "devices": {}
                }
            ]
        },
        "hook_configurations": {
            "hook_configurations": {
                "timeout": 0
            }
        },
        "ovf_resource": {
            "location_type": "string",
            "url": "string",
            "ssl_certificate_validation": "string",
            "certificate": "string",
            "authentication_scheme": "string"
        },
        "ovf_descriptor_properties": {
            "ovf_descriptor_properties": "string"
        },
        "vm_clone_config": "string",
        "vm_storage_policy": "string",
        "vm_storage_profiles": [
            "string"
        ],
        "vm_disk_type": "string",
        "vm_resource_pool": "string",
        "vm_folder": "string",
        "vm_resource_spec": {
            "ovf_deployment_option": "string"
        },
        "redeployment_policy": "string"
    },
    "source_vm_selection_specs": {
        "source_vm_selection_specs": {
            "selection_type": "string",
            "extra_config_value": "string"
        }
    },
    "cluster_module": "string"
}

array of string

eam_agency_ids

Required

Identifiers of the cluster bound solutions in EAM (EAM agencies).

This property was added in vSphere API 9.1.0.0.

solution

Required

Target desired solution specification in vLCM.

This property was added in vSphere API 9.1.0.0.

object

source_vm_selection_specs

Optional

Relation between System VMs and their respective Esx Settings Clusters Vms VmSelectionSpecs.

Provided VM IDs must be part of the solution being tarnsitioned and must exist in the cluster where the solution is installed.

Provided Esx Settings Clusters Vms VmSelectionSpecs must be present in the applied desired state as part of the Esx Settings Clusters Vms ClusterSolutionSpec.alternative_vm_specs.

This property was added in vSphere API 9.1.0.0.

If missing or null, no Esx Settings Clusters Vms VmSelectionSpecs are applied on the source agencies' System VMs during the enablement.

When clients pass a value of this schema as a parameter, the key in the property map must be an identifier for the resource type: VirtualMachine. When operations return a value of this schema as a response, the key in the property map will be an identifier for the resource type: VirtualMachine.

string

cluster_module

Optional

Cluster module to be reused for transitioned System VMs. Used to express VM-VM anti affinity relation between System VMs in the vSphere Cluster.

The module must exist for the cluster where the solution is installed.

This property was added in vSphere API 9.1.0.0.

If missing or null, no cluster module is reused. vLCM creates a new module if needed.

When clients pass a value of this schema as a parameter, the property must be an identifier for the resource type: com.vmware.vcenter.cluster.modules. When operations return a value of this schema as a response, the property will be an identifier for the resource type: com.vmware.vcenter.cluster.modules.

Parameter To

Esx Settings Clusters Vms Transition multiSourceEnable$Task