Managing Serviceguard Eighteenth Edition, September 2010

Package Configuration Planning
Planning for packages involves assembling information about each group of highly
available services.
NOTE: As of Serviceguard A.11.18, there is a new and simpler way to configure
packages. This method allows you to build packages out of smaller modules, and
eliminates the separate package control script and the need to distribute it manually;
see Chapter 6: “Configuring Packages and Their Services ” (page 279) for complete
instructions.
This manual refers to packages produced by the newer method as modular packages,
and to packages produced by the older method as legacy packages.
The discussion that follows assumes you will be using the modular method. For
information and instructions on creating and maintaining older packages, see
“Configuring a Legacy Package” (page 375).
The document Framework for HP Serviceguard Toolkits provides a guide to integrating
an application with Serviceguard, and includes a suite of customizable scripts intended
for use with legacy packages. This document is included in the Serviceguard Developers
Toolbox, which you can download free of charge
fromhttp://www.hp.com/go/softwaredepot.
NOTE: As of the date of this manual, the Framework for HP Serviceguard Toolkits deals
specifically with legacy packages.
Logical Volume and File System Planning
NOTE: LVM Volume groups that are to be activated by packages must also be defined
as cluster-aware in the cluster configuration file. See “Cluster Configuration Planning
” (page 135). Disk groups (for Veritas volume managers) that are to be activated by
packages must be defined in the package configuration file, described below.
You may need to use logical volumes in volume groups as part of the infrastructure
for package operations on a cluster. When the package moves from one node to another,
it must be able to access data residing on the same disk as on the previous node. This
is accomplished by activating the volume group and mounting the file system that
resides on it.
In Serviceguard, high availability applications, services, and data are located in volume
groups that are on a shared bus. When a node fails, the volume groups containing the
applications, services, and data of the failed node are deactivated on the failed node
and activated on the adoptive node. In order for this to happen, you must configure
the volume groups so that they can be transferred from the failed node to the adoptive
node.
168 Planning and Documenting an HA Cluster