Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4124
Rules
Assume that we want to make pkg1 depend on pkg2.
NOTE pkg1 can depend on more than one other package, and pkg2 can depend
on another package or packages; we are assuming only two packages in
order to make the rules as clear as possible.
• pkg1 will not start on any node unless pkg2 is running on that node.
• pkg1’s package_type (see page 210) and failover_policy (see
page 214) constrain the type and characteristics of pkg2, as follows:
—If pkg1 is a multi-node package, pkg2 must be a multi-node or
system multi-node package. (Note that system multi-node
packages are not supported for general use.)
—If pkg1 is a failover package and its failover_policy is
min_package_node, pkg2 must be a multi-node or system
multi-node package.
—If pkg1 is a failover package and its failover_policy is
configured_node, pkg2 must be:
— a multi-node or system multi-node package, or
— a failover package whose failover_policy is
configured_node.
• pkg2 cannot be a failover package whose failover_policy is
min_package_node.
• pkg2’s node list (see node_name, page 210) must contain all of the
nodes on pkg1’s.
— Preferably the nodes should be listed in the same order if the
dependency is between packages whose failover_policy is
configured_node; cmcheckconf and cmapplyconf will warn you
if they are not.