Provided by: cman_3.0.2-2ubuntu1_i386 bug

NAME

       cluster.conf - configuration file for cman, fence, dlm, gfs, rgmanager

DESCRIPTION

       The /etc/cluster/cluster.conf file contains configuration for:

       cman(5) for corosync and quorum configuration
       qdisk(5) for quorum disk configuration
       groupd(8) for daemon configuration
       fenced(8) for daemon and fence device configuration
       dlm_controld(8) for daemon configuration
       gfs_controld(8) for daemon configuration
       rgmanager(8) for daemon and resource configuration

       The same cluster.conf file must exist on each cluster node.

       When cman_tool starts corosync, the contents of cluster.conf are loaded
       into the corosync in-memory configuration database  (confdb).   Daemons
       and  programs  listed above use the libccs library to read cluster.conf
       data from the corosync confdb.  (The libconfdb library can also be used
       for more general, non-xml confdb queries.)

       When  cman  configures  corosync  using cluster.conf, the corosync.conf
       file is not used.

   Cluster Nodes
       cluster.conf is an XML file.  It  has  one  top-level  cluster  section
       containing  everything  else.   The  cluster  section has two mandatory
       attributes: name and config_version.  name can be up to  15  characters
       long  (16  including  terminating  null)  and specifies the name of the
       cluster.  It is important that this name be unique  among  clusters  on
       the  same  network.   config_version  is  a number used to identify the
       revision level of the cluster.conf file.

         <cluster name="alpha" config_version="1">
         </cluster>

       The set of nodes that  make  up  the  cluster  are  defined  under  the
       clusternodes  section.   A  clusternode  section  defines each node.  A
       clusternode has two mandatory attributes: name and nodeid

       The name should correspond to the hostname (the fully qualified name is
       generally  not  necessary)  on  the  network  interface  to be used for
       cluster communication.  Nodeid’s must be greater than zero and  unique.

         <cluster name="alpha" config_version="1">
                 <clusternodes>
                         <clusternode name="node-01" nodeid="1">
                         </clusternode>

                         <clusternode name="node-02" nodeid="2">
                         </clusternode>

                         <clusternode name="node-03" nodeid="3">
                         </clusternode>
                 </clusternodes>
         </cluster>

   Logging
       All  daemons  listed  above  use  the  <logging>  section  to configure
       loggging.  Global settings apply to all:

         <logging debug="on"/>

       Per-daemon  settings  override  the   corresponding   global   setting.
       logging_daemon  names that can be configured include: corosync, qdiskd,
       groupd, fenced, dlm_controld, gfs_controld, rgmanager.

         <logging>
             <logging_daemon name="qdiskd" debug="on"/>
             <logging_daemon name="fenced" debug="on"/>
         </logging>

       corosync daemon settings apply to all corosync subsystems  by  default,
       but subsystems can also be configured individually.  These include CLM,
       CPG, MAIN, SERV, CMAN, TOTEM, QUORUM, CONFDB, CKPT, EVT.

         <logging>
             <logging_daemon name="corosync" subsys="QUORUM" debug="on"/>
             <logging_daemon name="corosync" subsys="CONFDB" debug="on"/>
         </logging>

       Settings
       The settings available at global, daemon and subsystem levels are:

       to_syslog
       enable/disable messages to syslog (yes/no)
       default "yes"

       to_logfile
       enable/disable messages to log file (yes/no)
       default "yes"

       syslog_facility
       facility used for syslog messages
       default "daemon"

       syslog_priority
       messages at this level and up will be sent to syslog
       default "info"

       logfile_priority
       messages at this level and up will be written to log file
       default "info"

       logfile
       the log file name, default /var/log/cluster/<daemon>.log

       debug="on"
       is a shortcut for logfile_priority="debug"

       Defaults
       An explicit configuration for the default settings would be:

       <logging to_syslog="yes" to_logfile="yes" syslog_facility="daemon"
                syslog_priority="info" logfile_priority="info">
           <logging_daemon name="qdiskd"
                    logfile="/var/log/cluster/qdiskd.log"/>
           <logging_daemon name="groupd"
                    logfile="/var/log/cluster/groupd.log"/>
           <logging_daemon name="fenced"
                    logfile="/var/log/cluster/fenced.log"/>
           <logging_daemon name="dlm_controld"
                    logfile="/var/log/cluster/dlm_controld.log"/>
           <logging_daemon name="gfs_controld"
                    logfile="/var/log/cluster/gfs_controld.log"/>
           <logging_daemon name="rgmanager"
                    logfile="/var/log/cluster/rgmanager.log"/>
           <logging_daemon name="corosync"
                    logfile="/var/log/cluster/corosync.log"/>
       </logging>

       Examples
       To include debug messages (and above) from all daemons in their default
       log files, either
              <logging debug="on"/> or <logging logfile_priority="debug"/>

       To exclude all log messages from syslog
              <logging to_syslog="no"/>

       To disable logging to all log files
              <logging to_file="no"/>

       To include debug messages (and above) from all daemons in syslog
              <logging syslog_priority="debug"/>

       To limit syslog messages to error (and above), keeping info (and above)
       in log files (this logfile_priority setting is the default so could  be
       omitted)
              <logging syslog_priority="error" logfile_priority="info"/>

SEE ALSO

       cman(5),     qdisk(5),     groupd(8),    fenced(8),    dlm_controld(8),
       gfs_controld(8), rgmanager(8)

                                                               cluster.conf(5)