Managing HP Serviceguard A.11.20.10 for Linux, December 2012

to move; see “How Package Weights Interact with Package Priorities and Dependencies”
(page 121)). This is true whenever a package has a weight that exceeds the available amount
of the corresponding capacity on the node.
4.8.10.5 Rules and Guidelines
The following rules and guidelines apply to both the Simple Method (page 116) and the
Comprehensive Method (page 117) of configuring capacities and weights.
• You can define a maximum of four capacities, and corresponding weights, throughout the
cluster.
NOTE: But if you use the reserved CAPACITY_NAME package_limit, you can define
only that single capacity and corresponding weight. See “Simple Method” (page 116).
• Node capacity is defined in the cluster configuration file, via the CAPACITY_NAME and
CAPACITY_VALUE parameters.
• Capacities can be added, changed, and deleted while the cluster is running. This can cause
some packages to be moved, or even halted and not restarted.
• Package weight can be defined in cluster configuration file, via the WEIGHT_NAME and
WEIGHT_DEFAULT parameters, or in the package configuration file, via the weight_name
and weight_value parameters, or both.
• Weights can be assigned (and WEIGHT_DEFAULTs, apply) only to multi-node packages and
to failover packages whose failover_policy (page 172) is configured_node and whose
failback_policy (page 173) is manual.
• If you define weight (weight_name and weight_value) for a package, make sure you
define the corresponding capacity (CAPACITY_NAME and CAPACITY_VALUE) in the cluster
configuration file for at least one node on the package's node_name list (page 170). Otherwise
cmapplyconf will fail when you try to apply the package.
• Weights (both cluster-wide WEIGHT_DEFAULTs, and weights defined in the package
configuration files) can be changed while the cluster is up and the packages are running. This
can cause some packages to be moved, or even halted and not restarted.
4.8.10.6 For More Information
For more information about capacities, see the comments under CAPACITY_NAME and
CAPACITY_VALUE in:
• the cluster configuration file
• the cmquerycl (1m) manpage
• the section “Cluster Configuration Parameters ” (page 86) in this manual.
For more information about weights, see the comments under weight_name and weight_value
in:
• the package configuration file
• the cmmakepkg (1m) manpage
• the section “Package Parameter Explanations” (page 168) in this manual.
For further discussion and use cases, see the white paper Using Serviceguard’s Node Capacity
and Package Weight Feature at http://www.hp.com/go/linux-serviceguard-docs.
4.8.10.7 How Package Weights Interact with Package Priorities and Dependencies
If necessary, Serviceguard will halt a running lower-priority package that has weight to make room
for a higher-priority package that has weight. But a running package that has no priority (that is,
4.8 Package Configuration Planning 121