Managing HP Serviceguard A.11.20.10 for Linux, December 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 41), and“Package Configuration Planning
” (page 100).
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 163).
2. Generate the package configuration file (page 185).
3. Edit the configuration file (page 186).
4. Verify and apply the package configuration (page 189).
5. Add the package to the cluster (page 191).
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.
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 225).
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 232). 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 166)).
6.1 Choosing Package Modules
IMPORTANT: Before you start, you need to do the package-planning tasks described under
“Package Configuration Planning ” (page 100).
To choose the right package modules, you need to decide the following things about the package
you are creating:
• What type of package it is; see “Types of Package: Failover, Multi-Node, System Multi-Node”
(page 164).
• Which parameters need to be specified for the package (beyond those included in the base
type, which is normally failover, multi-node, or system-multi-node). See “Package Modules
and Parameters” (page 165).
6.1 Choosing Package Modules 163