Managing HP Serviceguard A.12.00.00 for Linux, June 2014

The following operations cannot be performed online:
• Changing at once both the mirror halves (xdc/xdc/raid_device_0[] and
xdc/xdc/raid_device_1[]) of an existing MD device (xdc/xdc/raid_device[]).
• Changing the service_name attribute of "raid_monitor" service when the serviceguard-xdc
package is running.
• Adding and deleting an MD device simultaneously.
• Add an MD device and replacing a mirror half in another existing MD device simultaneously.
• Deleteing an MD device and replacing a mirror half in another existing MD device
simultaneously.
• Replacing multiple mirror halves simultaneously while the package is running.
4.9.7 About Package Dependencies
A package can have dependencies on other packages, meaning the package will not start on a
node unless the packages it depends on are running on that node.
You can make a package dependent on any other package or packages running on the same
cluster node, subject to the restrictions spelled out in Chapter 6, under “dependency_condition”
(page 190).
Serviceguard adds two new capabilities: you can specify broadly where the package depended
on must be running, and you can specify that it must be down. These capabilities are discussed
later in this section under “Extended Dependencies” (page 115). You should read the next section,
“Simple Dependencies” (page 111), first.
4.9.7.1 Simple Dependencies
A simple dependency occurs when one package requires another to be running on the same node.
You define these conditions by means of the parameters dependency_condition and
dependency_location, using the literal values UP and same_node, respectively. (For detailed
configuration information, see the package parameter definitions starting with “dependency_name”
(page 190). For a discussion of complex dependencies, see “Extended Dependencies” (page 115).
Make a package dependent on another package if the first package cannot (or should not) function
without the services provided by the second. For example, pkg1 might run a real-time web interface
to a database managed by pkg2. In this case it might make sense to make pkg1 dependent on
pkg2.
In considering whether or not to create a dependency between packages, use the Rules for Simple
Dependencies and Guidelines for Simple Dependencies (page 115) that follow.
4.9.7.2 Rules for Simple Dependencies
Assume that we want to make pkg1 depend on pkg2.
NOTE: pkg1 can depend on more than one other package, and pkg2 can depend on another
package or packages; we are assuming only two packages in order to make the rules as clear as
possible.
4.9 Package Configuration Planning 111