Managing HP Serviceguard A.12.00.00 for Linux, June 2014

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 103).
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 179).
2. Generate the package configuration file (page 201).
3. Edit the configuration file (page 202).
4. Verify and apply the package configuration (page 206).
5. Add the package to the cluster (page 208).
6.1 Choosing Package Modules
IMPORTANT: Before you start, you need to do the package-planning tasks described under
“Package Configuration Planning” (page 103).
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 179).
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 180).
When you have made these decisions, you are ready to generate the package configuration file;
see “Generating the Package Configuration File” (page 201).
6.1.1 Types of Package: Failover, Multi-Node, System Multi-Node
There are three types of packages:
Failover packages. This is the most common type of package. Failover packages run on one
node at a time. If there is a failure, Serviceguard (or a user) can halt them, and then start them
up on another node selected from the package’s configuration list; see node_name (page 186).
To generate a package configuration file that creates a failover package, include-m
sg/failover on the cmmakepkg command line. See “Generating the Package Configuration
File” (page 201).
Multi-node packages. These packages run simultaneously on more than one node in the cluster.
Failures of package components such as applications, services, generic resource, or subnets,
will cause the package to be halted only on the node on which the failure occurred.
Relocatable IP addresses cannot be assigned to multi-node packages.
6.1 Choosing Package Modules 179