Esx Settings Clusters Vms Transition multiSourceEnable$Task
Enables multiple EAM managed solutions in vLCM as a single solution. The solution specification is validated before the enablement is started.
The enablement only transfers ownership of the solutions from EAM to LCCM and sets the desired state in LCCM. The new desired state is not applied, the solution system VMs are untouched. The following happens once the operation is started:
- A removal of the corresponding agencies in EAM is triggered.
The following happens once the operation is completed:
- The corresponding agencies in EAM can no longer be controlled through the EAM API.
- The management of the desired solution specification can be done only trough vLCM. See Esx Settings Clusters Vms Solutions
Supported only for solutions with deployment type Esx Settings Clusters Vms DeploymentType.CLUSTER_VM_SET.
This operation was added in vSphere API 9.1.0.0.
Returns an authorization error if you do not have all of the privileges described as follows:
- Operation execution requires
VcIntegrity.systemVM.Write.
Identifier of the cluster.
The parameter must be an identifier for the resource type: ClusterComputeResource.
Identifier of the solution.
The parameter must be an identifier for the resource type: com.vmware.esx.settings.vms.SystemVmSolution.
Enablement specification.
Show optional properties
{
"eam_agency_ids": [
{}
],
"solution": {}
}{
"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"
}Identifiers of the cluster bound solutions in EAM (EAM agencies).
This property was added in vSphere API 9.1.0.0.
Target desired solution specification in vLCM.
This property was added in vSphere API 9.1.0.0.
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.
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.
Success!
Vapi Std Errors InvalidArgument If:
- the validation of the cluster desired specification fails.
- the solution associated with solution already exist in vLCM for the cluster.
- the agencies associated with the eamAgencyIds property exist, but is not in the scope of the cluster. The value of the data property of Vapi Std Errors Error contains more information. It is a schema that contains all the properties defined in Esx Settings Clusters Vms Transition ValidationResult.
Vapi Std Errors NotAllowedInCurrentState If System VMs are disabled on the cluster via internal ESX Agent Manager (EAM) API (eam.EsxtAgentManager#disable).
Vapi Std Errors Unsupported If the cluster associated with cluster is not managed by vLCM.
{
"messages": [
{
"id": "string",
"default_message": "string",
"args": [
"string"
],
"params": {
"params": {
"s": "string",
"dt": "string",
"i": 0,
"d": "number",
"l": {
"id": "string",
"params": {
"params": "Vapi Std LocalizationParam Object"
}
},
"format": "string",
"precision": 0
}
},
"localized": "string"
}
],
"data": {},
"error_type": "string"
}Stack of one or more localizable messages for human error consumers.
The message at the top of the stack (first in the list) describes the error from the perspective of the operation the client invoked.
Each subsequent message in the stack describes the "cause" of the prior message.
Data to facilitate clients responding to the operation reporting a standard error to indicating that it was unable to complete successfully.
Operations may provide data that clients can use when responding to errors. Since the data that clients need may be specific to the context of the operation reporting the error, different operations that report the same error may provide different data in the error. The documentation for each each operation will describe what, if any, data it provides for each error it reports.
The Vapi Std Errors ArgumentLocations, Vapi Std Errors FileLocations, and Vapi Std Errors TransientIndication schemas are intended as possible values for this property. Vapi Std DynamicID may also be useful as a value for this property (although that is not its primary purpose). Some resources may provide their own specific schemas for use as the value of this property when reporting errors from their operations.
Some operations will not set this property when reporting errors.
Discriminator field to help API consumers identify the structure type.
For more information see: Vapi Std Errors Error Type.
This property was added in vSphere API 6.7.2.
Can be missing or null for compatibility with preceding implementations.
If the caller is not authenticated.
{
"messages": [
{
"id": "string",
"default_message": "string",
"args": [
"string"
],
"params": {
"params": {
"s": "string",
"dt": "string",
"i": 0,
"d": "number",
"l": "Vapi Std NestedLocalizableMessage Object",
"format": "string",
"precision": 0
}
},
"localized": "string"
}
],
"data": {},
"error_type": "string",
"challenge": "string"
}Indicates the authentication challenges applicable to the target API provider. It can be used by a client to discover the correct authentication scheme to use. The exact syntax of the value is defined by the specific provider, the protocol and authentication schemes used.
For example, a provider using REST may adhere to the WWW-Authenticate HTTP header specification, RFC7235, section 4.1. In this case an example challenge value may be: SIGN realm="27da1358-2ba4-11e9-b210-d663bd873d93",sts="http://vcenter/sso?vsphere.local", Basic realm="vCenter"
This property was added in vSphere API 7.0.0.0.
This property is optional because it was added in a newer version than its parent node.
If the user doesn't have the required privileges.
{
"messages": [
{
"id": "string",
"default_message": "string",
"args": [
"string"
],
"params": {
"params": {
"s": "string",
"dt": "string",
"i": 0,
"d": "number",
"l": "Vapi Std NestedLocalizableMessage Object",
"format": "string",
"precision": 0
}
},
"localized": "string"
}
],
"data": {},
"error_type": "string",
"challenge": "string"
}Indicates the authentication challenges applicable to the target API provider. It can be used by a client to discover the correct authentication scheme to use. The exact syntax of the value is defined by the specific provider, the protocol and authentication schemes used.
For example, a provider using REST may adhere to the WWW-Authenticate HTTP header specification, RFC7235, section 4.1. In this case an example challenge value may be: SIGN realm="27da158-2ba4-11e9-b",sts="http://vcenter/sso?vsphere.local", Basic realm="vCenter"
This property was added in vSphere API 9.1.0.0.
This property is optional because it was added in a newer version than its parent node.
If there is no cluster associated with the cluster or if there is no EAM agency associated with any of the IDs in eamAgencyIDs property of the spec in the system.
{
"messages": [
{
"id": "string",
"default_message": "string",
"args": [
"string"
],
"params": {
"params": {
"s": "string",
"dt": "string",
"i": 0,
"d": "number",
"l": "Vapi Std NestedLocalizableMessage Object",
"format": "string",
"precision": 0
}
},
"localized": "string"
}
],
"data": {},
"error_type": "string"
}If there is an internal error. The accompanying error message will give more details about the failure.
{
"messages": [
{
"id": "string",
"default_message": "string",
"args": [
"string"
],
"params": {
"params": {
"s": "string",
"dt": "string",
"i": 0,
"d": "number",
"l": "Vapi Std NestedLocalizableMessage Object",
"format": "string",
"precision": 0
}
},
"localized": "string"
}
],
"data": {},
"error_type": "string"
}Stack of one or more localizable messages for human error consumers.
The message at the top of the stack (first in the list) describes the error from the perspective of the operation the client invoked.
Each subsequent message in the stack describes the "cause" of the prior message.
Data to facilitate clients responding to the operation reporting a standard error to indicating that it was unable to complete successfully.
Operations may provide data that clients can use when responding to errors. Since the data that clients need may be specific to the context of the operation reporting the error, different operations that report the same error may provide different data in the error. The documentation for each each operation will describe what, if any, data it provides for each error it reports.
The Vapi Std Errors ArgumentLocations, Vapi Std Errors FileLocations, and Vapi Std Errors TransientIndication schemas are intended as possible values for this property. Vapi Std DynamicID may also be useful as a value for this property (although that is not its primary purpose). Some resources may provide their own specific schemas for use as the value of this property when reporting errors from their operations.
Some operations will not set this property when reporting errors.
Discriminator field to help API consumers identify the structure type.
For more information see: Vapi Std Errors Error Type.
This property was added in vSphere API 6.7.2.
Can be missing or null for compatibility with preceding implementations.
If the service is not available.
{
"messages": [
{
"id": "string",
"default_message": "string",
"args": [
"string"
],
"params": {
"params": {
"s": "string",
"dt": "string",
"i": 0,
"d": "number",
"l": "Vapi Std NestedLocalizableMessage Object",
"format": "string",
"precision": 0
}
},
"localized": "string"
}
],
"data": {},
"error_type": "string"
} curl -X POST -H 'Authorization: <value>' -H 'Content-Type: application/json' -d '{"eam_agency_ids":["string"],"solution":"{}"}' https://{api_host}/api/esx/settings/clusters/{cluster}/vms/transition/{solution}?action=multi-source-enable&vmw-task=true