Bug 229400 - Need better documentation of how to use hierarchical service definitions.
Need better documentation of how to use hierarchical service definitions.
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: rgmanager (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Lon Hohberger
Cluster QE
: Documentation
Depends On:
  Show dependency treegraph
Reported: 2007-02-20 15:46 EST by Neil Doane
Modified: 2009-04-16 16:22 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-01-29 15:18:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Neil Doane 2007-02-20 15:46:31 EST
Description of problem:
Customer has requested that we provide better documentation of how to use
hierarchical service definitions; that is, how to best construct and utilize the
existing supported functionality of nesting services to define dependent
relationships between resources within a service.

Specifically, information provided should demonstrate the order in which
resources are started and stopped (e.g. as from /usr/share/cluster/service.sh
meta-data) as well as provide examples of how to construct service definitions
that include dependent relationships between resources, esp. nested filesystem
mounts, IPs, and startup scripts.

Version-Release number of selected component (if applicable):
Any/All Applicable

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Lon Hohberger 2007-05-03 11:18:44 EDT
This has greatly been simplified with the introduction of #212121 to the RHEL4
branch; users can now run:

rg_test noop <configfile> <start|stop|status> service <servicename>

This will print out what rg_test would do if the operation was to occur - in
order - to stdout.  This will help users ensure they get the correct ordering
for their services.

Note that 212121 also makes resource ordering in cluster.conf a bit more obvious.
Comment 3 Michael Hideo 2007-10-22 22:52:28 EDT
Removing automation notification
Comment 4 Lon Hohberger 2008-01-29 15:18:25 EST

Note You need to log in before you can comment on or make changes to this bug.