Configuring Crm Options - Novell SUSE LINUX ENTERPRISE SERVER 10 SP2 HEARTBEAT Manual

• The NFS server as well as the IP address start after the file system is mounted.
<rsc_order id="nfs_second" from="nfs_group" action="start"
to="filesystem_resource" to_action="start" type="after"/>
• The NFS server as well as the IP address must be on the same node as the file sys-
tem.
<rsc_colocation id="nfs_on_drbd" to="filesystem_resource"
from="nfs_group" score="INFINITY"/>
• In addition to that, issue constraint that prevents the NFS server from running on
a node where drbd is running in slave mode.
<rsc_colocation id="nfs_on_slave" to="drbd_resource"
to_role="slave" from="nfs_group" score="-INFINITY"/>

5.4 Configuring CRM Options

The CRM options define the global behavior of a cluster. In principle, the default values
should be acceptable for many environments, but if you want to use special services,
like STONITH devices, you must inform the cluster about this. All options of
crm_config are made with nvpair and are added to cib.xml. For example, to
change the cluster-delay from its default value of 60s to 120s, use the following
configuration:
<cluster_property_set>
<attributes>
<nvpair id="1" name="cluster-delay" value="120s"/>
</attributes>
</cluster_property_set>
Write this information to a file and load it to the cluster with the command cibadmin
-C -o crm_config -x filename. The following is an overview of all available
configuration options:
cluster-delay (interval, default=60s)
This option used to be known as transition_idle_timeout. If no activity
is recorded in this time, the transition is deemed failed as are all sent actions that
have not yet been confirmed complete. If any operation initiated has an explicit
higher time-out, the higher value applies.
Manual Configuration of a Cluster 55