# Timing and fencing configuration (uncomment to override defaults)
pvc_vm_shutdown_timeout:180# Number of seconds before a 'shutdown' VM is forced off
pvc_keepalive_interval:5# Number of seconds between keepalive ticks
pvc_fence_intervals:6# Number of keepalive ticks before a node is considered dead
pvc_suicide_intervals:0# Number of keepalive ticks before a node consideres itself dead (0 to disable)
pvc_fence_successful_action:migrate # What to do with VMs when a fence is successful (migrate, None)
pvc_fence_failed_action:None # What to do with VMs when a fence is failed (migrate, None) - migrate is DANGEROUS without pvc_suicide_intervals set to < pvc_fence_intervals
- hostname:"pvc1"# The full ansible inventory hostname of the node
is_coordinator:yes# If the node is a coordinator or not
node_id:1# The sequential node ID, usually matches the numerical part of the hostname
router_id:"10.0.0.1"# The router ID of the node; can be the IP Address of the Cluster network, or the node_id, or some other unique number
cluster_ip:"by-id"# The Cluster network IP of the host; by-id uses the network then adds the node as node_id within that network (e.g. pvc1 becomes x.y.z.1)
storage_ip:"by-id"# The Storage network IP of the host; by-id as above
upstream_ip:""# The Upstream network IP of the host; by-id as above
ipmi_host:"pvc1-lom"# The IPMI hostname of the node
ipmi_user:""# The IPMI username to use
ipmi_password:""# The IPMI password to use
cpu_tuning:# Per-node CPU tuning options; if set, overrides the global options above; useful if a node has different CPU characteristics