summaryrefslogtreecommitdiffstats
path: root/conf/corosync.conf.example
diff options
context:
space:
mode:
Diffstat (limited to 'conf/corosync.conf.example')
-rw-r--r--conf/corosync.conf.example71
1 files changed, 71 insertions, 0 deletions
diff --git a/conf/corosync.conf.example b/conf/corosync.conf.example
new file mode 100644
index 0000000..4658a86
--- /dev/null
+++ b/conf/corosync.conf.example
@@ -0,0 +1,71 @@
+# Please read the corosync.conf.5 manual page
+totem {
+ version: 2
+
+ # Set name of the cluster
+ cluster_name: ExampleCluster
+
+ # crypto_cipher and crypto_hash: Used for mutual node authentication.
+ # If you choose to enable this, then do remember to create a shared
+ # secret with "corosync-keygen".
+ # enabling crypto_cipher, requires also enabling of crypto_hash.
+ # crypto works only with knet transport
+ crypto_cipher: none
+ crypto_hash: none
+}
+
+logging {
+ # Log the source file and line where messages are being
+ # generated. When in doubt, leave off. Potentially useful for
+ # debugging.
+ fileline: off
+ # Log to standard error. When in doubt, set to yes. Useful when
+ # running in the foreground (when invoking "corosync -f")
+ to_stderr: yes
+ # Log to a log file. When set to "no", the "logfile" option
+ # must not be set.
+ to_logfile: yes
+ logfile: /var/log/cluster/corosync.log
+ # Log to the system log daemon. When in doubt, set to yes.
+ to_syslog: yes
+ # Log debug messages (very verbose). When in doubt, leave off.
+ debug: off
+ # Log messages with time stamps. When in doubt, set to hires (or on)
+ #timestamp: hires
+ logger_subsys {
+ subsys: QUORUM
+ debug: off
+ }
+}
+
+quorum {
+ # Enable and configure quorum subsystem (default: off)
+ # see also corosync.conf.5 and votequorum.5
+ #provider: corosync_votequorum
+}
+
+nodelist {
+ # Change/uncomment/add node sections to match cluster configuration
+
+ node {
+ # Hostname of the node
+ name: node1
+ # Cluster membership node identifier
+ nodeid: 1
+ # Address of first link
+ #ring0_addr: 192.168.0.1
+ # When knet transport is used it's possible to define up to 8 links
+ #ring1_addr: 192.168.1.1
+ }
+ node {
+ # Hostname of the node
+ name: node2
+ # Cluster membership node identifier
+ nodeid: 2
+ # Address of first link
+ #ring0_addr: 192.168.0.2
+ # When knet transport is used it's possible to define up to 8 links
+ #ring1_addr: 192.168.1.2
+ }
+ # ...
+}