Modular package support in Serviceguard for Linux Toolkits, August 2008

Setting up a modular package

With the legacy method of packaging, the user had to configure three scripts: the package

configuration script, the package control script and the toolkit configuration file. With the

introduction of the modular method of packaging, the user has to modify only one file – the

package configuration file.

The package configuration file contains Serviceguard for Linux-specific parameters that need to be

configured appropriately by the user. The package configuration file also has service parameters

and some toolkit specific pre-configured default parameters. This simplifies configuration of a

package for the user.

For example, the service parameters in the package configuration file created on SLES with the

apache module included will be preset with the below values:

service_name service_apache

service_cmd “/opt/cmcluster/conf/scripts/tkit/apache/tkit_module.sh apache_monitor”

Please refer to Chapter 6 of the document Managing Serviceguard Fifteenth Edition December

2007 for details on how to modify the package configuration file. You can find this document in

the location http://docs.hp.com -> High Availability -> Serviceguard.

Creating the package

The user creates a package configuration file in their chosen location, such as /tmp, and then

modifies it. He/She then needs to configure the parameter TKIT_DIR in the package configuration

file, the Serviceguard for Linux parameters and the toolkit configuration parameters. The modified

package configuration file then needs to be applied. The steps for setting up a package are as

follows:

Note:

For illustration purposes, HP Apache is taken as example. Configuration of other toolkits will also

follow along similar lines unless mentioned otherwise.

1) #cmmakepkg –m tkit/apache/apache pkg.conf

Creates the package configuration file 'pkg.conf' by including the toolkit ADF attributes which

need to be configured later by the user for all necessary parameters including TKIT_DIR.

2) Configure all the required package parameters including TKIT_DIR.

Note: Kindly refer the README documents of the toolkit for assistance on how to configure the

toolkit specific parameters.

Also refer to the whitepaper Migrating Packages from Legacy to Modular Style, October 2007 for

more information. You can find this whitepaper at http://docs.hp.com -> High Availability ->

Serviceguard -> White Papers.

3) #cmapplyconf –P pkg.conf

This command ‘applies’ the package configuration to the CDB (Serviceguard Configuration

Database). It also creates toolkit configuration directory defined by TKIT_DIR, if not already

created and then creates the toolkit configuration file in it with the values specified in the pkg.conf

file.