Hide Forgot
Created attachment 477076 [details] Luci/Conga Screen for Configuring Virtual Machine as Cluster Resource RHEL 6 Cluster Administration Documentation All the Conga Options for configuring Virtual Machine as Cluster Resource are not described in Cluster Administration Document. For example, what does these fields mean and what are the expected values and why? Options are as follows 1. Migration type 2. Migration Mapping 3. Status Program 4. Path to xmlfile used to create the VM 5. VM configuration file path 6. Path to the VM snapshot directory 7. Hypervisor URI 8.Migration URI
Attribute Description autostart Automatic start after quorum formation depend Top-level service this depends on, in service:name format. depend_mode Service dependency mode (soft or hard). domain Cluster failover Domain exclusive Exclusive resource group hypervisor Hypervisor hypervisor_uri Hypervisor URI (normally automatic). max_restarts Maximum restarts for this service. migrate Migration type (live or pause, default = live). migration_mapping memberhost:targethost,memberhost:targethost .. migration_uri Migration URI (normally automatic). name Name path Path to virtual machine configuration files. recovery Failure recovery policy ref Reference to existing vm resource in the resources section. restart_expire_time Restart expiration time; amount of time before a restart is forgotten. snapshot Path to the snapshot directory where the virtual machine image will be stored. status_program Additional status check program use_virsh If set to 1, vm.sh will use the virsh command to manage virtual machines instead of xm. This is required when using non-Xen virtual machines (e.g. qemu / KVM). xmlfile Full path to libvirt XML file describing the domain. __enforce_timeouts Consider a timeout for operations as fatal. __failure_expire_time Amount of time before a failure is forgotten. __independent_subtree Treat this and all children as an independent subtree. __max_failures Maximum number of failures before returning a failure to a status check.
fence_virt is still in Tech preview for RHEL 6.1, so I'm moving this bug to RHEL 6.2. If the feature is out of Tech preview and fully supported for 6.2 I will add the parameters to the table of fence of device parameters at that time.
Is this fixed now via BZ 704539? Is one a duplicate of the other?
joshua: Thanks for finding this and pointing this out. This was my error in thinking the bug referenced fence_virt rather than the virtual machine resource. Many thanks for nothing this. *** This bug has been marked as a duplicate of bug 704539 ***
Joshua: That's "thanks for noting" (not "thanks for nothing"). Yikes. My apologies for that very unfortunate (if amusing) typo.