4.3. Cluster configuration

Drbdmanage knows many configuration settings like the log-level or the storage plugin that should be used (i.e., LVM, ThinLV, ThinPool, ZPool, or ThinZpool). Executing drbdmanage modify-config starts an editor that is used to specify theses settings. The configuration is split in several sections. If an option is specified in the [GLOBAL] section, this setting is used in the entire cluster. Additionally, it is possible to specify settings per node and per site. Node sections follow a syntax of [Node:nodename]. If an option is set globally and per node, the node setting overrules the global setting.

It is also possible to group nodes into sites. In order to make node alpha part of site mysite, you have to specify the site option in alpha’s node section:

# drbdmanage modify-config
[Node:alpha]
site = mysite

It is then also possible to specify drbdmanage settings per site using [Site:] sections. Lets assume that you want to set the loglevel option in general to INFO, for site mysite to WARN and for node alpha, which is also part of site mysite to DEBUG. This would result in the following configuration:

# drbdmanage modify-config
[GLOBAL]
loglevel = INFO

[Site:mysite]
loglevel = WARN

[Node:alpha]
site = mysite
loglevel = DEBUG

By executing drbdmanage modify-config without any options, you can edit global, per site and per node settings. It is also possible to execute modify-config for a specific node. In this per-node view, it is possible to set further per-node specific settings like the storage plugin discussed in Section 4.4, “Configuring storage plugins”.