HaVmOverride
The vsphere..HaVmOverride resource can be used to add an override for
vSphere HA settings on a cluster for a specific virtual machine. With this
resource, one can control specific HA settings so that they are different than
the cluster default, accommodating the needs of that specific virtual machine,
while not affecting the rest of the cluster.
For more information on vSphere HA, see this page.
NOTE: This resource requires vCenter and is not available on direct ESXi connections.
Example Usage
using Pulumi;
using VSphere = Pulumi.VSphere;
class MyStack : Stack
{
public MyStack()
{
var dc = Output.Create(VSphere.GetDatacenter.InvokeAsync(new VSphere.GetDatacenterArgs
{
Name = "dc1",
}));
var datastore = dc.Apply(dc => Output.Create(VSphere.GetDatastore.InvokeAsync(new VSphere.GetDatastoreArgs
{
DatacenterId = dc.Id,
Name = "datastore1",
})));
var cluster = dc.Apply(dc => Output.Create(VSphere.GetComputeCluster.InvokeAsync(new VSphere.GetComputeClusterArgs
{
DatacenterId = dc.Id,
Name = "cluster1",
})));
var network = dc.Apply(dc => Output.Create(VSphere.GetNetwork.InvokeAsync(new VSphere.GetNetworkArgs
{
DatacenterId = dc.Id,
Name = "network1",
})));
var vm = new VSphere.VirtualMachine("vm", new VSphere.VirtualMachineArgs
{
DatastoreId = datastore.Apply(datastore => datastore.Id),
Disks =
{
new VSphere.Inputs.VirtualMachineDiskArgs
{
Label = "disk0",
Size = 20,
},
},
GuestId = "other3xLinux64Guest",
Memory = 2048,
NetworkInterfaces =
{
new VSphere.Inputs.VirtualMachineNetworkInterfaceArgs
{
NetworkId = network.Apply(network => network.Id),
},
},
NumCpus = 2,
ResourcePoolId = cluster.Apply(cluster => cluster.ResourcePoolId),
});
var haVmOverride = new VSphere.HaVmOverride("haVmOverride", new VSphere.HaVmOverrideArgs
{
ComputeClusterId = cluster.Apply(cluster => cluster.Id),
HaVmRestartPriority = "highest",
VirtualMachineId = vm.Id,
});
}
}
Coming soon!
import pulumi
import pulumi_vsphere as vsphere
dc = vsphere.get_datacenter(name="dc1")
datastore = vsphere.get_datastore(datacenter_id=dc.id,
name="datastore1")
cluster = vsphere.get_compute_cluster(datacenter_id=dc.id,
name="cluster1")
network = vsphere.get_network(datacenter_id=dc.id,
name="network1")
vm = vsphere.VirtualMachine("vm",
datastore_id=datastore.id,
disks=[{
"label": "disk0",
"size": 20,
}],
guest_id="other3xLinux64Guest",
memory=2048,
network_interfaces=[{
"networkId": network.id,
}],
num_cpus=2,
resource_pool_id=cluster.resource_pool_id)
ha_vm_override = vsphere.HaVmOverride("haVmOverride",
compute_cluster_id=cluster.id,
ha_vm_restart_priority="highest",
virtual_machine_id=vm.id)import * as pulumi from "@pulumi/pulumi";
import * as vsphere from "@pulumi/vsphere";
const dc = pulumi.output(vsphere.getDatacenter({
name: "dc1",
}, { async: true }));
const datastore = dc.apply(dc => vsphere.getDatastore({
datacenterId: dc.id,
name: "datastore1",
}, { async: true }));
const cluster = dc.apply(dc => vsphere.getComputeCluster({
datacenterId: dc.id,
name: "cluster1",
}, { async: true }));
const network = dc.apply(dc => vsphere.getNetwork({
datacenterId: dc.id,
name: "network1",
}, { async: true }));
const vm = new vsphere.VirtualMachine("vm", {
datastoreId: datastore.id,
disks: [{
label: "disk0",
size: 20,
}],
guestId: "other3xLinux64Guest",
memory: 2048,
networkInterfaces: [{
networkId: network.id,
}],
numCpus: 2,
resourcePoolId: cluster.resourcePoolId,
});
const haVmOverride = new vsphere.HaVmOverride("ha_vm_override", {
computeClusterId: cluster.id,
haVmRestartPriority: "highest",
virtualMachineId: vm.id,
});Create a HaVmOverride Resource
new HaVmOverride(name: string, args: HaVmOverrideArgs, opts?: CustomResourceOptions);def HaVmOverride(resource_name, opts=None, compute_cluster_id=None, ha_datastore_apd_recovery_action=None, ha_datastore_apd_response=None, ha_datastore_apd_response_delay=None, ha_datastore_pdl_response=None, ha_host_isolation_response=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_monitoring_use_cluster_defaults=None, ha_vm_restart_priority=None, ha_vm_restart_timeout=None, virtual_machine_id=None, __props__=None);func NewHaVmOverride(ctx *Context, name string, args HaVmOverrideArgs, opts ...ResourceOption) (*HaVmOverride, error)public HaVmOverride(string name, HaVmOverrideArgs args, CustomResourceOptions? opts = null)- name string
- The unique name of the resource.
- args HaVmOverrideArgs
- 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 HaVmOverrideArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args HaVmOverrideArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
HaVmOverride Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Programming Model docs.
Inputs
The HaVmOverride resource accepts the following input properties:
- Compute
Cluster stringId The managed object reference ID of the cluster to put the override in. Forces a new resource if changed.
- Virtual
Machine stringId The UUID of the virtual machine to create the override for. Forces a new resource if changed.
- Ha
Datastore stringApd Recovery Action Controls the action to take on this virtual machine if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
useClusterDefault,noneorreset. Default:useClusterDefault.- Ha
Datastore stringApd Response Controls the action to take on this virtual machine when the cluster has detected loss to all paths to a relevant datastore. Can be one of
clusterDefault,disabled,warning,restartConservative, orrestartAggressive. Default:clusterDefault.- 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. Use-1to use the cluster default. Default:-1.- Ha
Datastore stringPdl Response Controls the action to take on this virtual machine when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
clusterDefault,disabled,warning, orrestartAggressive. Default:clusterDefault.- Ha
Host stringIsolation Response The action to take on this virtual machine when a host has detected that it has been isolated from the rest of the cluster. Can be one of
clusterIsolationResponse,none,powerOff, orshutdown. Default:clusterIsolationResponse.- Ha
Vm intFailure Interval If a heartbeat from this 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 this virtual machine when responding to a failure event. Default:
3- Ha
Vm intMinimum Uptime The time, in seconds, that HA waits after powering on this 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 boolMonitoring Use Cluster Defaults Determines whether or not the cluster’s default settings or the VM override settings specified in this resource are used for virtual machine monitoring. The default is
true(use cluster defaults) - set tofalseto have overrides take effect.- Ha
Vm stringRestart Priority The restart priority for the virtual machine when vSphere detects a host failure. Can be one of
clusterRestartPriority,lowest,low,medium,high, orhighest. Default:clusterRestartPriority.- Ha
Vm intRestart Timeout The maximum time, in seconds, that vSphere HA will wait for this virtual machine to be ready. Use
-1to specify the cluster default. Default:-1.
- Compute
Cluster stringId The managed object reference ID of the cluster to put the override in. Forces a new resource if changed.
- Virtual
Machine stringId The UUID of the virtual machine to create the override for. Forces a new resource if changed.
- Ha
Datastore stringApd Recovery Action Controls the action to take on this virtual machine if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
useClusterDefault,noneorreset. Default:useClusterDefault.- Ha
Datastore stringApd Response Controls the action to take on this virtual machine when the cluster has detected loss to all paths to a relevant datastore. Can be one of
clusterDefault,disabled,warning,restartConservative, orrestartAggressive. Default:clusterDefault.- 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. Use-1to use the cluster default. Default:-1.- Ha
Datastore stringPdl Response Controls the action to take on this virtual machine when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
clusterDefault,disabled,warning, orrestartAggressive. Default:clusterDefault.- Ha
Host stringIsolation Response The action to take on this virtual machine when a host has detected that it has been isolated from the rest of the cluster. Can be one of
clusterIsolationResponse,none,powerOff, orshutdown. Default:clusterIsolationResponse.- Ha
Vm intFailure Interval If a heartbeat from this 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 this virtual machine when responding to a failure event. Default:
3- Ha
Vm intMinimum Uptime The time, in seconds, that HA waits after powering on this 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 boolMonitoring Use Cluster Defaults Determines whether or not the cluster’s default settings or the VM override settings specified in this resource are used for virtual machine monitoring. The default is
true(use cluster defaults) - set tofalseto have overrides take effect.- Ha
Vm stringRestart Priority The restart priority for the virtual machine when vSphere detects a host failure. Can be one of
clusterRestartPriority,lowest,low,medium,high, orhighest. Default:clusterRestartPriority.- Ha
Vm intRestart Timeout The maximum time, in seconds, that vSphere HA will wait for this virtual machine to be ready. Use
-1to specify the cluster default. Default:-1.
- compute
Cluster stringId The managed object reference ID of the cluster to put the override in. Forces a new resource if changed.
- virtual
Machine stringId The UUID of the virtual machine to create the override for. Forces a new resource if changed.
- ha
Datastore stringApd Recovery Action Controls the action to take on this virtual machine if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
useClusterDefault,noneorreset. Default:useClusterDefault.- ha
Datastore stringApd Response Controls the action to take on this virtual machine when the cluster has detected loss to all paths to a relevant datastore. Can be one of
clusterDefault,disabled,warning,restartConservative, orrestartAggressive. Default:clusterDefault.- 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. Use-1to use the cluster default. Default:-1.- ha
Datastore stringPdl Response Controls the action to take on this virtual machine when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
clusterDefault,disabled,warning, orrestartAggressive. Default:clusterDefault.- ha
Host stringIsolation Response The action to take on this virtual machine when a host has detected that it has been isolated from the rest of the cluster. Can be one of
clusterIsolationResponse,none,powerOff, orshutdown. Default:clusterIsolationResponse.- ha
Vm numberFailure Interval If a heartbeat from this 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 this virtual machine when responding to a failure event. Default:
3- ha
Vm numberMinimum Uptime The time, in seconds, that HA waits after powering on this 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 booleanMonitoring Use Cluster Defaults Determines whether or not the cluster’s default settings or the VM override settings specified in this resource are used for virtual machine monitoring. The default is
true(use cluster defaults) - set tofalseto have overrides take effect.- ha
Vm stringRestart Priority The restart priority for the virtual machine when vSphere detects a host failure. Can be one of
clusterRestartPriority,lowest,low,medium,high, orhighest. Default:clusterRestartPriority.- ha
Vm numberRestart Timeout The maximum time, in seconds, that vSphere HA will wait for this virtual machine to be ready. Use
-1to specify the cluster default. Default:-1.
- compute_
cluster_ strid The managed object reference ID of the cluster to put the override in. Forces a new resource if changed.
- virtual_
machine_ strid The UUID of the virtual machine to create the override for. Forces a new resource if changed.
- ha_
datastore_ strapd_ recovery_ action Controls the action to take on this virtual machine if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
useClusterDefault,noneorreset. Default:useClusterDefault.- ha_
datastore_ strapd_ response Controls the action to take on this virtual machine when the cluster has detected loss to all paths to a relevant datastore. Can be one of
clusterDefault,disabled,warning,restartConservative, orrestartAggressive. Default:clusterDefault.- 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. Use-1to use the cluster default. Default:-1.- ha_
datastore_ strpdl_ response Controls the action to take on this virtual machine when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
clusterDefault,disabled,warning, orrestartAggressive. Default:clusterDefault.- ha_
host_ strisolation_ response The action to take on this virtual machine when a host has detected that it has been isolated from the rest of the cluster. Can be one of
clusterIsolationResponse,none,powerOff, orshutdown. Default:clusterIsolationResponse.- ha_
vm_ floatfailure_ interval If a heartbeat from this 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 this virtual machine when responding to a failure event. Default:
3- ha_
vm_ floatminimum_ uptime The time, in seconds, that HA waits after powering on this 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_ boolmonitoring_ use_ cluster_ defaults Determines whether or not the cluster’s default settings or the VM override settings specified in this resource are used for virtual machine monitoring. The default is
true(use cluster defaults) - set tofalseto have overrides take effect.- ha_
vm_ strrestart_ priority The restart priority for the virtual machine when vSphere detects a host failure. Can be one of
clusterRestartPriority,lowest,low,medium,high, orhighest. Default:clusterRestartPriority.- ha_
vm_ floatrestart_ timeout The maximum time, in seconds, that vSphere HA will wait for this virtual machine to be ready. Use
-1to specify the cluster default. Default:-1.
Outputs
All input properties are implicitly available as output properties. Additionally, the HaVmOverride resource produces the following output properties:
Look up an Existing HaVmOverride Resource
Get an existing HaVmOverride 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?: HaVmOverrideState, opts?: CustomResourceOptions): HaVmOverridestatic get(resource_name, id, opts=None, compute_cluster_id=None, ha_datastore_apd_recovery_action=None, ha_datastore_apd_response=None, ha_datastore_apd_response_delay=None, ha_datastore_pdl_response=None, ha_host_isolation_response=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_monitoring_use_cluster_defaults=None, ha_vm_restart_priority=None, ha_vm_restart_timeout=None, virtual_machine_id=None, __props__=None);func GetHaVmOverride(ctx *Context, name string, id IDInput, state *HaVmOverrideState, opts ...ResourceOption) (*HaVmOverride, error)public static HaVmOverride Get(string name, Input<string> id, HaVmOverrideState? 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:
- Compute
Cluster stringId The managed object reference ID of the cluster to put the override in. Forces a new resource if changed.
- Ha
Datastore stringApd Recovery Action Controls the action to take on this virtual machine if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
useClusterDefault,noneorreset. Default:useClusterDefault.- Ha
Datastore stringApd Response Controls the action to take on this virtual machine when the cluster has detected loss to all paths to a relevant datastore. Can be one of
clusterDefault,disabled,warning,restartConservative, orrestartAggressive. Default:clusterDefault.- 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. Use-1to use the cluster default. Default:-1.- Ha
Datastore stringPdl Response Controls the action to take on this virtual machine when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
clusterDefault,disabled,warning, orrestartAggressive. Default:clusterDefault.- Ha
Host stringIsolation Response The action to take on this virtual machine when a host has detected that it has been isolated from the rest of the cluster. Can be one of
clusterIsolationResponse,none,powerOff, orshutdown. Default:clusterIsolationResponse.- Ha
Vm intFailure Interval If a heartbeat from this 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 this virtual machine when responding to a failure event. Default:
3- Ha
Vm intMinimum Uptime The time, in seconds, that HA waits after powering on this 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 boolMonitoring Use Cluster Defaults Determines whether or not the cluster’s default settings or the VM override settings specified in this resource are used for virtual machine monitoring. The default is
true(use cluster defaults) - set tofalseto have overrides take effect.- Ha
Vm stringRestart Priority The restart priority for the virtual machine when vSphere detects a host failure. Can be one of
clusterRestartPriority,lowest,low,medium,high, orhighest. Default:clusterRestartPriority.- Ha
Vm intRestart Timeout The maximum time, in seconds, that vSphere HA will wait for this virtual machine to be ready. Use
-1to specify the cluster default. Default:-1.- Virtual
Machine stringId The UUID of the virtual machine to create the override for. Forces a new resource if changed.
- Compute
Cluster stringId The managed object reference ID of the cluster to put the override in. Forces a new resource if changed.
- Ha
Datastore stringApd Recovery Action Controls the action to take on this virtual machine if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
useClusterDefault,noneorreset. Default:useClusterDefault.- Ha
Datastore stringApd Response Controls the action to take on this virtual machine when the cluster has detected loss to all paths to a relevant datastore. Can be one of
clusterDefault,disabled,warning,restartConservative, orrestartAggressive. Default:clusterDefault.- 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. Use-1to use the cluster default. Default:-1.- Ha
Datastore stringPdl Response Controls the action to take on this virtual machine when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
clusterDefault,disabled,warning, orrestartAggressive. Default:clusterDefault.- Ha
Host stringIsolation Response The action to take on this virtual machine when a host has detected that it has been isolated from the rest of the cluster. Can be one of
clusterIsolationResponse,none,powerOff, orshutdown. Default:clusterIsolationResponse.- Ha
Vm intFailure Interval If a heartbeat from this 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 this virtual machine when responding to a failure event. Default:
3- Ha
Vm intMinimum Uptime The time, in seconds, that HA waits after powering on this 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 boolMonitoring Use Cluster Defaults Determines whether or not the cluster’s default settings or the VM override settings specified in this resource are used for virtual machine monitoring. The default is
true(use cluster defaults) - set tofalseto have overrides take effect.- Ha
Vm stringRestart Priority The restart priority for the virtual machine when vSphere detects a host failure. Can be one of
clusterRestartPriority,lowest,low,medium,high, orhighest. Default:clusterRestartPriority.- Ha
Vm intRestart Timeout The maximum time, in seconds, that vSphere HA will wait for this virtual machine to be ready. Use
-1to specify the cluster default. Default:-1.- Virtual
Machine stringId The UUID of the virtual machine to create the override for. Forces a new resource if changed.
- compute
Cluster stringId The managed object reference ID of the cluster to put the override in. Forces a new resource if changed.
- ha
Datastore stringApd Recovery Action Controls the action to take on this virtual machine if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
useClusterDefault,noneorreset. Default:useClusterDefault.- ha
Datastore stringApd Response Controls the action to take on this virtual machine when the cluster has detected loss to all paths to a relevant datastore. Can be one of
clusterDefault,disabled,warning,restartConservative, orrestartAggressive. Default:clusterDefault.- 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. Use-1to use the cluster default. Default:-1.- ha
Datastore stringPdl Response Controls the action to take on this virtual machine when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
clusterDefault,disabled,warning, orrestartAggressive. Default:clusterDefault.- ha
Host stringIsolation Response The action to take on this virtual machine when a host has detected that it has been isolated from the rest of the cluster. Can be one of
clusterIsolationResponse,none,powerOff, orshutdown. Default:clusterIsolationResponse.- ha
Vm numberFailure Interval If a heartbeat from this 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 this virtual machine when responding to a failure event. Default:
3- ha
Vm numberMinimum Uptime The time, in seconds, that HA waits after powering on this 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 booleanMonitoring Use Cluster Defaults Determines whether or not the cluster’s default settings or the VM override settings specified in this resource are used for virtual machine monitoring. The default is
true(use cluster defaults) - set tofalseto have overrides take effect.- ha
Vm stringRestart Priority The restart priority for the virtual machine when vSphere detects a host failure. Can be one of
clusterRestartPriority,lowest,low,medium,high, orhighest. Default:clusterRestartPriority.- ha
Vm numberRestart Timeout The maximum time, in seconds, that vSphere HA will wait for this virtual machine to be ready. Use
-1to specify the cluster default. Default:-1.- virtual
Machine stringId The UUID of the virtual machine to create the override for. Forces a new resource if changed.
- compute_
cluster_ strid The managed object reference ID of the cluster to put the override in. Forces a new resource if changed.
- ha_
datastore_ strapd_ recovery_ action Controls the action to take on this virtual machine if an APD status on an affected datastore clears in the middle of an APD event. Can be one of
useClusterDefault,noneorreset. Default:useClusterDefault.- ha_
datastore_ strapd_ response Controls the action to take on this virtual machine when the cluster has detected loss to all paths to a relevant datastore. Can be one of
clusterDefault,disabled,warning,restartConservative, orrestartAggressive. Default:clusterDefault.- 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. Use-1to use the cluster default. Default:-1.- ha_
datastore_ strpdl_ response Controls the action to take on this virtual machine when the cluster has detected a permanent device loss to a relevant datastore. Can be one of
clusterDefault,disabled,warning, orrestartAggressive. Default:clusterDefault.- ha_
host_ strisolation_ response The action to take on this virtual machine when a host has detected that it has been isolated from the rest of the cluster. Can be one of
clusterIsolationResponse,none,powerOff, orshutdown. Default:clusterIsolationResponse.- ha_
vm_ floatfailure_ interval If a heartbeat from this 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 this virtual machine when responding to a failure event. Default:
3- ha_
vm_ floatminimum_ uptime The time, in seconds, that HA waits after powering on this 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_ boolmonitoring_ use_ cluster_ defaults Determines whether or not the cluster’s default settings or the VM override settings specified in this resource are used for virtual machine monitoring. The default is
true(use cluster defaults) - set tofalseto have overrides take effect.- ha_
vm_ strrestart_ priority The restart priority for the virtual machine when vSphere detects a host failure. Can be one of
clusterRestartPriority,lowest,low,medium,high, orhighest. Default:clusterRestartPriority.- ha_
vm_ floatrestart_ timeout The maximum time, in seconds, that vSphere HA will wait for this virtual machine to be ready. Use
-1to specify the cluster default. Default:-1.- virtual_
machine_ strid The UUID of the virtual machine to create the override for. Forces a new resource if changed.
Package Details
- Repository
- https://github.com/pulumi/pulumi-vsphere
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
vsphereTerraform Provider.