Chapter 6 Configuring Packages and Their Services

Table of Contents

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? ”, “How the Package Manager Works”, and “Package Configuration Planning ” 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 ”.

Creating or modifying a package requires the following broad steps, each of which is described in the sections that follow:

Decide on the package’s major characteristics and choose the modules you need to include (“Choosing Package Modules”).
Generate the package configuration file (“Generating the Package Configuration File”).
Edit the configuration file (“Editing the Configuration File”).
Verify and apply the package configuration (“Verifying and Applying the Package Configuration”).
Add the package to the cluster (“Adding the Package to the Cluster”).




	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.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”. 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”. 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 starting on “Optional Package Modules”.)

Technical documentation