Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Configuring Packages and Their Services
Creating the Package Configuration
Chapter 6 187
• If the package depends on monitored devices, be sure to include
separate service entries (SERVICE_NAME DiskMond) for disk
monitoring and include the resclient command as the
SERVICE_CMD in the control script.
• If your package has IP addresses associated with it, enter the
SUBNET. This must be a subnet that is already specified in the cluster
configuration.
• NODE_FAIL_FAST_ENABLED parameter. Enter YES or NO.
Access Control Policy is a new feature with Serviceguard version
A.11.16. With it, you can allow non-root users to administer packages
and clusters. Cluster-wide roles are defined in the cluster configuration
file. Package-specific roles are defined in the package configuration file.
There must be no redundancy or conflict in roles. If there is,
configuration will fail and you will get a message. It is a good idea,
therefore, to look at the cluster configuration file (cmgetconf) before
creating any roles in the package’s file.
If a role is configured in the cluster, do not configure a role for the same
username/hostnode in the package. The exception is wildcards. For
example, if there were a MONITOR role for ANY_USER from ftsys9 in the
cluster configuration, and you created an ADMIN role for user Lee from
ftsys9 in the package configuration file, ANY_USER from ftsys9 would
have the role of PACKAGE_ADMIN for this policy. (This role already
includes the MONITOR role for the entire cluster.)
This package configuration data is later combined with the cluster
configuration data in the binary cluster configuration file.