Managing HP Serviceguard A.11.20.10 for Linux, December 2012

name for a weight that exactly corresponds to a
CAPACITY_NAME specified earlier in the cluster
configuration file. (A package has weight; a node has
capacity.) The rules for forming WEIGHT_NAME are the same
as those spelled out for CAPACITY_NAME earlier in this list.
These parameters are optional, but if they are defined,
WEIGHT_DEFAULT must follow WEIGHT_NAME, and must
be set to a floating-point value between 0 and 1000000.
If they are not specified for a given weight, Serviceguard
will assume a default value of zero for that weight. In either
case, the default can be overridden for an individual
package via the weight_name and weight_value
parameters in the package configuration file.
For more information and examples, see “Defining Weights”
(page 119).
IMPORTANT: CAPACITY_NAME, WEIGHT_NAME, and
weight_value must all match exactly.
NOTE: A weight (WEIGHT_NAME, WEIGHT_DEFAULT)
has no meaning on a node unless a corresponding capacity
(CAPACITY_NAME, CAPACITY_VALUE) is defined for that
node.
For the reserved weight and capacity package_limit,
the default weight is always one. This default cannot be
changed in the cluster configuration file, but it can be
overridden for an individual package in the package
configuration file.
cmapplyconf will fail if you define a default for a weight
but do not specify a capacity of the same name for at least
one node in the cluster. You can define a maximum of four
WEIGHT_DEFAULTs per cluster.
Can be changed while the cluster is running.
(Access Control Policies) Specify three things for each policy: USER_NAME,
USER_HOST, and USER_ROLE. Policies set in the
configuration file of a cluster and its packages must not be
conflicting or redundant. For more information, see
“Controlling Access to the Cluster” (page 152).
MAX_CONFIGURED_PACKAGES This parameter sets the maximum number of packages that
can be configured in the cluster. The minimum value is 0,
and the maximum value, which is also the default, is 300.
Can be changed while the cluster is running.
4.7.5 Cluster Configuration: Next Step
When you are ready to configure the cluster, proceed to “Configuring the Cluster” (page 147). If
you find it useful to record your configuration ahead of time, use the Cluster Configuration worksheet
(page 275).
4.7 Cluster Configuration Planning 99