Managing HP Serviceguard for Linux, Tenth Edition, September 2012

6 Configuring Packages and Their Services
Serviceguard packages group together applications and the services and resources they
depend on.
The typical Serviceguard package is a failover package that starts on one node but can
be moved (“failed over”) to another if necessary. For more information, see “What is
Serviceguard for Linux? ” (page 19), “How the Package Manager Works” (page 44),
and“Package Configuration Planning ” (page 120).
You can also create multi-node packages, which run on more than one node at the same
time.
System multi-node packages, which run on all the nodes in the cluster, are supported
only for applications supplied by HP.
Creating or modifying a package requires the following broad steps, each of which is
described in the sections that follow:
1. Decide on the package’s major characteristics and choose the modules you need
to include (page 200).
2. Generate the package configuration file (page 225).
3. Edit the configuration file (page 226).
4. Verify and apply the package configuration (page 230).
5. Add the package to the cluster (page 231).
NOTE: This is a new process for configuring packages, as of Serviceguard A.11.18.
This manual refers to packages created by this method as modular packages, and assumes
that you will use it to create new packages.
Packages created using Serviceguard A.11.16 or earlier are referred to as legacy
packages. If you need to reconfigure a legacy package (rather than create a new
package), see “Configuring a Legacy Package” (page 271).
It is also still possible to create new legacy packages by the method described in
“Configuring a Legacy Package”. If you are using a Serviceguard Toolkit, consult the
documentation for that product.
If you decide to convert a legacy package to a modular package, see “Migrating a
Legacy Package to a Modular Package” (page 281). Do not attempt to convert
Serviceguard Toolkit packages.
(Parameters that are in the package control script for legacy packages, but in the package
configuration file instead for modular packages, are indicated by (S) in the tables under
“Optional Package Modules” (page 203).)
199