Resource script for managing an eDirectory instance. Manages a single instance of eDirectory as an HA resource. The "multiple instances" feature or eDirectory has been added in version 8.8. This script will not work for any version of eDirectory prior to 8.8. This RA can be used to load multiple eDirectory instances on the same host.
It is very strongly recommended to put eDir configuration files (as per the eDir_config_file parameter) on local storage on each node. This is necessary for this RA to be able to handle situations where the shared storage has become unavailable. If the eDir configuration file is not available, this RA will fail, and heartbeat will be unable to manage the resource. Side effects include STONITH actions, unmanageable resources, etc...
Setting a high action timeout value is _very_ _strongly_ recommended. eDir with IDM can take in excess of 10 minutes to start. If heartbeat times out before eDir has had a chance to start properly, mayhem _WILL ENSUE_.
The LDAP module seems to be one of the very last to start. So this script will
take even longer to start on installations with IDM and LDAP if the monitoring
of IDM and/or LDAP is enabled, as the start command will wait for IDM and LDAP
to be available.
Path to configuration file for eDirectory instance. (optional, string, default
Should we monitor if LDAP is running for the eDirectory instance? (optional, boolean, default
Should we monitor if IDM is running for the eDirectory instance? (optional, boolean, default
Value for the DHOST_INITIAL_HEAP java environment variable. If unset, java defaults will be used. (optional, integer, no default)
Value for the DHOST_MAX_HEAP java environment variable. If unset, java defaults will be used. (optional, integer, no default)
Value for the DHOST_OPTIONS java environment variable. If unset, original values will be used. (optional, string, no default)
This resource agent supports the following actions (operations):
Starts the resource. Suggested minimum timeout: 600.
Stops the resource. Suggested minimum timeout: 600.
Performs a detailed status check. Suggested minimum timeout: 60. Suggested interval: 30.