Configuring Constraints - Novell SUSE LINUX ENTERPRISE SERVER 10 SP2 HEARTBEAT Manual

Configure the IP address completely with the Heartbeat RA configuration. No additional
modification is necessary in the system. The IP address RA is an OCF RA.
<group id="nfs_group">
<primitive id="nfs_resource" class="lsb" type="nfsserver"/>
<primitive id="ip_resource" class="ocf" provider="heartbeat"
type="IPaddr">
<instance_attributes id="ia-ipaddr_1">
</instance_attributes>
</primitive>
</group>
In a group resource, there may be several other resources. It must have an ID set.
The nfsserver is simple. It is just the LSB script for the NFS server. The service
itself must be configured in the system.
The IPaddr OCF RA does not need any configuration in the system. It is just
configured with the following instance_attributes.
There is only one mandatory instance attribute in the IPaddr RA. More possible
configuration options are found in the metadata of the RA.

5.3 Configuring Constraints

Having all the resources configured is only part of the job. Even if the clusters knows
all needed resources, it might still not be able to handle them correctly. For example,
it would be quite useless to try to mount the file system on the slave node of drbd (in
fact, this would fail with drbd). To inform the cluster about these things, define con-
straints.
In Heartbeat, there are three different kinds of constraints available:
• Locational constraints that define on which nodes a resource may be run
(rsc_location).
• Colocational constraints that tell the cluster which resources may or may not run
together on a node (rsc_colocation).
• Ordering constraints to define the sequence of actions (rsc_order).
52 Heartbeat
<attributes>
<nvpair id="ipaddr-nv-1" name="ip" value="10.10.0.1"/>
</attributes>