Managing Serviceguard A.11.20, March 2013

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. See “What is Serviceguard? ” (page 21), “How the Package
Manager Works” (page 50), and “Package Configuration Planning ” (page 131) for more
information.
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.
Before you begin, make sure you have done the necessary planning; see “Package Configuration
Planning ” (page 131).
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 232)).
2. Generate the package configuration file (page 258).
3. Edit the configuration file (page 259).
4. Verify and apply the package configuration (page 263).
5. Add the package to the cluster (page 264).
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; it is simpler and more efficient than the older method, allowing you to
build packages from smaller modules, and eliminating the separate package control script and
the need to distribute it manually.
If you want to create new modular CFS packages, see “Creating Modular Disk Group and Mount
Point Packages” (page 210).
Packages created using Serviceguard A.11.17 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 307).
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 such as Serviceguard NFS 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 316). Do not attempt to convert Serviceguard Toolkit packages.
If you decide to convert a legacy CFS package to a modular CFS package, see “Migrating from
Legacy CFS Packages to Modular CFS Packages ” (page 383).
If you want to convert from EMS resources to generic resources, see “Migrating EMS Resources to
Generic Resources” (page 402).
(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 later in this
section (page 236).)
Choosing Package Modules
IMPORTANT: Before you start, you need to do the package-planning tasks described under
“Package Configuration Planning ” (page 131).
232 Configuring Packages and Their Services