Skip to content

Commit 71d6c12

Browse files
committed
[readme] Update the documention
1 parent 214b6cc commit 71d6c12

File tree

1 file changed

+22
-8
lines changed

1 file changed

+22
-8
lines changed

README.md

+22-8
Original file line numberDiff line numberDiff line change
@@ -15,22 +15,21 @@ Supported distributions:
1515
- Ubuntu 14.x / 15.x / 16.x
1616

1717
Works with ``firewalld`` daemon and SELinux.
18-
If ``corosync_firewalld`` is set to ``true`` please make sure than ``firewalld`` package is installed and the service is started.
1918

2019
Because the version 1 of Corosync is *"not supported"* anymore, this role provides only a support for the version 2 of Corosync.
2120

2221
## Requirements
23-
This role needs at least 3 nodes and Ansible 2.0.
22+
This role needs at least 3 nodes and Ansible 2.x
2423

25-
To generate the Corosync auth key, you will need entropy. If the task ``Generating /eyc/corosync/authkey file`` is stuck it means that you don't have enough entropy. The workaround is to generate entropy with ``haveged`` daemon.
26-
```
27-
# yum install haveged -y ; systemctl start haveged
24+
To generate the Corosync auth key, you will need entropy. If the task ``Generating /eyc/corosync/authkey file`` is stuck it means that you don't have enough entropy. The workaround is to generate entropy with ``haveged`` daemon, enable this option:
2825
```
26+
corosync_haveged: true
2927
```
30-
# apt-get install haveged -y ; systemctl start haveged
31-
```
3228

33-
This package should be installed only on the first node of your inventory.
29+
If ``corosync_firewalld`` is set to ``true`` please make sure than ``firewalld`` package is installed and the service is started.
30+
31+
If ``corosync_selinux`` is set to ``true`` please make sure than ``policycoreutils-python`` package is installed.
32+
3433

3534
## Role Variables
3635
The description of all options is available here: http://manpages.ubuntu.com/manpages/wily/man5/corosync.conf.5.html
@@ -93,10 +92,16 @@ As said above, if you want to configure ``firewalld`` rules, be sure that ``coro
9392

9493
It's possible to use official Debian backports to have the latest Corosync version, just enable it via `corosync_debian_backports` set to ``true``.
9594

95+
The ``corosync_force_regenerate_authkey`` allows you to regenerate the ``/etc/corosync/authkey`` file.
96+
9697
### Multicast (1 ring)
9798
```
9899
---
99100
corosync_firewalld: true
101+
corosync_selinux: true
102+
corosync_haveged: true
103+
corosync_force_regenerate_authkey: false
104+
corosync_debian_backports: true
100105
corosync_expected_votes: 3
101106
102107
corosync_interfaces:
@@ -110,6 +115,9 @@ The following example will create a Corosync cluster using ``multicast`` with tw
110115
```
111116
---
112117
corosync_firewalld: true
118+
corosync_selinux: true
119+
corosync_haveged: true
120+
corosync_force_regenerate_authkey: false
113121
corosync_debian_backports: true
114122
corosync_expected_votes: 3
115123
@@ -129,6 +137,9 @@ If ``unicast`` is used, you will have to define ``corosync_transport: udpu`` and
129137
```
130138
---
131139
corosync_firewalld: true
140+
corosync_selinux: true
141+
corosync_haveged: true
142+
corosync_force_regenerate_authkey: false
132143
corosync_debian_backports: true
133144
corosync_node_list:
134145
- ctrl01
@@ -145,6 +156,9 @@ The following example will create a Corosync cluster using ``unicast`` with two
145156
```
146157
---
147158
corosync_firewalld: true
159+
corosync_selinux: true
160+
corosync_haveged: true
161+
corosync_force_regenerate_authkey: false
148162
corosync_debian_backports: true
149163
corosync_node_list:
150164
- ctrl01

0 commit comments

Comments
 (0)