HP Serviceguard for Linux Version A.11.18 Release Notes, 2nd Edition, March 2009
IMPORTANT: Serviceguard does not force you to use this new methodology. Existing
packages, known as legacy packages, continue to run without modification, and can
be maintained by means of the older methodology; see “Configuring a Legacy Package”
in Chapter 7 of Managing Serviceguard for Linux. You can also still create a new legacy
package. If you are using a Serviceguard Toolkit such as Serviceguard NFS Toolkit,
consult the documentation for that product.
The new modular method of creating packages provides the following benefits:
• All package parameters are now configured in one place, the package configuration
file.
You no longer need to create and distribute a separate package control file.
• External scripts offer an improved means of application integration.
These replace the Customer Defined Functions in the legacy package control script.
You do need to distribute these scripts to all the nodes that can run the package.
• The modular approach allows you to build a package from building blocks
containing only the functions needed by this package.
The subsections that follow provide more information. See also:
• Managing Serviceguard for Linux: “Package Configuration Planning” in Chapter 4;
and Chapter 6 “Configuring Packages and Their Services”
• The comments in the editable package configuration file output by the cmmakepkg
command, and the cmmakepkg manpage
Package Modules
The tables that follows show the new package modules and the configuration parameters
each module includes.
Base Package Modules
At least one base module (or default or all, which include the base module) must
be specified on the cmmakepkg command line. Parameters in bold are new for A.11.18
and are discussed under “New Parameters” (page 22).
What’s in this Release 19