Using Serviceguard Node Capacities and Package Weights, April 2009

10
Solution 3
This solution combines solutions 1 and 2. It allows you to assign the same capacity/weight values as
solution1 and use a default package weight so you do not need to change configuration files for
pkg2-pkg4. You can define your own capacity name, say “node_resources” and define a
weight_default of 20 (equal to the required weight of pkg2-pkg4) for that capacity.
The following table shows the relevant portions of the configuration files for the cluster and the
packages:
Table 6: Configuration for solution 3
Cluster configuration
file:
Node capacity and
weight default
definition
CLUSTER_NAME cluster_23
...
#
# node1 has capacity value of 80 for capacity
# node_resources
#
NODE_NAME node1
...
CAPACITY_NAME node_resources
CAPACITY_VALUE 80
#
# node2 has a capacity of 40 for capacity
# node_resources
#
NODE_NAME node2
...
CAPACITY_NAME node_resources
CAPACITY_VALUE 40
...
#
# package default weight for capacity/weight
# node_resources.
# 20 is the weight value for packages that
# do not specify a package weight.
#
WEIGHT_NAME node_resources
WEIGHT_DEFAULT 20
Package configuration
file for pkg1:
Weight definition
package_name pkg1
...
weight_name node_resources
weight_value 40
Package configuration
file for pkg5:
Weight definition
package_name pkg5
...
weight_name node_resources
weight_value 10