ocf_heartbeat_eDir88(7)

1OCF_HEARTBEAT_EDIR88(7)       OCF resource agents      OCF_HEARTBEAT_EDIR88(7)
2
3
4

NAME

6       ocf_heartbeat_eDir88 - Manages a Novell eDirectory directory server
7

SYNOPSIS

9       eDir88 [start | stop | monitor | meta-data | validate-all]
10

DESCRIPTION

12       Resource script for managing an eDirectory instance. Manages a single
13       instance of eDirectory as an HA resource. The "multiple instances"
14       feature or eDirectory has been added in version 8.8. This script will
15       not work for any version of eDirectory prior to 8.8. This RA can be
16       used to load multiple eDirectory instances on the same host.
17
18       It is very strongly recommended to put eDir configuration files (as per
19       the eDir_config_file parameter) on local storage on each node. This is
20       necessary for this RA to be able to handle situations where the shared
21       storage has become unavailable. If the eDir configuration file is not
22       available, this RA will fail, and heartbeat will be unable to manage
23       the resource. Side effects include STONITH actions, unmanageable
24       resources, etc...
25
26       Setting a high action timeout value is _very_ _strongly_ recommended.
27       eDir with IDM can take in excess of 10 minutes to start. If heartbeat
28       times out before eDir has had a chance to start properly, mayhem _WILL
29       ENSUE_.
30
31       The LDAP module seems to be one of the very last to start. So this
32       script will take even longer to start on installations with IDM and
33       LDAP if the monitoring of IDM and/or LDAP is enabled, as the start
34       command will wait for IDM and LDAP to be available.
35

SUPPORTED PARAMETERS

37       eDir_config_file
38           Path to configuration file for eDirectory instance.  (unique,
39           optional, string, default /etc/opt/novell/eDirectory/conf/nds.conf)
40
41       eDir_monitor_ldap
42           Should we monitor if LDAP is running for the eDirectory instance?
43           (optional, boolean, default 0)
44
45       eDir_monitor_idm
46           Should we monitor if IDM is running for the eDirectory instance?
47           (optional, boolean, default 0)
48
49       eDir_jvm_initial_heap
50           Value for the DHOST_INITIAL_HEAP java environment variable. If
51           unset, java defaults will be used.  (optional, integer, no default)
52
53       eDir_jvm_max_heap
54           Value for the DHOST_MAX_HEAP java environment variable. If unset,
55           java defaults will be used.  (optional, integer, no default)
56
57       eDir_jvm_options
58           Value for the DHOST_OPTIONS java environment variable. If unset,
59           original values will be used.  (optional, string, no default)
60

SUPPORTED ACTIONS

62       This resource agent supports the following actions (operations):
63
64       start
65           Starts the resource. Suggested minimum timeout: 600.
66
67       stop
68           Stops the resource. Suggested minimum timeout: 600.
69
70       monitor
71           Performs a detailed status check. Suggested minimum timeout: 60.
72           Suggested interval: 30.
73
74       meta-data
75           Retrieves resource agent metadata (internal use only). Suggested
76           minimum timeout: 5.
77
78       validate-all
79           Performs a validation of the resource configuration. Suggested
80           minimum timeout: 5.
81

EXAMPLE

83       The following is an example configuration for a eDir88 resource using
84       the crm(8) shell:
85
86           primitive p_eDir88 ocf:heartbeat:eDir88 \
87             op monitor timeout="60" interval="30"
88

AUTHOR

93       Linux-HA contributors (see the resource agent source for information
94       about individual authors)
95
96
97
98resource-agents 3.9.2             07/08/2011           OCF_HEARTBEAT_EDIR88(7)