ocf:CTDB — CTDB Resource Agent
OCF_RESKEY_ctdb_recovery_lock=string [OCF_RESKEY_ctdb_manages_samba=boolean] [OCF_RESKEY_ctdb_manages_winbind=boolean] [OCF_RESKEY_ctdb_service_smb=string] [OCF_RESKEY_ctdb_service_nmb=string] [OCF_RESKEY_ctdb_service_winbind=string] [OCF_RESKEY_ctdb_samba_skip_share_check=boolean] [OCF_RESKEY_ctdb_monitor_free_memory=integer] [OCF_RESKEY_ctdb_start_as_disabled=boolean] [OCF_RESKEY_ctdb_config_dir=string] [OCF_RESKEY_ctdb_binary=string] [OCF_RESKEY_ctdbd_binary=string] OCF_RESKEY_ctdb_socket=string OCF_RESKEY_ctdb_dbdir=string [OCF_RESKEY_ctdb_logfile=string] [OCF_RESKEY_ctdb_debuglevel=integer] [OCF_RESKEY_smb_conf=string] OCF_RESKEY_smb_private_dir=string [OCF_RESKEY_smb_passdb_backend=string] [OCF_RESKEY_smb_idmap_backend=string] [OCF_RESKEY_smb_fileid_algorithm=string] CTDB [start | stop | monitor | meta-data | validate-all]
This resource agent manages CTDB, allowing one to use Clustered Samba in a Linux-HA/Pacemaker cluster. You need a shared filesystem (e.g. OCFS2) on which the CTDB lock will be stored. Create /etc/ctdb/nodes containing a list of private IP addresses of each node in the cluster, then configure this RA as a clone. To have CTDB manage Samba, set ctdb_manages_samba="yes". Note that this option will be deprecated in future, in favour of configuring a separate Samba resource. For more information see http://linux-ha.org/wiki/CTDB_(resource_agent)
The location of a shared lock file, common across all nodes. This must be on shared storage, e.g.: /shared-fs/samba/ctdb.lock
Should CTDB manage starting/stopping the Samba service for you? This will be deprecated in future, in favor of configuring a separate Samba resource.
Should CTDB manage starting/stopping the Winbind service for you? This will be deprecated in future, in favor of configuring a separate Winbind resource.
Name of smb init script. Only necessary if CTDB is managing Samba directly. Will usually be auto-detected.
Name of nmb init script. Only necessary if CTDB is managing Samba directly. Will usually be auto-detected.
Name of winbind init script. Only necessary if CTDB is managing Winbind directly. Will usually be auto-detected.
If there are very many shares it may not be feasible to check that all of them are available during each monitoring interval. In that case this check can be disabled.
If the amount of free memory drops below this value the node will become unhealthy and ctdb and all managed services will be shutdown. Once this occurs, the administrator needs to find the reason for the OOM situation, rectify it and restart ctdb with "service ctdb start".
When set to yes, the CTDB node will start in DISABLED mode and not host any public ip addresses.
The directory containing various CTDB configuration files. The "nodes" and "notify.sh" scripts are expected to be in this directory, as is the "events.d" subdirectory.
Full path to the CTDB binary.
Full path to the CTDB cluster daemon binary.
Full path to the domain socket that ctdbd will create, used for local clients to attach and communicate with the ctdb daemon.
The directory to put the local CTDB database files in. Persistent database files will be put in ctdb_dbdir/persistent.
Full path to log file. To log to syslog instead, use the value "syslog".
What debug level to run at (0-10). Higher means more verbose.
Path to default samba config file. Only necessary if CTDB is managing Samba.
The directory for smbd to use for storing such files as smbpasswd and secrets.tdb. Old versions of CTBD (prior to 1.0.50) required this to be on shared storage. This parameter should not be set for current versions of CTDB, and only remains in the RA for backwards compatibility.
Which backend to use for storing user and possibly group information. Only necessary if CTDB is managing Samba.
Which backend to use for SID/uid/gid mapping. Only necessary if CTDB is managing Samba.
Which fileid:algorithm to use with vfs_fileid. The correct value depends on which clustered filesystem is in use, e.g.: for OCFS2, this should be set to "fsid". Only necessary if CTDB is managing Samba.