HP Serviceguard manual Dependencylocation, Specifies where the dependencycondition must be met

dependency_location

Specifies where the dependency_condition must be met.

•If dependency_condition is UP, legal values fordependency_location are same_node, any_node, and different_node.

◦same_node means that the package depended on must be running on the same node.

◦different_node means that the package depended on must be running on a different node in this cluster.

◦any_node means that the package depended on must be running on some node in this cluster.

•If dependency_condition is DOWN, legal values fordependency_location are same_node andall_nodes.

◦same_node means that the package depended on must not be running on the same node.

◦all_nodes means that the package depended on must not be running on any node in this cluster.

For more information, see “About Package Dependencies” (page 137).

weight_name, weight_value

These parameters specify a weight for a package; this weight is compared to a node's available capacity (defined by the CAPACITY_NAME and CAPACITY_VALUE parameters in the cluster configuration file) to determine whether the package can run there.

Both parameters are optional, but if weight_value is specified, weight_name must also be specified, and must come first. You can define up to four weights, corresponding to four different capacities, per cluster. To specify more than one weight for this package, repeat weight_name and weight_value.

NOTE: But if weight_name is package_limit, you can use only that one weight and capacity throughout the cluster. package_limit is a reserved value, which, if used, must be entered exactly in that form. It provides the simplest way of managing weights and capacities; see “Simple Method” (page 145) for more information.

The rules for forming weight_name are the same as those for forming package_name (page 234). weight_name must exactly match the corresponding CAPACITY_NAME.

weight_value is an unsigned floating-point value between 0 and 1000000 with at most three digits after the decimal point.

You can use these parameters to override the cluster-wide default package weight that corresponds to a given node capacity. You can define that cluster-wide default package weight by means of the WEIGHT_NAME and WEIGHT_DEFAULT parameters in the cluster configuration file (explicit default). If you do not define an explicit default (that is, if you define a CAPACITY_NAME in the cluster configuration file with no corresponding WEIGHT_NAME and WEIGHT_DEFAULT), the default weight is assumed to be zero (implicit default). Configuring weight_name and weight_value here in the package configuration file overrides the cluster-wide default (implicit or explicit), and assigns a particular weight to this package.

For more information, see “About Package Weights” (page 144). See also the discussion of the relevant parameters under “Cluster Configuration Parameters ” (page 109), in the cmmakepkg (1m) and cmquerycl (1m) manpages, and in the cluster configuration and package configuration template files.

New for 11.19.

240 Configuring Packages and Their Services