ComputeCluster
A note on the naming of this resource: VMware refers to clusters of hosts in the UI and documentation as clusters, HA clusters, or DRS clusters. All of these refer to the same kind of resource (with the latter two referring to specific features of clustering). We use
vsphere..ComputeClusterto differentiate host clusters from datastore clusters, which are clusters of datastores that can be used to distribute load and ensure fault tolerance via distribution of virtual machines. Datastore clusters can also be managed through the provider, via thevsphere..DatastoreClusterresource.
The vsphere..ComputeCluster resource can be used to create and manage
clusters of hosts allowing for resource control of compute resources, load
balancing through DRS, and high availability through vSphere HA.
For more information on vSphere clusters and DRS, see this page. For more information on vSphere HA, see this page.
NOTE: This resource requires vCenter and is not available on direct ESXi connections.
NOTE: vSphere DRS requires a vSphere Enterprise Plus license.
vSphere Version Requirements
A large number of settings in the vsphere..ComputeCluster resource require a
specific version of vSphere to function. Rather than include warnings at every
setting or section, these settings are documented below. Note that this list
is for cluster-specific attributes only, and does not include the
tags parameter, which requires vSphere 6.0 or higher across all
resources that can be tagged.
All settings are footnoted by an asterisk (*) in their specific section in
the documentation, which takes you here.
Settings that require vSphere version 6.0 or higher
These settings require vSphere 6.0 or higher:
ha_datastore_apd_recovery_actionha_datastore_apd_responseha_datastore_apd_response_delayha_datastore_pdl_responseha_vm_component_protection
Settings that require vSphere version 6.5 or higher
These settings require vSphere 6.5 or higher:
drs_enable_predictive_drsha_admission_control_host_failure_tolerance(Whenha_admission_control_policyis set toresourcePercentageorslotPolicy. Permitted in all versions underfailoverHosts)ha_admission_control_resource_percentage_auto_computeha_vm_restart_timeoutha_vm_dependency_restart_conditionha_vm_restart_additional_delayproactive_ha_automation_levelproactive_ha_enabledproactive_ha_moderate_remediationproactive_ha_provider_idsproactive_ha_severe_remediation
Create a ComputeCluster Resource
new ComputeCluster(name: string, args: ComputeClusterArgs, opts?: CustomResourceOptions);def ComputeCluster(resource_name, opts=None, custom_attributes=None, datacenter_id=None, dpm_automation_level=None, dpm_enabled=None, dpm_threshold=None, drs_advanced_options=None, drs_automation_level=None, drs_enable_predictive_drs=None, drs_enable_vm_overrides=None, drs_enabled=None, drs_migration_threshold=None, folder=None, force_evacuate_on_destroy=None, ha_admission_control_failover_host_system_ids=None, ha_admission_control_host_failure_tolerance=None, ha_admission_control_performance_tolerance=None, ha_admission_control_policy=None, ha_admission_control_resource_percentage_auto_compute=None, ha_admission_control_resource_percentage_cpu=None, ha_admission_control_resource_percentage_memory=None, ha_admission_control_slot_policy_explicit_cpu=None, ha_admission_control_slot_policy_explicit_memory=None, ha_admission_control_slot_policy_use_explicit_size=None, ha_advanced_options=None, ha_datastore_apd_recovery_action=None, ha_datastore_apd_response=None, ha_datastore_apd_response_delay=None, ha_datastore_pdl_response=None, ha_enabled=None, ha_heartbeat_datastore_ids=None, ha_heartbeat_datastore_policy=None, ha_host_isolation_response=None, ha_host_monitoring=None, ha_vm_component_protection=None, ha_vm_dependency_restart_condition=None, ha_vm_failure_interval=None, ha_vm_maximum_failure_window=None, ha_vm_maximum_resets=None, ha_vm_minimum_uptime=None, ha_vm_monitoring=None, ha_vm_restart_additional_delay=None, ha_vm_restart_priority=None, ha_vm_restart_timeout=None, host_cluster_exit_timeout=None, host_managed=None, host_system_ids=None, name=None, proactive_ha_automation_level=None, proactive_ha_enabled=None, proactive_ha_moderate_remediation=None, proactive_ha_provider_ids=None, proactive_ha_severe_remediation=None, tags=None, __props__=None);func NewComputeCluster(ctx *Context, name string, args ComputeClusterArgs, opts ...ResourceOption) (*ComputeCluster, error)public ComputeCluster(string name, ComputeClusterArgs args, CustomResourceOptions? opts = null)- name string
- The unique name of the resource.
- args ComputeClusterArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- opts ResourceOptions
- A bag of options that control this resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args ComputeClusterArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args ComputeClusterArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
ComputeCluster Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Programming Model docs.
Inputs
The ComputeCluster resource accepts the following input properties:
- Datacenter
Id string The managed object ID of the datacenter to create the cluster in. Forces a new resource if changed.
- Custom
Attributes Dictionary<string, string> A map of custom attribute ids to attribute value strings to set for the datastore cluster.
- Dpm
Automation stringLevel The automation level for host power operations in this cluster. Can be one of
manualorautomated. Default:manual.- Dpm
Enabled bool Enable DPM support for DRS in this cluster. Requires
drs_enabledto betruein order to be effective. Default:false.- Dpm
Threshold int A value between
1and5indicating the threshold of load within the cluster that influences host power operations. This affects both power on and power off operations - a lower setting will tolerate more of a surplus/deficit than a higher setting. Default:3.- Drs
Advanced Dictionary<string, string>Options A key/value map that specifies advanced options for DRS and DPM.
- Drs
Automation stringLevel The default automation level for all virtual machines in this cluster. Can be one of
manual,partiallyAutomated, orfullyAutomated. Default:manual.- Drs
Enable boolPredictive Drs When
true, enables DRS to use data from [vRealize Operations Manager][ref-vsphere-vro] to make proactive DRS recommendations. *- Drs
Enable boolVm Overrides Allow individual DRS overrides to be set for virtual machines in the cluster. Default:
true.- Drs
Enabled bool Enable DRS for this cluster. Default:
false.- Drs
Migration intThreshold A value between
1and5indicating the threshold of imbalance tolerated between hosts. A lower setting will tolerate more imbalance while a higher setting will tolerate less. Default:3.- Folder string
The relative path to a folder to put this cluster in. This is a path relative to the datacenter you are deploying the cluster to. Example: for the
dc1datacenter, and a providedfolderoffoo/bar, The provider will place a cluster namedcompute-cluster-testin a host folder located at/dc1/host/foo/bar, with the final inventory path being/dc1/host/foo/bar/datastore-cluster-test.- Force
Evacuate boolOn Destroy When destroying the resource, setting this to
truewill auto-remove any hosts that are currently a member of the cluster, as if they were removed by taking their entry out ofhost_system_ids(see below). This is an advanced option and should only be used for testing. Default:false.- Ha
Admission List<string>Control Failover Host System Ids Defines the managed object IDs of hosts to use as dedicated failover hosts. These hosts are kept as available as possible - admission control will block access to the host, and DRS will ignore the host when making recommendations.
- Ha
Admission intControl Host Failure Tolerance The maximum number of failed hosts that admission control tolerates when making decisions on whether to permit virtual machine operations. The maximum is one less than the number of hosts in the cluster. Default:
1. *- Ha
Admission intControl Performance Tolerance The percentage of resource reduction that a cluster of virtual machines can tolerate in case of a failover. A value of 0 produces warnings only, whereas a value of 100 disables the setting. Default:
100(disabled).- Ha
Admission stringControl Policy The type of admission control policy to use with vSphere HA. Can be one of
resourcePercentage,slotPolicy,failoverHosts, ordisabled. Default:resourcePercentage.- Ha
Admission boolControl Resource Percentage Auto Compute Automatically determine available resource percentages by subtracting the average number of host resources represented by the
ha_admission_control_host_failure_tolerancesetting from the total amount of resources in the cluster. Disable to supply user-defined values. Default:true. *- Ha
Admission intControl Resource Percentage Cpu Controls the user-defined percentage of CPU resources in the cluster to reserve for failover. Default:
100.- Ha
Admission intControl Resource Percentage Memory Controls the user-defined percentage of memory resources in the cluster to reserve for failover. Default:
100.- Ha
Admission intControl Slot Policy Explicit Cpu Controls the user-defined CPU slot size, in MHz. Default:
32.- Ha
Admission intControl Slot Policy Explicit Memory Controls the user-defined memory slot size, in MB. Default:
100.- Ha
Admission boolControl Slot Policy Use Explicit Size Controls whether or not you wish to supply explicit values to CPU and memory slot sizes. The default is
false, which tells vSphere to gather a automatic average based on all powered-on virtual machines currently in the cluster.- Ha
Advanced Dictionary<string, string>Options A key/value map that specifies advanced options for vSphere HA.
- Ha
Datastore stringApd Recovery Action Controls the action to take on virtual machines if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
noneorreset. Default:none. *- Ha
Datastore stringApd Response Controls the action to take on virtual machines when the cluster has detected loss to all paths to a relevant datastore. Can be one of
disabled,warning,restartConservative, orrestartAggressive. Default:disabled. *- Ha
Datastore intApd Response Delay Controls the delay in minutes to wait after an APD timeout event to execute the response action defined in
ha_datastore_apd_response. Default:3minutes. *- Ha
Datastore stringPdl Response Controls the action to take on virtual machines when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
disabled,warning, orrestartAggressive. Default:disabled. *- Ha
Enabled bool Enable vSphere HA for this cluster. Default:
false.- Ha
Heartbeat List<string>Datastore Ids The list of managed object IDs for preferred datastores to use for HA heartbeating. This setting is only useful when
ha_heartbeat_datastore_policyis set to eitheruserSelectedDsorallFeasibleDsWithUserPreference.- Ha
Heartbeat stringDatastore Policy The selection policy for HA heartbeat datastores. Can be one of
allFeasibleDs,userSelectedDs, orallFeasibleDsWithUserPreference. Default:allFeasibleDsWithUserPreference.- Ha
Host stringIsolation Response The action to take on virtual machines when a host has detected that it has been isolated from the rest of the cluster. Can be one of
none,powerOff, orshutdown. Default:none.- Ha
Host stringMonitoring Global setting that controls whether vSphere HA remediates virtual machines on host failure. Can be one of
enabledordisabled. Default:enabled.- Ha
Vm stringComponent Protection Controls vSphere VM component protection for virtual machines in this cluster. Can be one of
enabledordisabled. Default:enabled. *- Ha
Vm stringDependency Restart Condition The condition used to determine whether or not virtual machines in a certain restart priority class are online, allowing HA to move on to restarting virtual machines on the next priority. Can be one of
none,poweredOn,guestHbStatusGreen, orappHbStatusGreen. The default isnone, which means that a virtual machine is considered ready immediately after a host is found to start it on. *- Ha
Vm intFailure Interval If a heartbeat from a virtual machine is not received within this configured interval, the virtual machine is marked as failed. The value is in seconds. Default:
30.- Ha
Vm intMaximum Failure Window The length of the reset window in which
ha_vm_maximum_resetscan operate. When this window expires, no more resets are attempted regardless of the setting configured inha_vm_maximum_resets.-1means no window, meaning an unlimited reset time is allotted. The value is specified in seconds. Default:-1(no window).- Ha
Vm intMaximum Resets The maximum number of resets that HA will perform to a virtual machine when responding to a failure event. Default:
3- Ha
Vm intMinimum Uptime The time, in seconds, that HA waits after powering on a virtual machine before monitoring for heartbeats. Default:
120(2 minutes).- Ha
Vm stringMonitoring The type of virtual machine monitoring to use when HA is enabled in the cluster. Can be one of
vmMonitoringDisabled,vmMonitoringOnly, orvmAndAppMonitoring. Default:vmMonitoringDisabled.- Ha
Vm intRestart Additional Delay Additional delay in seconds after ready condition is met. A VM is considered ready at this point. Default:
0(no delay). *- Ha
Vm stringRestart Priority The default restart priority for affected virtual machines when vSphere detects a host failure. Can be one of
lowest,low,medium,high, orhighest. Default:medium.- Ha
Vm intRestart Timeout The maximum time, in seconds, that vSphere HA will wait for virtual machines in one priority to be ready before proceeding with the next priority. Default:
600(10 minutes). *- Host
Cluster intExit Timeout The timeout for each host maintenance mode operation when removing hosts from a cluster. The value is specified in seconds. Default:
3600(1 hour).- Host
Managed bool Can be set to
trueif compute cluster membership will be managed through thehostresource rather than thecompute_clusterresource. Conflicts with:host_system_ids. >>>>>>> v1.18.3- Host
System List<string>Ids The [managed object IDs][docs-about-morefs] of the hosts to put in the cluster. Conflicts with:
host_managed.- Name string
The name of the cluster.
- Proactive
Ha stringAutomation Level Determines how the host quarantine, maintenance mode, or virtual machine migration recommendations made by proactive HA are to be handled. Can be one of
AutomatedorManual. Default:Manual. *- Proactive
Ha boolEnabled Enables Proactive HA. Default:
false. *- Proactive
Ha stringModerate Remediation The configured remediation for moderately degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toMaintenanceModewhenproactive_ha_severe_remediationis set toQuarantineMode. Default:QuarantineMode. *- Proactive
Ha List<string>Provider Ids The list of IDs for health update providers configured for this cluster. *
- Proactive
Ha stringSevere Remediation The configured remediation for severely degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toQuarantineModewhenproactive_ha_moderate_remediationis set toMaintenanceMode. Default:QuarantineMode. *- List<string>
The IDs of any tags to attach to this resource.
- Datacenter
Id string The managed object ID of the datacenter to create the cluster in. Forces a new resource if changed.
- Custom
Attributes map[string]string A map of custom attribute ids to attribute value strings to set for the datastore cluster.
- Dpm
Automation stringLevel The automation level for host power operations in this cluster. Can be one of
manualorautomated. Default:manual.- Dpm
Enabled bool Enable DPM support for DRS in this cluster. Requires
drs_enabledto betruein order to be effective. Default:false.- Dpm
Threshold int A value between
1and5indicating the threshold of load within the cluster that influences host power operations. This affects both power on and power off operations - a lower setting will tolerate more of a surplus/deficit than a higher setting. Default:3.- Drs
Advanced map[string]stringOptions A key/value map that specifies advanced options for DRS and DPM.
- Drs
Automation stringLevel The default automation level for all virtual machines in this cluster. Can be one of
manual,partiallyAutomated, orfullyAutomated. Default:manual.- Drs
Enable boolPredictive Drs When
true, enables DRS to use data from [vRealize Operations Manager][ref-vsphere-vro] to make proactive DRS recommendations. *- Drs
Enable boolVm Overrides Allow individual DRS overrides to be set for virtual machines in the cluster. Default:
true.- Drs
Enabled bool Enable DRS for this cluster. Default:
false.- Drs
Migration intThreshold A value between
1and5indicating the threshold of imbalance tolerated between hosts. A lower setting will tolerate more imbalance while a higher setting will tolerate less. Default:3.- Folder string
The relative path to a folder to put this cluster in. This is a path relative to the datacenter you are deploying the cluster to. Example: for the
dc1datacenter, and a providedfolderoffoo/bar, The provider will place a cluster namedcompute-cluster-testin a host folder located at/dc1/host/foo/bar, with the final inventory path being/dc1/host/foo/bar/datastore-cluster-test.- Force
Evacuate boolOn Destroy When destroying the resource, setting this to
truewill auto-remove any hosts that are currently a member of the cluster, as if they were removed by taking their entry out ofhost_system_ids(see below). This is an advanced option and should only be used for testing. Default:false.- Ha
Admission []stringControl Failover Host System Ids Defines the managed object IDs of hosts to use as dedicated failover hosts. These hosts are kept as available as possible - admission control will block access to the host, and DRS will ignore the host when making recommendations.
- Ha
Admission intControl Host Failure Tolerance The maximum number of failed hosts that admission control tolerates when making decisions on whether to permit virtual machine operations. The maximum is one less than the number of hosts in the cluster. Default:
1. *- Ha
Admission intControl Performance Tolerance The percentage of resource reduction that a cluster of virtual machines can tolerate in case of a failover. A value of 0 produces warnings only, whereas a value of 100 disables the setting. Default:
100(disabled).- Ha
Admission stringControl Policy The type of admission control policy to use with vSphere HA. Can be one of
resourcePercentage,slotPolicy,failoverHosts, ordisabled. Default:resourcePercentage.- Ha
Admission boolControl Resource Percentage Auto Compute Automatically determine available resource percentages by subtracting the average number of host resources represented by the
ha_admission_control_host_failure_tolerancesetting from the total amount of resources in the cluster. Disable to supply user-defined values. Default:true. *- Ha
Admission intControl Resource Percentage Cpu Controls the user-defined percentage of CPU resources in the cluster to reserve for failover. Default:
100.- Ha
Admission intControl Resource Percentage Memory Controls the user-defined percentage of memory resources in the cluster to reserve for failover. Default:
100.- Ha
Admission intControl Slot Policy Explicit Cpu Controls the user-defined CPU slot size, in MHz. Default:
32.- Ha
Admission intControl Slot Policy Explicit Memory Controls the user-defined memory slot size, in MB. Default:
100.- Ha
Admission boolControl Slot Policy Use Explicit Size Controls whether or not you wish to supply explicit values to CPU and memory slot sizes. The default is
false, which tells vSphere to gather a automatic average based on all powered-on virtual machines currently in the cluster.- Ha
Advanced map[string]stringOptions A key/value map that specifies advanced options for vSphere HA.
- Ha
Datastore stringApd Recovery Action Controls the action to take on virtual machines if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
noneorreset. Default:none. *- Ha
Datastore stringApd Response Controls the action to take on virtual machines when the cluster has detected loss to all paths to a relevant datastore. Can be one of
disabled,warning,restartConservative, orrestartAggressive. Default:disabled. *- Ha
Datastore intApd Response Delay Controls the delay in minutes to wait after an APD timeout event to execute the response action defined in
ha_datastore_apd_response. Default:3minutes. *- Ha
Datastore stringPdl Response Controls the action to take on virtual machines when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
disabled,warning, orrestartAggressive. Default:disabled. *- Ha
Enabled bool Enable vSphere HA for this cluster. Default:
false.- Ha
Heartbeat []stringDatastore Ids The list of managed object IDs for preferred datastores to use for HA heartbeating. This setting is only useful when
ha_heartbeat_datastore_policyis set to eitheruserSelectedDsorallFeasibleDsWithUserPreference.- Ha
Heartbeat stringDatastore Policy The selection policy for HA heartbeat datastores. Can be one of
allFeasibleDs,userSelectedDs, orallFeasibleDsWithUserPreference. Default:allFeasibleDsWithUserPreference.- Ha
Host stringIsolation Response The action to take on virtual machines when a host has detected that it has been isolated from the rest of the cluster. Can be one of
none,powerOff, orshutdown. Default:none.- Ha
Host stringMonitoring Global setting that controls whether vSphere HA remediates virtual machines on host failure. Can be one of
enabledordisabled. Default:enabled.- Ha
Vm stringComponent Protection Controls vSphere VM component protection for virtual machines in this cluster. Can be one of
enabledordisabled. Default:enabled. *- Ha
Vm stringDependency Restart Condition The condition used to determine whether or not virtual machines in a certain restart priority class are online, allowing HA to move on to restarting virtual machines on the next priority. Can be one of
none,poweredOn,guestHbStatusGreen, orappHbStatusGreen. The default isnone, which means that a virtual machine is considered ready immediately after a host is found to start it on. *- Ha
Vm intFailure Interval If a heartbeat from a virtual machine is not received within this configured interval, the virtual machine is marked as failed. The value is in seconds. Default:
30.- Ha
Vm intMaximum Failure Window The length of the reset window in which
ha_vm_maximum_resetscan operate. When this window expires, no more resets are attempted regardless of the setting configured inha_vm_maximum_resets.-1means no window, meaning an unlimited reset time is allotted. The value is specified in seconds. Default:-1(no window).- Ha
Vm intMaximum Resets The maximum number of resets that HA will perform to a virtual machine when responding to a failure event. Default:
3- Ha
Vm intMinimum Uptime The time, in seconds, that HA waits after powering on a virtual machine before monitoring for heartbeats. Default:
120(2 minutes).- Ha
Vm stringMonitoring The type of virtual machine monitoring to use when HA is enabled in the cluster. Can be one of
vmMonitoringDisabled,vmMonitoringOnly, orvmAndAppMonitoring. Default:vmMonitoringDisabled.- Ha
Vm intRestart Additional Delay Additional delay in seconds after ready condition is met. A VM is considered ready at this point. Default:
0(no delay). *- Ha
Vm stringRestart Priority The default restart priority for affected virtual machines when vSphere detects a host failure. Can be one of
lowest,low,medium,high, orhighest. Default:medium.- Ha
Vm intRestart Timeout The maximum time, in seconds, that vSphere HA will wait for virtual machines in one priority to be ready before proceeding with the next priority. Default:
600(10 minutes). *- Host
Cluster intExit Timeout The timeout for each host maintenance mode operation when removing hosts from a cluster. The value is specified in seconds. Default:
3600(1 hour).- Host
Managed bool Can be set to
trueif compute cluster membership will be managed through thehostresource rather than thecompute_clusterresource. Conflicts with:host_system_ids. >>>>>>> v1.18.3- Host
System []stringIds The [managed object IDs][docs-about-morefs] of the hosts to put in the cluster. Conflicts with:
host_managed.- Name string
The name of the cluster.
- Proactive
Ha stringAutomation Level Determines how the host quarantine, maintenance mode, or virtual machine migration recommendations made by proactive HA are to be handled. Can be one of
AutomatedorManual. Default:Manual. *- Proactive
Ha boolEnabled Enables Proactive HA. Default:
false. *- Proactive
Ha stringModerate Remediation The configured remediation for moderately degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toMaintenanceModewhenproactive_ha_severe_remediationis set toQuarantineMode. Default:QuarantineMode. *- Proactive
Ha []stringProvider Ids The list of IDs for health update providers configured for this cluster. *
- Proactive
Ha stringSevere Remediation The configured remediation for severely degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toQuarantineModewhenproactive_ha_moderate_remediationis set toMaintenanceMode. Default:QuarantineMode. *- []string
The IDs of any tags to attach to this resource.
- datacenter
Id string The managed object ID of the datacenter to create the cluster in. Forces a new resource if changed.
- custom
Attributes {[key: string]: string} A map of custom attribute ids to attribute value strings to set for the datastore cluster.
- dpm
Automation stringLevel The automation level for host power operations in this cluster. Can be one of
manualorautomated. Default:manual.- dpm
Enabled boolean Enable DPM support for DRS in this cluster. Requires
drs_enabledto betruein order to be effective. Default:false.- dpm
Threshold number A value between
1and5indicating the threshold of load within the cluster that influences host power operations. This affects both power on and power off operations - a lower setting will tolerate more of a surplus/deficit than a higher setting. Default:3.- drs
Advanced {[key: string]: string}Options A key/value map that specifies advanced options for DRS and DPM.
- drs
Automation stringLevel The default automation level for all virtual machines in this cluster. Can be one of
manual,partiallyAutomated, orfullyAutomated. Default:manual.- drs
Enable booleanPredictive Drs When
true, enables DRS to use data from [vRealize Operations Manager][ref-vsphere-vro] to make proactive DRS recommendations. *- drs
Enable booleanVm Overrides Allow individual DRS overrides to be set for virtual machines in the cluster. Default:
true.- drs
Enabled boolean Enable DRS for this cluster. Default:
false.- drs
Migration numberThreshold A value between
1and5indicating the threshold of imbalance tolerated between hosts. A lower setting will tolerate more imbalance while a higher setting will tolerate less. Default:3.- folder string
The relative path to a folder to put this cluster in. This is a path relative to the datacenter you are deploying the cluster to. Example: for the
dc1datacenter, and a providedfolderoffoo/bar, The provider will place a cluster namedcompute-cluster-testin a host folder located at/dc1/host/foo/bar, with the final inventory path being/dc1/host/foo/bar/datastore-cluster-test.- force
Evacuate booleanOn Destroy When destroying the resource, setting this to
truewill auto-remove any hosts that are currently a member of the cluster, as if they were removed by taking their entry out ofhost_system_ids(see below). This is an advanced option and should only be used for testing. Default:false.- ha
Admission string[]Control Failover Host System Ids Defines the managed object IDs of hosts to use as dedicated failover hosts. These hosts are kept as available as possible - admission control will block access to the host, and DRS will ignore the host when making recommendations.
- ha
Admission numberControl Host Failure Tolerance The maximum number of failed hosts that admission control tolerates when making decisions on whether to permit virtual machine operations. The maximum is one less than the number of hosts in the cluster. Default:
1. *- ha
Admission numberControl Performance Tolerance The percentage of resource reduction that a cluster of virtual machines can tolerate in case of a failover. A value of 0 produces warnings only, whereas a value of 100 disables the setting. Default:
100(disabled).- ha
Admission stringControl Policy The type of admission control policy to use with vSphere HA. Can be one of
resourcePercentage,slotPolicy,failoverHosts, ordisabled. Default:resourcePercentage.- ha
Admission booleanControl Resource Percentage Auto Compute Automatically determine available resource percentages by subtracting the average number of host resources represented by the
ha_admission_control_host_failure_tolerancesetting from the total amount of resources in the cluster. Disable to supply user-defined values. Default:true. *- ha
Admission numberControl Resource Percentage Cpu Controls the user-defined percentage of CPU resources in the cluster to reserve for failover. Default:
100.- ha
Admission numberControl Resource Percentage Memory Controls the user-defined percentage of memory resources in the cluster to reserve for failover. Default:
100.- ha
Admission numberControl Slot Policy Explicit Cpu Controls the user-defined CPU slot size, in MHz. Default:
32.- ha
Admission numberControl Slot Policy Explicit Memory Controls the user-defined memory slot size, in MB. Default:
100.- ha
Admission booleanControl Slot Policy Use Explicit Size Controls whether or not you wish to supply explicit values to CPU and memory slot sizes. The default is
false, which tells vSphere to gather a automatic average based on all powered-on virtual machines currently in the cluster.- ha
Advanced {[key: string]: string}Options A key/value map that specifies advanced options for vSphere HA.
- ha
Datastore stringApd Recovery Action Controls the action to take on virtual machines if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
noneorreset. Default:none. *- ha
Datastore stringApd Response Controls the action to take on virtual machines when the cluster has detected loss to all paths to a relevant datastore. Can be one of
disabled,warning,restartConservative, orrestartAggressive. Default:disabled. *- ha
Datastore numberApd Response Delay Controls the delay in minutes to wait after an APD timeout event to execute the response action defined in
ha_datastore_apd_response. Default:3minutes. *- ha
Datastore stringPdl Response Controls the action to take on virtual machines when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
disabled,warning, orrestartAggressive. Default:disabled. *- ha
Enabled boolean Enable vSphere HA for this cluster. Default:
false.- ha
Heartbeat string[]Datastore Ids The list of managed object IDs for preferred datastores to use for HA heartbeating. This setting is only useful when
ha_heartbeat_datastore_policyis set to eitheruserSelectedDsorallFeasibleDsWithUserPreference.- ha
Heartbeat stringDatastore Policy The selection policy for HA heartbeat datastores. Can be one of
allFeasibleDs,userSelectedDs, orallFeasibleDsWithUserPreference. Default:allFeasibleDsWithUserPreference.- ha
Host stringIsolation Response The action to take on virtual machines when a host has detected that it has been isolated from the rest of the cluster. Can be one of
none,powerOff, orshutdown. Default:none.- ha
Host stringMonitoring Global setting that controls whether vSphere HA remediates virtual machines on host failure. Can be one of
enabledordisabled. Default:enabled.- ha
Vm stringComponent Protection Controls vSphere VM component protection for virtual machines in this cluster. Can be one of
enabledordisabled. Default:enabled. *- ha
Vm stringDependency Restart Condition The condition used to determine whether or not virtual machines in a certain restart priority class are online, allowing HA to move on to restarting virtual machines on the next priority. Can be one of
none,poweredOn,guestHbStatusGreen, orappHbStatusGreen. The default isnone, which means that a virtual machine is considered ready immediately after a host is found to start it on. *- ha
Vm numberFailure Interval If a heartbeat from a virtual machine is not received within this configured interval, the virtual machine is marked as failed. The value is in seconds. Default:
30.- ha
Vm numberMaximum Failure Window The length of the reset window in which
ha_vm_maximum_resetscan operate. When this window expires, no more resets are attempted regardless of the setting configured inha_vm_maximum_resets.-1means no window, meaning an unlimited reset time is allotted. The value is specified in seconds. Default:-1(no window).- ha
Vm numberMaximum Resets The maximum number of resets that HA will perform to a virtual machine when responding to a failure event. Default:
3- ha
Vm numberMinimum Uptime The time, in seconds, that HA waits after powering on a virtual machine before monitoring for heartbeats. Default:
120(2 minutes).- ha
Vm stringMonitoring The type of virtual machine monitoring to use when HA is enabled in the cluster. Can be one of
vmMonitoringDisabled,vmMonitoringOnly, orvmAndAppMonitoring. Default:vmMonitoringDisabled.- ha
Vm numberRestart Additional Delay Additional delay in seconds after ready condition is met. A VM is considered ready at this point. Default:
0(no delay). *- ha
Vm stringRestart Priority The default restart priority for affected virtual machines when vSphere detects a host failure. Can be one of
lowest,low,medium,high, orhighest. Default:medium.- ha
Vm numberRestart Timeout The maximum time, in seconds, that vSphere HA will wait for virtual machines in one priority to be ready before proceeding with the next priority. Default:
600(10 minutes). *- host
Cluster numberExit Timeout The timeout for each host maintenance mode operation when removing hosts from a cluster. The value is specified in seconds. Default:
3600(1 hour).- host
Managed boolean Can be set to
trueif compute cluster membership will be managed through thehostresource rather than thecompute_clusterresource. Conflicts with:host_system_ids. >>>>>>> v1.18.3- host
System string[]Ids The [managed object IDs][docs-about-morefs] of the hosts to put in the cluster. Conflicts with:
host_managed.- name string
The name of the cluster.
- proactive
Ha stringAutomation Level Determines how the host quarantine, maintenance mode, or virtual machine migration recommendations made by proactive HA are to be handled. Can be one of
AutomatedorManual. Default:Manual. *- proactive
Ha booleanEnabled Enables Proactive HA. Default:
false. *- proactive
Ha stringModerate Remediation The configured remediation for moderately degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toMaintenanceModewhenproactive_ha_severe_remediationis set toQuarantineMode. Default:QuarantineMode. *- proactive
Ha string[]Provider Ids The list of IDs for health update providers configured for this cluster. *
- proactive
Ha stringSevere Remediation The configured remediation for severely degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toQuarantineModewhenproactive_ha_moderate_remediationis set toMaintenanceMode. Default:QuarantineMode. *- string[]
The IDs of any tags to attach to this resource.
- datacenter_
id str The managed object ID of the datacenter to create the cluster in. Forces a new resource if changed.
- custom_
attributes Dict[str, str] A map of custom attribute ids to attribute value strings to set for the datastore cluster.
- dpm_
automation_ strlevel The automation level for host power operations in this cluster. Can be one of
manualorautomated. Default:manual.- dpm_
enabled bool Enable DPM support for DRS in this cluster. Requires
drs_enabledto betruein order to be effective. Default:false.- dpm_
threshold float A value between
1and5indicating the threshold of load within the cluster that influences host power operations. This affects both power on and power off operations - a lower setting will tolerate more of a surplus/deficit than a higher setting. Default:3.- drs_
advanced_ Dict[str, str]options A key/value map that specifies advanced options for DRS and DPM.
- drs_
automation_ strlevel The default automation level for all virtual machines in this cluster. Can be one of
manual,partiallyAutomated, orfullyAutomated. Default:manual.- drs_
enable_ boolpredictive_ drs When
true, enables DRS to use data from [vRealize Operations Manager][ref-vsphere-vro] to make proactive DRS recommendations. *- drs_
enable_ boolvm_ overrides Allow individual DRS overrides to be set for virtual machines in the cluster. Default:
true.- drs_
enabled bool Enable DRS for this cluster. Default:
false.- drs_
migration_ floatthreshold A value between
1and5indicating the threshold of imbalance tolerated between hosts. A lower setting will tolerate more imbalance while a higher setting will tolerate less. Default:3.- folder str
The relative path to a folder to put this cluster in. This is a path relative to the datacenter you are deploying the cluster to. Example: for the
dc1datacenter, and a providedfolderoffoo/bar, The provider will place a cluster namedcompute-cluster-testin a host folder located at/dc1/host/foo/bar, with the final inventory path being/dc1/host/foo/bar/datastore-cluster-test.- force_
evacuate_ boolon_ destroy When destroying the resource, setting this to
truewill auto-remove any hosts that are currently a member of the cluster, as if they were removed by taking their entry out ofhost_system_ids(see below). This is an advanced option and should only be used for testing. Default:false.- ha_
admission_ List[str]control_ failover_ host_ system_ ids Defines the managed object IDs of hosts to use as dedicated failover hosts. These hosts are kept as available as possible - admission control will block access to the host, and DRS will ignore the host when making recommendations.
- ha_
admission_ floatcontrol_ host_ failure_ tolerance The maximum number of failed hosts that admission control tolerates when making decisions on whether to permit virtual machine operations. The maximum is one less than the number of hosts in the cluster. Default:
1. *- ha_
admission_ floatcontrol_ performance_ tolerance The percentage of resource reduction that a cluster of virtual machines can tolerate in case of a failover. A value of 0 produces warnings only, whereas a value of 100 disables the setting. Default:
100(disabled).- ha_
admission_ strcontrol_ policy The type of admission control policy to use with vSphere HA. Can be one of
resourcePercentage,slotPolicy,failoverHosts, ordisabled. Default:resourcePercentage.- ha_
admission_ boolcontrol_ resource_ percentage_ auto_ compute Automatically determine available resource percentages by subtracting the average number of host resources represented by the
ha_admission_control_host_failure_tolerancesetting from the total amount of resources in the cluster. Disable to supply user-defined values. Default:true. *- ha_
admission_ floatcontrol_ resource_ percentage_ cpu Controls the user-defined percentage of CPU resources in the cluster to reserve for failover. Default:
100.- ha_
admission_ floatcontrol_ resource_ percentage_ memory Controls the user-defined percentage of memory resources in the cluster to reserve for failover. Default:
100.- ha_
admission_ floatcontrol_ slot_ policy_ explicit_ cpu Controls the user-defined CPU slot size, in MHz. Default:
32.- ha_
admission_ floatcontrol_ slot_ policy_ explicit_ memory Controls the user-defined memory slot size, in MB. Default:
100.- ha_
admission_ boolcontrol_ slot_ policy_ use_ explicit_ size Controls whether or not you wish to supply explicit values to CPU and memory slot sizes. The default is
false, which tells vSphere to gather a automatic average based on all powered-on virtual machines currently in the cluster.- ha_
advanced_ Dict[str, str]options A key/value map that specifies advanced options for vSphere HA.
- ha_
datastore_ strapd_ recovery_ action Controls the action to take on virtual machines if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
noneorreset. Default:none. *- ha_
datastore_ strapd_ response Controls the action to take on virtual machines when the cluster has detected loss to all paths to a relevant datastore. Can be one of
disabled,warning,restartConservative, orrestartAggressive. Default:disabled. *- ha_
datastore_ floatapd_ response_ delay Controls the delay in minutes to wait after an APD timeout event to execute the response action defined in
ha_datastore_apd_response. Default:3minutes. *- ha_
datastore_ strpdl_ response Controls the action to take on virtual machines when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
disabled,warning, orrestartAggressive. Default:disabled. *- ha_
enabled bool Enable vSphere HA for this cluster. Default:
false.- ha_
heartbeat_ List[str]datastore_ ids The list of managed object IDs for preferred datastores to use for HA heartbeating. This setting is only useful when
ha_heartbeat_datastore_policyis set to eitheruserSelectedDsorallFeasibleDsWithUserPreference.- ha_
heartbeat_ strdatastore_ policy The selection policy for HA heartbeat datastores. Can be one of
allFeasibleDs,userSelectedDs, orallFeasibleDsWithUserPreference. Default:allFeasibleDsWithUserPreference.- ha_
host_ strisolation_ response The action to take on virtual machines when a host has detected that it has been isolated from the rest of the cluster. Can be one of
none,powerOff, orshutdown. Default:none.- ha_
host_ strmonitoring Global setting that controls whether vSphere HA remediates virtual machines on host failure. Can be one of
enabledordisabled. Default:enabled.- ha_
vm_ strcomponent_ protection Controls vSphere VM component protection for virtual machines in this cluster. Can be one of
enabledordisabled. Default:enabled. *- ha_
vm_ strdependency_ restart_ condition The condition used to determine whether or not virtual machines in a certain restart priority class are online, allowing HA to move on to restarting virtual machines on the next priority. Can be one of
none,poweredOn,guestHbStatusGreen, orappHbStatusGreen. The default isnone, which means that a virtual machine is considered ready immediately after a host is found to start it on. *- ha_
vm_ floatfailure_ interval If a heartbeat from a virtual machine is not received within this configured interval, the virtual machine is marked as failed. The value is in seconds. Default:
30.- ha_
vm_ floatmaximum_ failure_ window The length of the reset window in which
ha_vm_maximum_resetscan operate. When this window expires, no more resets are attempted regardless of the setting configured inha_vm_maximum_resets.-1means no window, meaning an unlimited reset time is allotted. The value is specified in seconds. Default:-1(no window).- ha_
vm_ floatmaximum_ resets The maximum number of resets that HA will perform to a virtual machine when responding to a failure event. Default:
3- ha_
vm_ floatminimum_ uptime The time, in seconds, that HA waits after powering on a virtual machine before monitoring for heartbeats. Default:
120(2 minutes).- ha_
vm_ strmonitoring The type of virtual machine monitoring to use when HA is enabled in the cluster. Can be one of
vmMonitoringDisabled,vmMonitoringOnly, orvmAndAppMonitoring. Default:vmMonitoringDisabled.- ha_
vm_ floatrestart_ additional_ delay Additional delay in seconds after ready condition is met. A VM is considered ready at this point. Default:
0(no delay). *- ha_
vm_ strrestart_ priority The default restart priority for affected virtual machines when vSphere detects a host failure. Can be one of
lowest,low,medium,high, orhighest. Default:medium.- ha_
vm_ floatrestart_ timeout The maximum time, in seconds, that vSphere HA will wait for virtual machines in one priority to be ready before proceeding with the next priority. Default:
600(10 minutes). *- host_
cluster_ floatexit_ timeout The timeout for each host maintenance mode operation when removing hosts from a cluster. The value is specified in seconds. Default:
3600(1 hour).- host_
managed bool Can be set to
trueif compute cluster membership will be managed through thehostresource rather than thecompute_clusterresource. Conflicts with:host_system_ids. >>>>>>> v1.18.3- host_
system_ List[str]ids The [managed object IDs][docs-about-morefs] of the hosts to put in the cluster. Conflicts with:
host_managed.- name str
The name of the cluster.
- proactive_
ha_ strautomation_ level Determines how the host quarantine, maintenance mode, or virtual machine migration recommendations made by proactive HA are to be handled. Can be one of
AutomatedorManual. Default:Manual. *- proactive_
ha_ boolenabled Enables Proactive HA. Default:
false. *- proactive_
ha_ strmoderate_ remediation The configured remediation for moderately degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toMaintenanceModewhenproactive_ha_severe_remediationis set toQuarantineMode. Default:QuarantineMode. *- proactive_
ha_ List[str]provider_ ids The list of IDs for health update providers configured for this cluster. *
- proactive_
ha_ strsevere_ remediation The configured remediation for severely degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toQuarantineModewhenproactive_ha_moderate_remediationis set toMaintenanceMode. Default:QuarantineMode. *- List[str]
The IDs of any tags to attach to this resource.
Outputs
All input properties are implicitly available as output properties. Additionally, the ComputeCluster resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- Resource
Pool stringId The managed object ID of the cluster’s root resource pool.
- Id string
- The provider-assigned unique ID for this managed resource.
- Resource
Pool stringId The managed object ID of the cluster’s root resource pool.
- id string
- The provider-assigned unique ID for this managed resource.
- resource
Pool stringId The managed object ID of the cluster’s root resource pool.
- id str
- The provider-assigned unique ID for this managed resource.
- resource_
pool_ strid The managed object ID of the cluster’s root resource pool.
Look up an Existing ComputeCluster Resource
Get an existing ComputeCluster resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: ComputeClusterState, opts?: CustomResourceOptions): ComputeClusterstatic get(resource_name, id, opts=None, custom_attributes=None, datacenter_id=None, dpm_automation_level=None, dpm_enabled=None, dpm_threshold=None, drs_advanced_options=None, drs_automation_level=None, drs_enable_predictive_drs=None, drs_enable_vm_overrides=None, drs_enabled=None, drs_migration_threshold=None, folder=None, force_evacuate_on_destroy=None, ha_admission_control_failover_host_system_ids=None, ha_admission_control_host_failure_tolerance=None, ha_admission_control_performance_tolerance=None, ha_admission_control_policy=None, ha_admission_control_resource_percentage_auto_compute=None, ha_admission_control_resource_percentage_cpu=None, ha_admission_control_resource_percentage_memory=None, ha_admission_control_slot_policy_explicit_cpu=None, ha_admission_control_slot_policy_explicit_memory=None, ha_admission_control_slot_policy_use_explicit_size=None, ha_advanced_options=None, ha_datastore_apd_recovery_action=None, ha_datastore_apd_response=None, ha_datastore_apd_response_delay=None, ha_datastore_pdl_response=None, ha_enabled=None, ha_heartbeat_datastore_ids=None, ha_heartbeat_datastore_policy=None, ha_host_isolation_response=None, ha_host_monitoring=None, ha_vm_component_protection=None, ha_vm_dependency_restart_condition=None, ha_vm_failure_interval=None, ha_vm_maximum_failure_window=None, ha_vm_maximum_resets=None, ha_vm_minimum_uptime=None, ha_vm_monitoring=None, ha_vm_restart_additional_delay=None, ha_vm_restart_priority=None, ha_vm_restart_timeout=None, host_cluster_exit_timeout=None, host_managed=None, host_system_ids=None, name=None, proactive_ha_automation_level=None, proactive_ha_enabled=None, proactive_ha_moderate_remediation=None, proactive_ha_provider_ids=None, proactive_ha_severe_remediation=None, resource_pool_id=None, tags=None, __props__=None);func GetComputeCluster(ctx *Context, name string, id IDInput, state *ComputeClusterState, opts ...ResourceOption) (*ComputeCluster, error)public static ComputeCluster Get(string name, Input<string> id, ComputeClusterState? state, CustomResourceOptions? opts = null)- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
The following state arguments are supported:
- Custom
Attributes Dictionary<string, string> A map of custom attribute ids to attribute value strings to set for the datastore cluster.
- Datacenter
Id string The managed object ID of the datacenter to create the cluster in. Forces a new resource if changed.
- Dpm
Automation stringLevel The automation level for host power operations in this cluster. Can be one of
manualorautomated. Default:manual.- Dpm
Enabled bool Enable DPM support for DRS in this cluster. Requires
drs_enabledto betruein order to be effective. Default:false.- Dpm
Threshold int A value between
1and5indicating the threshold of load within the cluster that influences host power operations. This affects both power on and power off operations - a lower setting will tolerate more of a surplus/deficit than a higher setting. Default:3.- Drs
Advanced Dictionary<string, string>Options A key/value map that specifies advanced options for DRS and DPM.
- Drs
Automation stringLevel The default automation level for all virtual machines in this cluster. Can be one of
manual,partiallyAutomated, orfullyAutomated. Default:manual.- Drs
Enable boolPredictive Drs When
true, enables DRS to use data from [vRealize Operations Manager][ref-vsphere-vro] to make proactive DRS recommendations. *- Drs
Enable boolVm Overrides Allow individual DRS overrides to be set for virtual machines in the cluster. Default:
true.- Drs
Enabled bool Enable DRS for this cluster. Default:
false.- Drs
Migration intThreshold A value between
1and5indicating the threshold of imbalance tolerated between hosts. A lower setting will tolerate more imbalance while a higher setting will tolerate less. Default:3.- Folder string
The relative path to a folder to put this cluster in. This is a path relative to the datacenter you are deploying the cluster to. Example: for the
dc1datacenter, and a providedfolderoffoo/bar, The provider will place a cluster namedcompute-cluster-testin a host folder located at/dc1/host/foo/bar, with the final inventory path being/dc1/host/foo/bar/datastore-cluster-test.- Force
Evacuate boolOn Destroy When destroying the resource, setting this to
truewill auto-remove any hosts that are currently a member of the cluster, as if they were removed by taking their entry out ofhost_system_ids(see below). This is an advanced option and should only be used for testing. Default:false.- Ha
Admission List<string>Control Failover Host System Ids Defines the managed object IDs of hosts to use as dedicated failover hosts. These hosts are kept as available as possible - admission control will block access to the host, and DRS will ignore the host when making recommendations.
- Ha
Admission intControl Host Failure Tolerance The maximum number of failed hosts that admission control tolerates when making decisions on whether to permit virtual machine operations. The maximum is one less than the number of hosts in the cluster. Default:
1. *- Ha
Admission intControl Performance Tolerance The percentage of resource reduction that a cluster of virtual machines can tolerate in case of a failover. A value of 0 produces warnings only, whereas a value of 100 disables the setting. Default:
100(disabled).- Ha
Admission stringControl Policy The type of admission control policy to use with vSphere HA. Can be one of
resourcePercentage,slotPolicy,failoverHosts, ordisabled. Default:resourcePercentage.- Ha
Admission boolControl Resource Percentage Auto Compute Automatically determine available resource percentages by subtracting the average number of host resources represented by the
ha_admission_control_host_failure_tolerancesetting from the total amount of resources in the cluster. Disable to supply user-defined values. Default:true. *- Ha
Admission intControl Resource Percentage Cpu Controls the user-defined percentage of CPU resources in the cluster to reserve for failover. Default:
100.- Ha
Admission intControl Resource Percentage Memory Controls the user-defined percentage of memory resources in the cluster to reserve for failover. Default:
100.- Ha
Admission intControl Slot Policy Explicit Cpu Controls the user-defined CPU slot size, in MHz. Default:
32.- Ha
Admission intControl Slot Policy Explicit Memory Controls the user-defined memory slot size, in MB. Default:
100.- Ha
Admission boolControl Slot Policy Use Explicit Size Controls whether or not you wish to supply explicit values to CPU and memory slot sizes. The default is
false, which tells vSphere to gather a automatic average based on all powered-on virtual machines currently in the cluster.- Ha
Advanced Dictionary<string, string>Options A key/value map that specifies advanced options for vSphere HA.
- Ha
Datastore stringApd Recovery Action Controls the action to take on virtual machines if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
noneorreset. Default:none. *- Ha
Datastore stringApd Response Controls the action to take on virtual machines when the cluster has detected loss to all paths to a relevant datastore. Can be one of
disabled,warning,restartConservative, orrestartAggressive. Default:disabled. *- Ha
Datastore intApd Response Delay Controls the delay in minutes to wait after an APD timeout event to execute the response action defined in
ha_datastore_apd_response. Default:3minutes. *- Ha
Datastore stringPdl Response Controls the action to take on virtual machines when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
disabled,warning, orrestartAggressive. Default:disabled. *- Ha
Enabled bool Enable vSphere HA for this cluster. Default:
false.- Ha
Heartbeat List<string>Datastore Ids The list of managed object IDs for preferred datastores to use for HA heartbeating. This setting is only useful when
ha_heartbeat_datastore_policyis set to eitheruserSelectedDsorallFeasibleDsWithUserPreference.- Ha
Heartbeat stringDatastore Policy The selection policy for HA heartbeat datastores. Can be one of
allFeasibleDs,userSelectedDs, orallFeasibleDsWithUserPreference. Default:allFeasibleDsWithUserPreference.- Ha
Host stringIsolation Response The action to take on virtual machines when a host has detected that it has been isolated from the rest of the cluster. Can be one of
none,powerOff, orshutdown. Default:none.- Ha
Host stringMonitoring Global setting that controls whether vSphere HA remediates virtual machines on host failure. Can be one of
enabledordisabled. Default:enabled.- Ha
Vm stringComponent Protection Controls vSphere VM component protection for virtual machines in this cluster. Can be one of
enabledordisabled. Default:enabled. *- Ha
Vm stringDependency Restart Condition The condition used to determine whether or not virtual machines in a certain restart priority class are online, allowing HA to move on to restarting virtual machines on the next priority. Can be one of
none,poweredOn,guestHbStatusGreen, orappHbStatusGreen. The default isnone, which means that a virtual machine is considered ready immediately after a host is found to start it on. *- Ha
Vm intFailure Interval If a heartbeat from a virtual machine is not received within this configured interval, the virtual machine is marked as failed. The value is in seconds. Default:
30.- Ha
Vm intMaximum Failure Window The length of the reset window in which
ha_vm_maximum_resetscan operate. When this window expires, no more resets are attempted regardless of the setting configured inha_vm_maximum_resets.-1means no window, meaning an unlimited reset time is allotted. The value is specified in seconds. Default:-1(no window).- Ha
Vm intMaximum Resets The maximum number of resets that HA will perform to a virtual machine when responding to a failure event. Default:
3- Ha
Vm intMinimum Uptime The time, in seconds, that HA waits after powering on a virtual machine before monitoring for heartbeats. Default:
120(2 minutes).- Ha
Vm stringMonitoring The type of virtual machine monitoring to use when HA is enabled in the cluster. Can be one of
vmMonitoringDisabled,vmMonitoringOnly, orvmAndAppMonitoring. Default:vmMonitoringDisabled.- Ha
Vm intRestart Additional Delay Additional delay in seconds after ready condition is met. A VM is considered ready at this point. Default:
0(no delay). *- Ha
Vm stringRestart Priority The default restart priority for affected virtual machines when vSphere detects a host failure. Can be one of
lowest,low,medium,high, orhighest. Default:medium.- Ha
Vm intRestart Timeout The maximum time, in seconds, that vSphere HA will wait for virtual machines in one priority to be ready before proceeding with the next priority. Default:
600(10 minutes). *- Host
Cluster intExit Timeout The timeout for each host maintenance mode operation when removing hosts from a cluster. The value is specified in seconds. Default:
3600(1 hour).- Host
Managed bool Can be set to
trueif compute cluster membership will be managed through thehostresource rather than thecompute_clusterresource. Conflicts with:host_system_ids. >>>>>>> v1.18.3- Host
System List<string>Ids The [managed object IDs][docs-about-morefs] of the hosts to put in the cluster. Conflicts with:
host_managed.- Name string
The name of the cluster.
- Proactive
Ha stringAutomation Level Determines how the host quarantine, maintenance mode, or virtual machine migration recommendations made by proactive HA are to be handled. Can be one of
AutomatedorManual. Default:Manual. *- Proactive
Ha boolEnabled Enables Proactive HA. Default:
false. *- Proactive
Ha stringModerate Remediation The configured remediation for moderately degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toMaintenanceModewhenproactive_ha_severe_remediationis set toQuarantineMode. Default:QuarantineMode. *- Proactive
Ha List<string>Provider Ids The list of IDs for health update providers configured for this cluster. *
- Proactive
Ha stringSevere Remediation The configured remediation for severely degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toQuarantineModewhenproactive_ha_moderate_remediationis set toMaintenanceMode. Default:QuarantineMode. *- Resource
Pool stringId The managed object ID of the cluster’s root resource pool.
- List<string>
The IDs of any tags to attach to this resource.
- Custom
Attributes map[string]string A map of custom attribute ids to attribute value strings to set for the datastore cluster.
- Datacenter
Id string The managed object ID of the datacenter to create the cluster in. Forces a new resource if changed.
- Dpm
Automation stringLevel The automation level for host power operations in this cluster. Can be one of
manualorautomated. Default:manual.- Dpm
Enabled bool Enable DPM support for DRS in this cluster. Requires
drs_enabledto betruein order to be effective. Default:false.- Dpm
Threshold int A value between
1and5indicating the threshold of load within the cluster that influences host power operations. This affects both power on and power off operations - a lower setting will tolerate more of a surplus/deficit than a higher setting. Default:3.- Drs
Advanced map[string]stringOptions A key/value map that specifies advanced options for DRS and DPM.
- Drs
Automation stringLevel The default automation level for all virtual machines in this cluster. Can be one of
manual,partiallyAutomated, orfullyAutomated. Default:manual.- Drs
Enable boolPredictive Drs When
true, enables DRS to use data from [vRealize Operations Manager][ref-vsphere-vro] to make proactive DRS recommendations. *- Drs
Enable boolVm Overrides Allow individual DRS overrides to be set for virtual machines in the cluster. Default:
true.- Drs
Enabled bool Enable DRS for this cluster. Default:
false.- Drs
Migration intThreshold A value between
1and5indicating the threshold of imbalance tolerated between hosts. A lower setting will tolerate more imbalance while a higher setting will tolerate less. Default:3.- Folder string
The relative path to a folder to put this cluster in. This is a path relative to the datacenter you are deploying the cluster to. Example: for the
dc1datacenter, and a providedfolderoffoo/bar, The provider will place a cluster namedcompute-cluster-testin a host folder located at/dc1/host/foo/bar, with the final inventory path being/dc1/host/foo/bar/datastore-cluster-test.- Force
Evacuate boolOn Destroy When destroying the resource, setting this to
truewill auto-remove any hosts that are currently a member of the cluster, as if they were removed by taking their entry out ofhost_system_ids(see below). This is an advanced option and should only be used for testing. Default:false.- Ha
Admission []stringControl Failover Host System Ids Defines the managed object IDs of hosts to use as dedicated failover hosts. These hosts are kept as available as possible - admission control will block access to the host, and DRS will ignore the host when making recommendations.
- Ha
Admission intControl Host Failure Tolerance The maximum number of failed hosts that admission control tolerates when making decisions on whether to permit virtual machine operations. The maximum is one less than the number of hosts in the cluster. Default:
1. *- Ha
Admission intControl Performance Tolerance The percentage of resource reduction that a cluster of virtual machines can tolerate in case of a failover. A value of 0 produces warnings only, whereas a value of 100 disables the setting. Default:
100(disabled).- Ha
Admission stringControl Policy The type of admission control policy to use with vSphere HA. Can be one of
resourcePercentage,slotPolicy,failoverHosts, ordisabled. Default:resourcePercentage.- Ha
Admission boolControl Resource Percentage Auto Compute Automatically determine available resource percentages by subtracting the average number of host resources represented by the
ha_admission_control_host_failure_tolerancesetting from the total amount of resources in the cluster. Disable to supply user-defined values. Default:true. *- Ha
Admission intControl Resource Percentage Cpu Controls the user-defined percentage of CPU resources in the cluster to reserve for failover. Default:
100.- Ha
Admission intControl Resource Percentage Memory Controls the user-defined percentage of memory resources in the cluster to reserve for failover. Default:
100.- Ha
Admission intControl Slot Policy Explicit Cpu Controls the user-defined CPU slot size, in MHz. Default:
32.- Ha
Admission intControl Slot Policy Explicit Memory Controls the user-defined memory slot size, in MB. Default:
100.- Ha
Admission boolControl Slot Policy Use Explicit Size Controls whether or not you wish to supply explicit values to CPU and memory slot sizes. The default is
false, which tells vSphere to gather a automatic average based on all powered-on virtual machines currently in the cluster.- Ha
Advanced map[string]stringOptions A key/value map that specifies advanced options for vSphere HA.
- Ha
Datastore stringApd Recovery Action Controls the action to take on virtual machines if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
noneorreset. Default:none. *- Ha
Datastore stringApd Response Controls the action to take on virtual machines when the cluster has detected loss to all paths to a relevant datastore. Can be one of
disabled,warning,restartConservative, orrestartAggressive. Default:disabled. *- Ha
Datastore intApd Response Delay Controls the delay in minutes to wait after an APD timeout event to execute the response action defined in
ha_datastore_apd_response. Default:3minutes. *- Ha
Datastore stringPdl Response Controls the action to take on virtual machines when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
disabled,warning, orrestartAggressive. Default:disabled. *- Ha
Enabled bool Enable vSphere HA for this cluster. Default:
false.- Ha
Heartbeat []stringDatastore Ids The list of managed object IDs for preferred datastores to use for HA heartbeating. This setting is only useful when
ha_heartbeat_datastore_policyis set to eitheruserSelectedDsorallFeasibleDsWithUserPreference.- Ha
Heartbeat stringDatastore Policy The selection policy for HA heartbeat datastores. Can be one of
allFeasibleDs,userSelectedDs, orallFeasibleDsWithUserPreference. Default:allFeasibleDsWithUserPreference.- Ha
Host stringIsolation Response The action to take on virtual machines when a host has detected that it has been isolated from the rest of the cluster. Can be one of
none,powerOff, orshutdown. Default:none.- Ha
Host stringMonitoring Global setting that controls whether vSphere HA remediates virtual machines on host failure. Can be one of
enabledordisabled. Default:enabled.- Ha
Vm stringComponent Protection Controls vSphere VM component protection for virtual machines in this cluster. Can be one of
enabledordisabled. Default:enabled. *- Ha
Vm stringDependency Restart Condition The condition used to determine whether or not virtual machines in a certain restart priority class are online, allowing HA to move on to restarting virtual machines on the next priority. Can be one of
none,poweredOn,guestHbStatusGreen, orappHbStatusGreen. The default isnone, which means that a virtual machine is considered ready immediately after a host is found to start it on. *- Ha
Vm intFailure Interval If a heartbeat from a virtual machine is not received within this configured interval, the virtual machine is marked as failed. The value is in seconds. Default:
30.- Ha
Vm intMaximum Failure Window The length of the reset window in which
ha_vm_maximum_resetscan operate. When this window expires, no more resets are attempted regardless of the setting configured inha_vm_maximum_resets.-1means no window, meaning an unlimited reset time is allotted. The value is specified in seconds. Default:-1(no window).- Ha
Vm intMaximum Resets The maximum number of resets that HA will perform to a virtual machine when responding to a failure event. Default:
3- Ha
Vm intMinimum Uptime The time, in seconds, that HA waits after powering on a virtual machine before monitoring for heartbeats. Default:
120(2 minutes).- Ha
Vm stringMonitoring The type of virtual machine monitoring to use when HA is enabled in the cluster. Can be one of
vmMonitoringDisabled,vmMonitoringOnly, orvmAndAppMonitoring. Default:vmMonitoringDisabled.- Ha
Vm intRestart Additional Delay Additional delay in seconds after ready condition is met. A VM is considered ready at this point. Default:
0(no delay). *- Ha
Vm stringRestart Priority The default restart priority for affected virtual machines when vSphere detects a host failure. Can be one of
lowest,low,medium,high, orhighest. Default:medium.- Ha
Vm intRestart Timeout The maximum time, in seconds, that vSphere HA will wait for virtual machines in one priority to be ready before proceeding with the next priority. Default:
600(10 minutes). *- Host
Cluster intExit Timeout The timeout for each host maintenance mode operation when removing hosts from a cluster. The value is specified in seconds. Default:
3600(1 hour).- Host
Managed bool Can be set to
trueif compute cluster membership will be managed through thehostresource rather than thecompute_clusterresource. Conflicts with:host_system_ids. >>>>>>> v1.18.3- Host
System []stringIds The [managed object IDs][docs-about-morefs] of the hosts to put in the cluster. Conflicts with:
host_managed.- Name string
The name of the cluster.
- Proactive
Ha stringAutomation Level Determines how the host quarantine, maintenance mode, or virtual machine migration recommendations made by proactive HA are to be handled. Can be one of
AutomatedorManual. Default:Manual. *- Proactive
Ha boolEnabled Enables Proactive HA. Default:
false. *- Proactive
Ha stringModerate Remediation The configured remediation for moderately degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toMaintenanceModewhenproactive_ha_severe_remediationis set toQuarantineMode. Default:QuarantineMode. *- Proactive
Ha []stringProvider Ids The list of IDs for health update providers configured for this cluster. *
- Proactive
Ha stringSevere Remediation The configured remediation for severely degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toQuarantineModewhenproactive_ha_moderate_remediationis set toMaintenanceMode. Default:QuarantineMode. *- Resource
Pool stringId The managed object ID of the cluster’s root resource pool.
- []string
The IDs of any tags to attach to this resource.
- custom
Attributes {[key: string]: string} A map of custom attribute ids to attribute value strings to set for the datastore cluster.
- datacenter
Id string The managed object ID of the datacenter to create the cluster in. Forces a new resource if changed.
- dpm
Automation stringLevel The automation level for host power operations in this cluster. Can be one of
manualorautomated. Default:manual.- dpm
Enabled boolean Enable DPM support for DRS in this cluster. Requires
drs_enabledto betruein order to be effective. Default:false.- dpm
Threshold number A value between
1and5indicating the threshold of load within the cluster that influences host power operations. This affects both power on and power off operations - a lower setting will tolerate more of a surplus/deficit than a higher setting. Default:3.- drs
Advanced {[key: string]: string}Options A key/value map that specifies advanced options for DRS and DPM.
- drs
Automation stringLevel The default automation level for all virtual machines in this cluster. Can be one of
manual,partiallyAutomated, orfullyAutomated. Default:manual.- drs
Enable booleanPredictive Drs When
true, enables DRS to use data from [vRealize Operations Manager][ref-vsphere-vro] to make proactive DRS recommendations. *- drs
Enable booleanVm Overrides Allow individual DRS overrides to be set for virtual machines in the cluster. Default:
true.- drs
Enabled boolean Enable DRS for this cluster. Default:
false.- drs
Migration numberThreshold A value between
1and5indicating the threshold of imbalance tolerated between hosts. A lower setting will tolerate more imbalance while a higher setting will tolerate less. Default:3.- folder string
The relative path to a folder to put this cluster in. This is a path relative to the datacenter you are deploying the cluster to. Example: for the
dc1datacenter, and a providedfolderoffoo/bar, The provider will place a cluster namedcompute-cluster-testin a host folder located at/dc1/host/foo/bar, with the final inventory path being/dc1/host/foo/bar/datastore-cluster-test.- force
Evacuate booleanOn Destroy When destroying the resource, setting this to
truewill auto-remove any hosts that are currently a member of the cluster, as if they were removed by taking their entry out ofhost_system_ids(see below). This is an advanced option and should only be used for testing. Default:false.- ha
Admission string[]Control Failover Host System Ids Defines the managed object IDs of hosts to use as dedicated failover hosts. These hosts are kept as available as possible - admission control will block access to the host, and DRS will ignore the host when making recommendations.
- ha
Admission numberControl Host Failure Tolerance The maximum number of failed hosts that admission control tolerates when making decisions on whether to permit virtual machine operations. The maximum is one less than the number of hosts in the cluster. Default:
1. *- ha
Admission numberControl Performance Tolerance The percentage of resource reduction that a cluster of virtual machines can tolerate in case of a failover. A value of 0 produces warnings only, whereas a value of 100 disables the setting. Default:
100(disabled).- ha
Admission stringControl Policy The type of admission control policy to use with vSphere HA. Can be one of
resourcePercentage,slotPolicy,failoverHosts, ordisabled. Default:resourcePercentage.- ha
Admission booleanControl Resource Percentage Auto Compute Automatically determine available resource percentages by subtracting the average number of host resources represented by the
ha_admission_control_host_failure_tolerancesetting from the total amount of resources in the cluster. Disable to supply user-defined values. Default:true. *- ha
Admission numberControl Resource Percentage Cpu Controls the user-defined percentage of CPU resources in the cluster to reserve for failover. Default:
100.- ha
Admission numberControl Resource Percentage Memory Controls the user-defined percentage of memory resources in the cluster to reserve for failover. Default:
100.- ha
Admission numberControl Slot Policy Explicit Cpu Controls the user-defined CPU slot size, in MHz. Default:
32.- ha
Admission numberControl Slot Policy Explicit Memory Controls the user-defined memory slot size, in MB. Default:
100.- ha
Admission booleanControl Slot Policy Use Explicit Size Controls whether or not you wish to supply explicit values to CPU and memory slot sizes. The default is
false, which tells vSphere to gather a automatic average based on all powered-on virtual machines currently in the cluster.- ha
Advanced {[key: string]: string}Options A key/value map that specifies advanced options for vSphere HA.
- ha
Datastore stringApd Recovery Action Controls the action to take on virtual machines if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
noneorreset. Default:none. *- ha
Datastore stringApd Response Controls the action to take on virtual machines when the cluster has detected loss to all paths to a relevant datastore. Can be one of
disabled,warning,restartConservative, orrestartAggressive. Default:disabled. *- ha
Datastore numberApd Response Delay Controls the delay in minutes to wait after an APD timeout event to execute the response action defined in
ha_datastore_apd_response. Default:3minutes. *- ha
Datastore stringPdl Response Controls the action to take on virtual machines when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
disabled,warning, orrestartAggressive. Default:disabled. *- ha
Enabled boolean Enable vSphere HA for this cluster. Default:
false.- ha
Heartbeat string[]Datastore Ids The list of managed object IDs for preferred datastores to use for HA heartbeating. This setting is only useful when
ha_heartbeat_datastore_policyis set to eitheruserSelectedDsorallFeasibleDsWithUserPreference.- ha
Heartbeat stringDatastore Policy The selection policy for HA heartbeat datastores. Can be one of
allFeasibleDs,userSelectedDs, orallFeasibleDsWithUserPreference. Default:allFeasibleDsWithUserPreference.- ha
Host stringIsolation Response The action to take on virtual machines when a host has detected that it has been isolated from the rest of the cluster. Can be one of
none,powerOff, orshutdown. Default:none.- ha
Host stringMonitoring Global setting that controls whether vSphere HA remediates virtual machines on host failure. Can be one of
enabledordisabled. Default:enabled.- ha
Vm stringComponent Protection Controls vSphere VM component protection for virtual machines in this cluster. Can be one of
enabledordisabled. Default:enabled. *- ha
Vm stringDependency Restart Condition The condition used to determine whether or not virtual machines in a certain restart priority class are online, allowing HA to move on to restarting virtual machines on the next priority. Can be one of
none,poweredOn,guestHbStatusGreen, orappHbStatusGreen. The default isnone, which means that a virtual machine is considered ready immediately after a host is found to start it on. *- ha
Vm numberFailure Interval If a heartbeat from a virtual machine is not received within this configured interval, the virtual machine is marked as failed. The value is in seconds. Default:
30.- ha
Vm numberMaximum Failure Window The length of the reset window in which
ha_vm_maximum_resetscan operate. When this window expires, no more resets are attempted regardless of the setting configured inha_vm_maximum_resets.-1means no window, meaning an unlimited reset time is allotted. The value is specified in seconds. Default:-1(no window).- ha
Vm numberMaximum Resets The maximum number of resets that HA will perform to a virtual machine when responding to a failure event. Default:
3- ha
Vm numberMinimum Uptime The time, in seconds, that HA waits after powering on a virtual machine before monitoring for heartbeats. Default:
120(2 minutes).- ha
Vm stringMonitoring The type of virtual machine monitoring to use when HA is enabled in the cluster. Can be one of
vmMonitoringDisabled,vmMonitoringOnly, orvmAndAppMonitoring. Default:vmMonitoringDisabled.- ha
Vm numberRestart Additional Delay Additional delay in seconds after ready condition is met. A VM is considered ready at this point. Default:
0(no delay). *- ha
Vm stringRestart Priority The default restart priority for affected virtual machines when vSphere detects a host failure. Can be one of
lowest,low,medium,high, orhighest. Default:medium.- ha
Vm numberRestart Timeout The maximum time, in seconds, that vSphere HA will wait for virtual machines in one priority to be ready before proceeding with the next priority. Default:
600(10 minutes). *- host
Cluster numberExit Timeout The timeout for each host maintenance mode operation when removing hosts from a cluster. The value is specified in seconds. Default:
3600(1 hour).- host
Managed boolean Can be set to
trueif compute cluster membership will be managed through thehostresource rather than thecompute_clusterresource. Conflicts with:host_system_ids. >>>>>>> v1.18.3- host
System string[]Ids The [managed object IDs][docs-about-morefs] of the hosts to put in the cluster. Conflicts with:
host_managed.- name string
The name of the cluster.
- proactive
Ha stringAutomation Level Determines how the host quarantine, maintenance mode, or virtual machine migration recommendations made by proactive HA are to be handled. Can be one of
AutomatedorManual. Default:Manual. *- proactive
Ha booleanEnabled Enables Proactive HA. Default:
false. *- proactive
Ha stringModerate Remediation The configured remediation for moderately degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toMaintenanceModewhenproactive_ha_severe_remediationis set toQuarantineMode. Default:QuarantineMode. *- proactive
Ha string[]Provider Ids The list of IDs for health update providers configured for this cluster. *
- proactive
Ha stringSevere Remediation The configured remediation for severely degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toQuarantineModewhenproactive_ha_moderate_remediationis set toMaintenanceMode. Default:QuarantineMode. *- resource
Pool stringId The managed object ID of the cluster’s root resource pool.
- string[]
The IDs of any tags to attach to this resource.
- custom_
attributes Dict[str, str] A map of custom attribute ids to attribute value strings to set for the datastore cluster.
- datacenter_
id str The managed object ID of the datacenter to create the cluster in. Forces a new resource if changed.
- dpm_
automation_ strlevel The automation level for host power operations in this cluster. Can be one of
manualorautomated. Default:manual.- dpm_
enabled bool Enable DPM support for DRS in this cluster. Requires
drs_enabledto betruein order to be effective. Default:false.- dpm_
threshold float A value between
1and5indicating the threshold of load within the cluster that influences host power operations. This affects both power on and power off operations - a lower setting will tolerate more of a surplus/deficit than a higher setting. Default:3.- drs_
advanced_ Dict[str, str]options A key/value map that specifies advanced options for DRS and DPM.
- drs_
automation_ strlevel The default automation level for all virtual machines in this cluster. Can be one of
manual,partiallyAutomated, orfullyAutomated. Default:manual.- drs_
enable_ boolpredictive_ drs When
true, enables DRS to use data from [vRealize Operations Manager][ref-vsphere-vro] to make proactive DRS recommendations. *- drs_
enable_ boolvm_ overrides Allow individual DRS overrides to be set for virtual machines in the cluster. Default:
true.- drs_
enabled bool Enable DRS for this cluster. Default:
false.- drs_
migration_ floatthreshold A value between
1and5indicating the threshold of imbalance tolerated between hosts. A lower setting will tolerate more imbalance while a higher setting will tolerate less. Default:3.- folder str
The relative path to a folder to put this cluster in. This is a path relative to the datacenter you are deploying the cluster to. Example: for the
dc1datacenter, and a providedfolderoffoo/bar, The provider will place a cluster namedcompute-cluster-testin a host folder located at/dc1/host/foo/bar, with the final inventory path being/dc1/host/foo/bar/datastore-cluster-test.- force_
evacuate_ boolon_ destroy When destroying the resource, setting this to
truewill auto-remove any hosts that are currently a member of the cluster, as if they were removed by taking their entry out ofhost_system_ids(see below). This is an advanced option and should only be used for testing. Default:false.- ha_
admission_ List[str]control_ failover_ host_ system_ ids Defines the managed object IDs of hosts to use as dedicated failover hosts. These hosts are kept as available as possible - admission control will block access to the host, and DRS will ignore the host when making recommendations.
- ha_
admission_ floatcontrol_ host_ failure_ tolerance The maximum number of failed hosts that admission control tolerates when making decisions on whether to permit virtual machine operations. The maximum is one less than the number of hosts in the cluster. Default:
1. *- ha_
admission_ floatcontrol_ performance_ tolerance The percentage of resource reduction that a cluster of virtual machines can tolerate in case of a failover. A value of 0 produces warnings only, whereas a value of 100 disables the setting. Default:
100(disabled).- ha_
admission_ strcontrol_ policy The type of admission control policy to use with vSphere HA. Can be one of
resourcePercentage,slotPolicy,failoverHosts, ordisabled. Default:resourcePercentage.- ha_
admission_ boolcontrol_ resource_ percentage_ auto_ compute Automatically determine available resource percentages by subtracting the average number of host resources represented by the
ha_admission_control_host_failure_tolerancesetting from the total amount of resources in the cluster. Disable to supply user-defined values. Default:true. *- ha_
admission_ floatcontrol_ resource_ percentage_ cpu Controls the user-defined percentage of CPU resources in the cluster to reserve for failover. Default:
100.- ha_
admission_ floatcontrol_ resource_ percentage_ memory Controls the user-defined percentage of memory resources in the cluster to reserve for failover. Default:
100.- ha_
admission_ floatcontrol_ slot_ policy_ explicit_ cpu Controls the user-defined CPU slot size, in MHz. Default:
32.- ha_
admission_ floatcontrol_ slot_ policy_ explicit_ memory Controls the user-defined memory slot size, in MB. Default:
100.- ha_
admission_ boolcontrol_ slot_ policy_ use_ explicit_ size Controls whether or not you wish to supply explicit values to CPU and memory slot sizes. The default is
false, which tells vSphere to gather a automatic average based on all powered-on virtual machines currently in the cluster.- ha_
advanced_ Dict[str, str]options A key/value map that specifies advanced options for vSphere HA.
- ha_
datastore_ strapd_ recovery_ action Controls the action to take on virtual machines if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
noneorreset. Default:none. *- ha_
datastore_ strapd_ response Controls the action to take on virtual machines when the cluster has detected loss to all paths to a relevant datastore. Can be one of
disabled,warning,restartConservative, orrestartAggressive. Default:disabled. *- ha_
datastore_ floatapd_ response_ delay Controls the delay in minutes to wait after an APD timeout event to execute the response action defined in
ha_datastore_apd_response. Default:3minutes. *- ha_
datastore_ strpdl_ response Controls the action to take on virtual machines when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
disabled,warning, orrestartAggressive. Default:disabled. *- ha_
enabled bool Enable vSphere HA for this cluster. Default:
false.- ha_
heartbeat_ List[str]datastore_ ids The list of managed object IDs for preferred datastores to use for HA heartbeating. This setting is only useful when
ha_heartbeat_datastore_policyis set to eitheruserSelectedDsorallFeasibleDsWithUserPreference.- ha_
heartbeat_ strdatastore_ policy The selection policy for HA heartbeat datastores. Can be one of
allFeasibleDs,userSelectedDs, orallFeasibleDsWithUserPreference. Default:allFeasibleDsWithUserPreference.- ha_
host_ strisolation_ response The action to take on virtual machines when a host has detected that it has been isolated from the rest of the cluster. Can be one of
none,powerOff, orshutdown. Default:none.- ha_
host_ strmonitoring Global setting that controls whether vSphere HA remediates virtual machines on host failure. Can be one of
enabledordisabled. Default:enabled.- ha_
vm_ strcomponent_ protection Controls vSphere VM component protection for virtual machines in this cluster. Can be one of
enabledordisabled. Default:enabled. *- ha_
vm_ strdependency_ restart_ condition The condition used to determine whether or not virtual machines in a certain restart priority class are online, allowing HA to move on to restarting virtual machines on the next priority. Can be one of
none,poweredOn,guestHbStatusGreen, orappHbStatusGreen. The default isnone, which means that a virtual machine is considered ready immediately after a host is found to start it on. *- ha_
vm_ floatfailure_ interval If a heartbeat from a virtual machine is not received within this configured interval, the virtual machine is marked as failed. The value is in seconds. Default:
30.- ha_
vm_ floatmaximum_ failure_ window The length of the reset window in which
ha_vm_maximum_resetscan operate. When this window expires, no more resets are attempted regardless of the setting configured inha_vm_maximum_resets.-1means no window, meaning an unlimited reset time is allotted. The value is specified in seconds. Default:-1(no window).- ha_
vm_ floatmaximum_ resets The maximum number of resets that HA will perform to a virtual machine when responding to a failure event. Default:
3- ha_
vm_ floatminimum_ uptime The time, in seconds, that HA waits after powering on a virtual machine before monitoring for heartbeats. Default:
120(2 minutes).- ha_
vm_ strmonitoring The type of virtual machine monitoring to use when HA is enabled in the cluster. Can be one of
vmMonitoringDisabled,vmMonitoringOnly, orvmAndAppMonitoring. Default:vmMonitoringDisabled.- ha_
vm_ floatrestart_ additional_ delay Additional delay in seconds after ready condition is met. A VM is considered ready at this point. Default:
0(no delay). *- ha_
vm_ strrestart_ priority The default restart priority for affected virtual machines when vSphere detects a host failure. Can be one of
lowest,low,medium,high, orhighest. Default:medium.- ha_
vm_ floatrestart_ timeout The maximum time, in seconds, that vSphere HA will wait for virtual machines in one priority to be ready before proceeding with the next priority. Default:
600(10 minutes). *- host_
cluster_ floatexit_ timeout The timeout for each host maintenance mode operation when removing hosts from a cluster. The value is specified in seconds. Default:
3600(1 hour).- host_
managed bool Can be set to
trueif compute cluster membership will be managed through thehostresource rather than thecompute_clusterresource. Conflicts with:host_system_ids. >>>>>>> v1.18.3- host_
system_ List[str]ids The [managed object IDs][docs-about-morefs] of the hosts to put in the cluster. Conflicts with:
host_managed.- name str
The name of the cluster.
- proactive_
ha_ strautomation_ level Determines how the host quarantine, maintenance mode, or virtual machine migration recommendations made by proactive HA are to be handled. Can be one of
AutomatedorManual. Default:Manual. *- proactive_
ha_ boolenabled Enables Proactive HA. Default:
false. *- proactive_
ha_ strmoderate_ remediation The configured remediation for moderately degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toMaintenanceModewhenproactive_ha_severe_remediationis set toQuarantineMode. Default:QuarantineMode. *- proactive_
ha_ List[str]provider_ ids The list of IDs for health update providers configured for this cluster. *
- proactive_
ha_ strsevere_ remediation The configured remediation for severely degraded hosts. Can be one of
MaintenanceModeorQuarantineMode. Note that this cannot be set toQuarantineModewhenproactive_ha_moderate_remediationis set toMaintenanceMode. Default:QuarantineMode. *- resource_
pool_ strid The managed object ID of the cluster’s root resource pool.
- List[str]
The IDs of any tags to attach to this resource.
Package Details
- Repository
- https://github.com/pulumi/pulumi-vsphere
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
vsphereTerraform Provider.