Universal Logging System

This chapter describes the installation and configuration of the Script-CLuster.

Es wird das Paket u2webtools zum Betrieb des SCript-CLusters vorausgesetzt.

Die Datei rpm-Datei des SCript-CLusters auf den Zielrechner kopieren.

# rpm --install sccl-1.3-2.i586.rpm

There is no installable package for HP-UX, you must use a tar-ed version.

# cd /
# /usr/local/bin/tar xvzf /var/Software/sccl-HP-UX.1.2-4.tgz
/usr/local/bin/tar: Record size = 16 blocks
clusterlocks
etc/
etc/unix2web/
etc/unix2web/sccl.conf
etc/sccl/
...
usr/local/sccl/sccl_start_node
usr/local/sccl/sccl_test_res
var/
var/clusterlocks/

The configuration of the whole cluster is found in three ascii files

• sccl.conf
• packages.conf
• resources.conf

All files are located in

cd /etc/sccl/

This file is source'd, so be careful when editing.

Die Clusterpakete werden in der Datei, die durch PAKETE in der /etc/sccl/sccl.conf angegeben ist, definiert. Als Standard ist /etc/sccl/packages.conf festgelegt. Sie beinhaltet eine Tabelle mit allen Paketen des Clusters und die Clusterknoten, auf denen sie gestartet werden dürfen.

# vi /etc/sccl/packages.conf
package1 clnode1 clnode2
package2 - clnode2 clnode1
package3 - clnode2 clnode1

Jede Zeile hat die Form:

<package> { - | <stdnode> } [<altnode1> <altnode2> ...]

Das Clusterpaket <package> wird automatisch beim Start des Clusters auf seinem Standard-Clusterknoten <stdnode> gestartet und darf auf allen <altnodeX> laufen. Ein '-' anstelle von <stdnode> verhindert das automatische Starten des Clusterpakets beim Starten des Clusters oder des Clusterknotens.

The resources are configured in the file indicated by the (showing the default entry):

RESOURCES=/etc/sccl/resources.conf

entry in the /etc/sccl/sccl.conf.

The RESOURCES file contains all definitions of the resources belonging to the cluster packages.

It may also contain resource definitions belonging to sub-packages which are not listed as packages in the PACKAGES file but only used in the RESOURCES file. Sub-packages are used to bundle resources under one definition, which is useful if several packages make use of that sub-package. Sub-packages cannot be started stand-alone and they do not appear as package in the output of the sccl_show_cluster command and their status cannot be determined.

The resource definition must be in one line! The general syntax of a resource definition:

<package> <description_no_spaces> [MULTI] <resource> <resource> ...

When the package ist “started”, all resources are activated or started in the sequence the resources are given in the resource definition line (from left to right/forward).

When the package ist “stopped”, all resources are deactivated or stopped in the sequence the resources are given in the resource definition line (from right to left/backwards).

Link to examples

ip address

Start only, if a specific process is running.

Start only if specific processes are not running.

A raw partition.

Mount a file system.

Mount a file system group.

This resource type is rarely used as it needs a file system group definition based on specific remarks in the /etc/fstab file.

Mount an NFS file system.

Mount a group of NFS file systems.

This resource type is rarely used as it needs a file system group definition based on specific remarks in the /etc/fstab file.

The sub-package (resource) will be started when needed by the first package and it is stopped when the last package, that the sub-package is used by, is stopped.

Execute a script to start or stop the package.

A specific cluster packages must be active in the cluster.

on which cluster node?