Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4 127
Package Configuration File Parameters
Before editing the package configuration file, assemble the following
information and enter it on the worksheet for each package. For more
details about each parameter, see the “Package Parameter Explanations”
on page 201; you may also want to generate and print out a complete
package configuration file; use a command such as:
cmmakepkg -m sg/all $SGCONF/sg-all
package_name The name of the package. The package name must be
unique in the cluster. It is used to start, stop, modify,
and view the package.
The package name can be from 1 to 39 characters; more
details in Chapter 6 under package_name (see page
201).
package_type The type of the package. This parameter indicates
whether the package will run on one node at a time or
on multiple nodes. Valid types are failover,
multi_node, and system_multi_node. Default is
failover. system_multi_node packages are
supported only for applications supplied by HP.
node_name The names of primary and alternate nodes for the
package. Enter a node_name for each node on which the
package can run.
The order in which you specify the node names is
important. First list the primary node name (the node
where you normally want the package to start), then
the first adoptive node name, then the second adoptive
node name, followed, in order of preference, by
additional node names. In case of a failover, control of
the package will be transferred to the next adoptive
node name listed in the package configuration file, or
(if that node is not available or cannot run the package
at that time) to the next node in the list, and so on.
(This behavior can be influenced by package
dependencies; see “About Package Dependencies” on
page 115.)
If all nodes in the cluster can run the package, and if
order is not important, you can specify: node_name *