Novell LINUX ENTERPRISE 11 - HIGH AVAILABILITY, Manual, Page: 71 / 298

The previous command configures a “primitive” with the name
myIP
. You need
the class (here
ocf
), provider (
heartbeat
), and type (
IPaddr
). Furthermore
this primitive expects some parameters like the IP address. You have to change
the address to your setup.
4 Display and review the changes you have made:
crm(live)configure# show
To see the XML structure, use the following:
crm(live)configure# show xml
5
Commit your changes to take effect:
crm(live)configure# commit
5.3.1 LSB Initialization Scripts
All LSB scripts are commonly found in the directory
/etc/init.d
. They must have
several actions implemented, which are at least
start
,
stop
,
restart
,
reload
,
force-reload
, and
status
as explained in
http://www.linux-foundation
.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB/iniscrptact.html
.
The configuration of those services is not standardized. If you intend to use an LSB
script with High Availability, make sure that you understand how the relevant script is
configured. Often you can find some documentation to this in the documentation of the
relevant package in
/usr/share/doc/packages/ PACKAGENAME
.
NOTE: Do Not Touch Services Used by High Availability
When used by High Availability, the service should not be touched by other
means. This means that it should not be started or stopped on boot, reboot,
or manually. However, if you want to check if the service is configured properly,
start it manually, but make sure that it is stopped again before High Availability
takes over.
Before using an LSB resource, make sure that the configuration of this resource is
present and identical on all cluster nodes. The configuration is not managed by High
Availability. You must do this yourself.
Configuring Cluster Resources From Command Line 61