Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4 115
Create an entry for each logical volume, indicating its use for a file
system or for a raw device.
CAUTION Do not use /etc/fstab to mount file systems that are used by
Serviceguard packages.
For information about creating, exporting, and importing volume groups,
see “Creating the Logical Volume Infrastructure” on page 163.
Planning for Expansion
You can add packages to a running cluster. This process is described in
Chapter 7, “Cluster and Package Maintenance,” on page 229.
When adding packages, be sure not to exceed the value of
max_configured_packages as defined in the cluster configuration file
(see “Cluster Configuration Parameters” on page 106). You can modify
this parameter while the cluster is running if you need to.
Choosing Failover Behavior
To determine failover behavior, you can define a package failover policy
that governs which nodes will automatically start up a package that is
not running. In addition, you can define a failback policy that determines
whether a package will be automatically returned to its primary node
when that is possible.
Table 3-3 (page 56) describes different types of failover behavior and how
to set the parameters that determine each behavior.
About Package Dependencies
A package can have dependencies on other packages, meaning the
package will not start on a node unless the packages it depends on are
running on that node.
You can make a package dependent on any other package or packages
running on the same cluster node, subject to the restrictions spelled out
in Chapter 6, under dependency_condition (see page 207).