Debugging Your Configuration Changes; Creating Cluster Resources - Novell LINUX ENTERPRISE 11 - HIGH AVAILABILITY Manual

5.2 Debugging Your Configuration
Before loading the changes back into the cluster, it is recommended to view your changes
with ptest. The ptest can show a diagram of actions which would be induced by
the changes to be committed. You need the graphiz package to display the diagrams.
The following example is a transcript, adding a monitor operation:
# crm
crm(live)# configure
crm(live)configure# show fence-node2
primitive fence-node2 stonith:apcsmart \
crm(live)configure# monitor fence-node2 120m:60s
crm(live)configure# show changed
primitive fence-node2 stonith:apcsmart \
crm(live)configure# ptest
crm(live)configure# commit

5.3 Creating Cluster Resources

There are three types of RAs (Resource Agents) available with the cluster. First, there
are legacy Heartbeat 1 scripts. High availability can make use of LSB initialization
scripts. Finally, the cluster has its own set of OCF (Open Cluster Framework) agents.
This documentation concentrates on LSB scripts and OCF agents.
To create a cluster resource use the crm tool. To add a new resource to the cluster, the
general procedure is as follows:
1 Open a shell and become root.
2 Run crm to open the internal shell of crm. The prompt changes to crm(live)#.
3 Configure a primitive IP address:
60 High Availability Guide
Changes
params hostlist="node2"
params hostlist="node2" \
op monitor interval="120m" timeout="60s"
crm(live)# configure
crm(live)configure# primitive myIP ocf:heartbeat:IPaddr \
params ip=127.0.0.99 op monitor interval=60s