Managing HP Serviceguard A.12.00.00 for Linux, June 2014

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 169).
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.8.5 Cluster Configuration: Next Step
When you are ready to configure the cluster, proceed to “Configuring the Cluster” (page 164). If
you find it useful to record your configuration ahead of time, use the Cluster Configuration worksheet
(page 301).
4.9 Package Configuration Planning
Planning for packages involves assembling information about each group of highly available
services.
The document HP Serviceguard Developer’s Toolbox User Guide, December 2012 provides a
guide for integrating an application with Serviceguard using a suite of customizable scripts known
as "Serviceguard Developer’s Toolbox" intended for use with modular packages only. The
“Serviceguard Developer’s Toolbox” is available free of charge and can be downloaded from
Software Depot at http://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?
productNumber=SGDTOOLBOX.
4.9.1 Logical Volume and File System Planning
Use logical volumes in volume groups as the storage infrastructure for package operations on a
cluster. When the package moves from one node to another, it must still be able to access the
same data on the same disk as it did when it was running on the previous node. This is accomplished
by activating the volume group and mounting the file system that resides on it.
In Serviceguard, high availability applications, services, and data are located in volume groups
that are on a shared bus. When a node fails, the volume groups containing the applications,
services, and data of the failed node are deactivated on the failed node and activated on the
adoptive node (the node the packages move to). In order for this to happen, you must configure
the volume groups so that they can be transferred from the failed node to the adoptive node.
4.9 Package Configuration Planning 103