Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4130
The alternative policy is min_package_node, which
tells the package manager to select (from the list of
nodes that can run this package) the node that is
running the fewest packages.
See also “About Package Dependencies” on page 115.
failback_policy
The policy used to determine what action the package
manager should take if a failover package is not
running on its primary node (the first node on its
node_name list) and its primary node is capable of
running the package.
Default is manual, which means no attempt will be
made to move the package back to its primary node
when it is running on an alternate node. The alternate
policy is automatic, which means that the package will
be halted and restarted on its primary node as soon as
the primary node is capable of running the package. (If
the failover policy is min_package_node is, failback
cannot occur until the primary node is running fewer
packages than the current node.)
See also “About Package Dependencies” on page 115.
priority Assigns a priority to the package. Used to decide
whether a package can “drag” another package it
depends on to another node. See “About Package
Dependencies” on page 115.
Valid values are 1 through 3000, or no_priority. The
default is no_priority.
If you assign a priority, it must be unique in this
cluster. A lower number indicates a higher priority.
It is a good idea to assign values in increments of 20 so
as to leave gaps in the sequence; otherwise you may
have to shuffle all the existing priorities when
assigning priority to a new package.
More details in Chapter 6, under priority (see page
206). See also “About Package Dependencies” on
page 115.