This Resource Agent (RA) can be used if you want to build a Heartbeat cluster in a OES2 environment and if you want to make your NCP volumes (which reside on traditional Linux filesystems) highly available.
It can NOT be used if your NCP volumes are on NSS. It's merely for people who don't use Novell Cluster Services but still want to put some of their OES2 resources in a cluster (based on Heartbeat2 which is part of SLES10)
This RA is using the NCS idea where each cluster resource (=NCP volume) has its own virtual IP address You also need to have shared storage on which the NCP volume resides.
I assume you already have a basic heartbeat configuration working.
Drop the RA in /usr/lib/ocf/resource.d/heartbeat/
1) Create a Linux filesystem like ext3 or reiser on a shared disk (iSCSI, SAN, ...)
e.g I want to create an ext3 filesystem on an iSCSI disk which is /dev/sda
[0:0:0:0] disk IET VIRTUAL-DISK 0 /dev/sda
# mkfs.ext3 /dev/sda
2) Mount this disk somewhere on your system
# mkdir /media/ncp/users
# mount /dev/sda /media/ncp/users
3) Create an NCP volume on this disk
e.g The NCP volume will be called USERS
# ncpcon create volume USERS /media/ncp/users
This command creates a Volume object in eDirectory, and associates the volumename
to a path on your server.
4) Edit /etc/opt/novell/ncpserv.cfg and comment or remove the line that was added for the volume.
The reason why we do this is because we don't want to mount the ncp volume at boot, the cluster will mount this if necessary.
e.g The line that refers to the USERS volume in ncpserv.cfg
VOLUME USERS /media/ncp/users
5) Unmount the NCP volume
# ncpcon dismount USERS
6) Unmount the ext3 filesystem
# umount /media/ncp/users
6) Create a Virtual NCP Server Object for NCP Volumes in eDirectory. This is to make it easier for clients to access the clustered volumes
since it does not point to a physical server.
Go to iManager > Directory Administration > Create object > select 'NCP server'
specify a name for this virtual NCP server object (e.g: NCP_USERSVOL_SHR)
7) Add an IP address resources to your heartbeat configuration. This IP is the virtual IP of the NCP volume. Each NCP volume would have its own IP.
8) Add a Filesystem resource to the heartbeat configuration. This Filesystem resource will mount the shared disk on a specified mountpoint
9) Add a NcpVolume resource to the heartbeat configuration. This resource will make the NCP volume accessible to NCP clients and assigns an IP address to the NCP Server cluster resource name.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.