/etc/corosync/corosync.conf
.
Example C.1. Corosync 2.x configuration file for two nodes myhost1 and myhost2
totem { version: 2 secauth: off cluster_name: mycluster transport: udpu } nodelist { node { ring0_addr: myhost1 nodeid: 1 } node { ring0_addr: myhost2 nodeid: 2 } } quorum { provider: corosync_votequorum two_node: 1 } logging { to_syslog: yes }
Example C.2. Corosync 2.x configuration file for three nodes myhost1, myhost2 and myhost3
totem { version: 2 secauth: off cluster_name: mycluster transport: udpu } nodelist { node { ring0_addr: myhost1 nodeid: 1 } node { ring0_addr: myhost2 nodeid: 2 } node { ring0_addr: myhost3 nodeid: 3 } } quorum { provider: corosync_votequorum } logging { to_syslog: yes }
totem
section defines what protocol version and options (including encryption) to use, [23] and gives the cluster a unique name (mycluster
in these examples).
node
section lists the nodes in this cluster. (See Section 4.2, “Where Pacemaker Gets the Node Name” for how this affects pacemaker.)
quorum
section defines how the cluster uses quorum. The important thing is that two-node clusters must be handled specially, so two_node: 1
must be defined for two-node clusters (and only for two-node clusters).
logging
section should be self-explanatory.