Nodeware installation

Package

Download the lastest 'opensvc' package available for your operating system of choice from http://repo.opensvc.com and install it. Depending on the operating system, and operating system version, you might need to satisfy dependencies using packages provided on this website.

The package post-installation steps are handled by the /opt/opensvc/bin/postinstall script. This script can be safely executed on a node where opensvc is already installed.

Files

The package installs the following directory tree:

/opt/opensvc/
/opt/opensvc/etc
/opt/opensvc/tmp
/opt/opensvc/bin
/opt/opensvc/bin/pkg
/opt/opensvc/bin/cron
/opt/opensvc/var
/opt/opensvc/var/sync
/opt/opensvc/var/lock
/opt/opensvc/usr
/opt/opensvc/usr/share
/opt/opensvc/usr/share/doc
/opt/opensvc/lib
/opt/opensvc/log

Cron jobs

The package installs the following cron jobs, in (by order of preference), /etc/cron.d/opensvc, /var/spool/cron/crontabs/root, /var/spool/cron/root :

0,10,20,30,40,50 * * * * [ -x /opt/opensvc/bin/svcmon ] && /opt/opensvc/bin/svcmon --updatedb >/dev/null 2>&1
0 4 * * * [ -x /opt/opensvc/bin/cron/opensvc.daily ] && /opt/opensvc/bin/cron/opensvc.daily >/dev/null 2>&1

Keys

If the root account has no ssh key, a 1024 bits dsa key is generated by the package post-install. Production node keys must be trusted on all cluster nodes (PRD and DRP), whereas the keys of disaster recovery servers must not be trusted by production nodes. This setup is used for rsync file transfers and remote command execution.

Set host mode

The valid host mode values are PRD, DEV, TMP. The setting is stored in /opt/opensvc/var/host_mode. No comments are allowed in this file.

The host_mode setting is used to enforce the following policies:

• Only PRD services are allowed to start on a PRD node

• Only PRD nodes are allowed to push data to a PRD node

Configuration for collector usage

The collector is contacted by the node using the generic name dbopensvc. This name should be known to your prefered resolving mecanism : hosts, dns, ... If you choose to use the internet shared collector, the corresponding ip adress must be set to the adress of collector.opensvc.com.

You can accelerate the node discovery by forcing the execution of both opensvc cronjobs after the package installation.

HP-UX specificities

The python package provided by HP will output garbage on exec because it won't find terminfo at the expected places. To fix that, you have to export TERMINFO=/usr/share/lib/terminfo from /etc/profile

The HP-UX base system does not provide tools to handle scsi persistent reservations. You have to install the scu tool if you want to activate this feature.

Linux LVM2 specificities

Opensvc controls volume group activation and desactivation. Most Linux distributions activate all visible volume groups at boot, some even re-activate them upon de-activation events. These mecanisms can be disabled using the following setup. It also provides another protection against unwanted volume group activation from a secondary cluster node.

This setup tells LVM2 commands to activate only the objects tagged with the hostname. Opensvc makes sure the tags are set on start and unset on stop. Opensvc also purges all tags before adding the one it needs to activate a volume group, so opensvc can satisfy a start request on a service uncleanly shut down.

/etc/lvm/lvm.conf

Add the following root-level configuration node

tags {
    hosttags = 1
    local {}
}

And add the 'local' tag to all local volume groups. For example:

vgchange --addtag local rootvg

Finally you need to rebuild the initrd/initramfs to prevent shared vg activation at boot.

/etc/lvm/lvm_{node}.conf

Create this file, {node} being the output of uname -n and add the following configuration.

activation { volume_list = ["@{node}"] }