Managing Serviceguard 14th Edition, June 2007

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4 165
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,” on page 271 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” on page 363.
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” on page 153. 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