Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ocf_heartbeat_xen(7) [suse man page]

OCF_HEARTBEAT_XEN(7)						OCF resource agents					      OCF_HEARTBEAT_XEN(7)

NAME
ocf_heartbeat_Xen - Manages Xen unprivileged domains (DomUs) SYNOPSIS
Xen [start | stop | migrate_from | migrate_to | monitor | meta-data | validate-all] DESCRIPTION
Resource Agent for the Xen Hypervisor. Manages Xen virtual machine instances by mapping cluster resource start and stop, to Xen create and shutdown, respectively. A note on names We will try to extract the name from the config file (the xmfile attribute). If you use a simple assignment statement, then you should be fine. Otherwise, if there's some python acrobacy involved such as dynamically assigning names depending on other variables, and we will try to detect this, then please set the name attribute. You should also do that if there is any chance of a pathological situation where a config file might be missing, for example if it resides on a shared storage. If all fails, we finally fall back to the instance id to preserve backward compatibility. Para-virtualized guests can also be migrated by enabling the meta_attribute allow-migrate. SUPPORTED PARAMETERS
xmfile Absolute path to the Xen control file, for this virtual machine. (required, string, no default) name Name of the virtual machine. (optional, string, no default) shutdown_timeout The Xen agent will first try an orderly shutdown using xm shutdown. Should this not succeed within this timeout, the agent will escalate to xm destroy, forcibly killing the node. If this is not set, it will default to two-third of the stop action timeout. Setting this value to 0 forces an immediate destroy. (optional, boolean, no default) allow_mem_management This parameter enables dynamic adjustment of memory for start and stop actions used for Dom0 and the DomUs. The default is to not adjust memory dynamically. (optional, boolean, default 0) reserved_Dom0_memory In case memory management is used, this parameter defines the minimum amount of memory to be reserved for the dom0. The default minimum memory is 512MB. (optional, string, default 512) monitor_scripts To additionally monitor services within the unprivileged domain, add this parameter with a list of scripts to monitor. (optional, string, no default) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 60. stop Stops the resource. Suggested minimum timeout: 40. migrate_from Executes steps necessary for migrating the resource away from the node. Suggested minimum timeout: 120. migrate_to Executes steps necessary for migrating the resource to the node. Suggested minimum timeout: 120. monitor Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 5. EXAMPLE
The following is an example configuration for a Xen resource using the crm(8) shell: primitive example_Xen ocf:heartbeat:Xen params xmfile=string meta allow-migrate="true" op monitor depth="0" timeout="30" interval="10" SEE ALSO
http://www.linux-ha.org/wiki/Xen_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents 1.0.3 07/05/2010 OCF_HEARTBEAT_XEN(7)

Check Out this Related Man Page

OCF_HEARTBEAT_DUMMY(7)						OCF resource agents					    OCF_HEARTBEAT_DUMMY(7)

NAME
ocf_heartbeat_Dummy - Example stateless resource agent SYNOPSIS
Dummy [start | stop | monitor | migrate_to | migrate_from | meta-data | validate-all] DESCRIPTION
This is a Dummy Resource Agent. It does absolutely nothing except keep track of whether its running or not. Its purpose in life is for testing and to serve as a template for RA writers. NB: Please pay attention to the timeouts specified in the actions section below. They should be meaningful for the kind of resource the agent manages. They should be the minimum advised timeouts, but they shouldn't/cannot cover _all_ possible resource instances. So, try to be neither overly generous nor too stingy, but moderate. The minimum timeouts should never be below 10 seconds. SUPPORTED PARAMETERS
state Location to store the resource state in. (unique, optional, string, default /var/run/resource-agents/Dummy-default.state) fake Fake attribute that can be changed to cause a reload (optional, string, default dummy) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 20. stop Stops the resource. Suggested minimum timeout: 20. monitor Performs a detailed status check. Suggested minimum timeout: 20. Suggested interval: 10. reload Suggested minimum timeout: 20. migrate_to Executes steps necessary for migrating the resource to the node. Suggested minimum timeout: 20. migrate_from Executes steps necessary for migrating the resource away from the node. Suggested minimum timeout: 20. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 20. EXAMPLE
The following is an example configuration for a Dummy resource using the crm(8) shell: primitive p_Dummy ocf:heartbeat:Dummy meta allow-migrate="true" op monitor timeout="20" interval="10" depth="0" SEE ALSO
http://www.linux-ha.org/wiki/Dummy_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_DUMMY(7)
Man Page