Some minor exceptions to the behavior of SUSE Xen VMs managed by the Orchestration Server in a Pacemaker cluster include the following:
Building VMs (that is, using the VM Builder through the Orchestration Server action) is not supported in a Xen cluster. You first need to build the VMs in a non-clustered environment and then afterwards provision them to the Xen cluster.
The action is not supported for VMs running within a Xen cluster.
The , , , and (VNC console) actions are supported in the cluster only when the VM is configured to use the Xen.CMOS script. These actions are unavailable if you use the default Xen OCF script provided by the SLES 11 HAE product.
During the action, the xen provisioning adapter discovers any configured Xen clusters and models them as follows:
Creates a VmHostCluster object using the name of the clustered Orchestration Agent by default.
Discovers all nodes associated with the create VmHostCluster operation and models them as regular VM host Grid objects with the vmhost.cluster fact specified (this identifies the VM host as a member of a VmHostCluster).
Creates repositories based on file systems under the control of the clustering stack. These are resources that define the Filesystem OCF script in the cluster CIB. The provisioning adapter does not discover any shared storage that is not under control of the cluster stack. You must manually add this storage, if necessary.
When VMs are discovered (that is, when the action is executed), they are configured with a set of custom facts. These facts are stored on the VM Grid object. They are listed and described in the table below.
|
Custom Fact Name |
Description |
|---|---|
|
resource.vm.linuxha.cib_xml.id |
The unique ID of this VM as known by the cluster CIB. The fact is used as an identifier when performing actions on a VM running within a Xen Pacemaker cluster. |
|
resource.vm.linuxha.cib_xml |
The stored CIB XML definition for this VM in the cluster. When a VM is discovered (that is, when the , , or actions are executed) this fact is overwritten with new data queried from the cluster CIB. For all other actions (for example, , , etc.), the cluster’s CIB definition for the VM is replaced with the contents of this fact. |
The new xenClusterVmDefaults policy is associated by default to the VMs_xen Resource Group. The policy defines a set of default facts on a VM grid object that belongs to a Xen cluster. The facts are listed and described in the table below.
|
Fact Name |
Description |
|---|---|
|
resource.vm.linuxha.cib_xml_default |
The default CIB primitive to be used in the case where a CIB definition for this VM does not exist (that is, the VM is not defined in the cluster CIB and the value for the resource.vm.linuxha.cib_xml fact is empty). |
|
resource.vm.linuxha.clear_migrate_constraints_on_shutdown |
Used when shutting down (or restarting) the vm. If set, any location constraints created by migrate will be cleared at shutdown time. If there are specific location constraints created by an administrator, they are not cleared (unless they follow the naming convention for standard migrate constraints). |
|
resource.vm.linuxha.failcount.threshold |
Defines the allowed threshold for the failcount value used during the provisioning of a VM to a cluster. If the specified failcount threshold has been reached on all nodes in the cluster, the failcount will be reset back to 0 before attempting the start of the VM. This value can be one of: '+INFINITY', or '<Integer>'. To disable this feature, specify a value of '-1'. |
|
resource.vm.linuxha.migrate.timeout |
Timeout (in seconds) to wait for a clustered VM to reach the running state following migration. A value of 0 means wait forever. If set, this value overrides vm.linuxha.vm_state.wait.timeout (for migrate). |
|
resource.vm.linuxha.provision.timeout |
Timeout (in seconds) to wait for a clustered VM to reach the running state. A value of 0 means wait forever. If set, this value overrides vm.linuxha.vm_state.wait.timeout, and is set as the start operation timeout. |
|
resource.vm.linuxha.shutdown.timeout |
Timeout (in seconds) to wait for a clustered VM to reach the running state. A value of 0 means wait forever. if set, this value overrides vm.linuxha.vm_state.wait.timeout, and is set as the stop operation timeout and the VM’s shutdown_timeout in the CIB. To use per-VM values, set the value of this fact to the empty string (‘ ‘). The default is to use the value of the resource.vm.shutdown.timeout fact. |
|
resource.vm.linuxha.vm_state.wait.interval |
Defines the interval (in seconds) when the desired VM state should be re-checked (sleep interval). The default value is 5 seconds. |
|
resource.vm.linuxha.vm_state.wait.timeout |
Timeout (in seconds) to wait for a desired VM state. A value of -1 means wait forever. The default value is 120 seconds (2 min). |
The new xenClusterResource policy is associated by default to the Clusters_xen Resource Group. The policy defines a set of default facts on a Xen cluster grid object. The facts are listed and described in the table below.
|
Fact Name |
Description |
|---|---|
|
resource.linuxha.joblets.default_slots |
Specifies the default number of joblets slots to create for a Xen Cluster resource. |
|
resource.linuxha.cibadmin.cache.enabled |
If the value for this fact is true, the cluster CIB is cached when invoking queries. If the value is false, the CIB is queried directly. |
|
resource.linuxha.cibadmin.cache.lifetime |
The amount of time (in seconds) for which the cached CIB should stay valid. |
|
resource.linuxha.cibadmin.cache.invalidate_on_write |
Specifies (true or false) whether the CIB cache should be invalidated when writing to the CIB. |