Managing Serviceguard 12th Edition, March 2006

Configuring Packages and Their Services
Creating the Package Configuration
Chapter 6286
RESOURCE_START AUTOMATIC
RESOURCE_UP_VALUE = UP
• ACCESS_CONTROL_POLICY begins with Serviceguard version A.11.16.
With it, you can allow non-root users to monitor the cluster and to
administer packages. Configuration still requires root.
The only role in the package configuration file is that of
PACKAGE_ADMIN over the one configured package. Cluster-wide
roles are defined in the cluster configuration file.
There must be no 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 (use the cmgetconf command) before
creating any roles in the package’s file.
If a role is configured in the cluster, do not specify a role for the same
username/hostnode in the package configuration.
Data about Access Control Policies in the package configuration files
and the cluster configuration file are later combined in the binary
cluster configuration file.
See “Access Roles” on page 193 for more information.
• Simple package dependencies are a new feature in Serviceguard
A.11.17. At the release of Serviceguard A.11.17, dependencies are
only supported for use by applications specified by Hewlett-Packard,
such as the ones for clusters with the VERITAS Cluster File System.
This ensures that the failover application package will not start on a
node unless the CFS packages are already running on that node.
For example, if you have CFS installed, you can add a dependency to
your failover package configuration. There are three attributes;
specify them in this order:
— DEPENDENCY_NAME. Enter a unique name for your dependency.
— DEPENDENCY_CONDITION. The only condition supported in this
release is
pkg_name =UP. For a failover package that uses CFS
this is: SG-CFS-pkg = UP
— DEPENDENCY_LOCATION. For Serviceguard A.11.17, the only
location supported is SAME_NODE.