Red Hat Bugzilla – Bug 229400
Need better documentation of how to use hierarchical service definitions.
Last modified: 2009-04-16 16:22:09 EDT
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):
Steps to Reproduce:
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.
Removing automation notification