]>
Commit | Line | Data |
---|---|---|
d8742b0c | 1 | ifdef::manvolnum[] |
b2f242ab DM |
2 | pvecm(1) |
3 | ======== | |
d8742b0c | 4 | include::attributes.txt[] |
5f09af76 DM |
5 | :pve-toplevel: |
6 | ||
d8742b0c DM |
7 | NAME |
8 | ---- | |
9 | ||
74026b8f | 10 | pvecm - Proxmox VE Cluster Manager |
d8742b0c | 11 | |
49a5e11c | 12 | SYNOPSIS |
d8742b0c DM |
13 | -------- |
14 | ||
15 | include::pvecm.1-synopsis.adoc[] | |
16 | ||
17 | DESCRIPTION | |
18 | ----------- | |
19 | endif::manvolnum[] | |
20 | ||
21 | ifndef::manvolnum[] | |
22 | Cluster Manager | |
23 | =============== | |
24 | include::attributes.txt[] | |
5f09af76 | 25 | :pve-toplevel: |
194d2f29 | 26 | endif::manvolnum[] |
5f09af76 | 27 | |
8c1189b6 FG |
28 | The {PVE} cluster manager `pvecm` is a tool to create a group of |
29 | physical servers. Such a group is called a *cluster*. We use the | |
8a865621 | 30 | http://www.corosync.org[Corosync Cluster Engine] for reliable group |
5eba0743 | 31 | communication, and such clusters can consist of up to 32 physical nodes |
8a865621 DM |
32 | (probably more, dependent on network latency). |
33 | ||
8c1189b6 | 34 | `pvecm` can be used to create a new cluster, join nodes to a cluster, |
8a865621 | 35 | leave the cluster, get status information and do various other cluster |
e300cf7d FG |
36 | related tasks. The **P**rox**m**o**x** **C**luster **F**ile **S**ystem (``pmxcfs'') |
37 | is used to transparently distribute the cluster configuration to all cluster | |
8a865621 DM |
38 | nodes. |
39 | ||
40 | Grouping nodes into a cluster has the following advantages: | |
41 | ||
42 | * Centralized, web based management | |
43 | ||
5eba0743 | 44 | * Multi-master clusters: each node can do all management task |
8a865621 | 45 | |
8c1189b6 FG |
46 | * `pmxcfs`: database-driven file system for storing configuration files, |
47 | replicated in real-time on all nodes using `corosync`. | |
8a865621 | 48 | |
5eba0743 | 49 | * Easy migration of virtual machines and containers between physical |
8a865621 DM |
50 | hosts |
51 | ||
52 | * Fast deployment | |
53 | ||
54 | * Cluster-wide services like firewall and HA | |
55 | ||
56 | ||
57 | Requirements | |
58 | ------------ | |
59 | ||
8c1189b6 | 60 | * All nodes must be in the same network as `corosync` uses IP Multicast |
8a865621 | 61 | to communicate between nodes (also see |
ceabe189 | 62 | http://www.corosync.org[Corosync Cluster Engine]). Corosync uses UDP |
ff72a2ba | 63 | ports 5404 and 5405 for cluster communication. |
ceabe189 DM |
64 | + |
65 | NOTE: Some switches do not support IP multicast by default and must be | |
66 | manually enabled first. | |
8a865621 DM |
67 | |
68 | * Date and time have to be synchronized. | |
69 | ||
ceabe189 | 70 | * SSH tunnel on TCP port 22 between nodes is used. |
8a865621 | 71 | |
ceabe189 DM |
72 | * If you are interested in High Availability, you need to have at |
73 | least three nodes for reliable quorum. All nodes should have the | |
74 | same version. | |
8a865621 DM |
75 | |
76 | * We recommend a dedicated NIC for the cluster traffic, especially if | |
77 | you use shared storage. | |
78 | ||
79 | NOTE: It is not possible to mix Proxmox VE 3.x and earlier with | |
ceabe189 | 80 | Proxmox VE 4.0 cluster nodes. |
8a865621 DM |
81 | |
82 | ||
ceabe189 DM |
83 | Preparing Nodes |
84 | --------------- | |
8a865621 DM |
85 | |
86 | First, install {PVE} on all nodes. Make sure that each node is | |
87 | installed with the final hostname and IP configuration. Changing the | |
88 | hostname and IP is not possible after cluster creation. | |
89 | ||
90 | Currently the cluster creation has to be done on the console, so you | |
8c1189b6 | 91 | need to login via `ssh`. |
8a865621 | 92 | |
8a865621 | 93 | Create the Cluster |
ceabe189 | 94 | ------------------ |
8a865621 | 95 | |
8c1189b6 FG |
96 | Login via `ssh` to the first {pve} node. Use a unique name for your cluster. |
97 | This name cannot be changed later. | |
8a865621 DM |
98 | |
99 | hp1# pvecm create YOUR-CLUSTER-NAME | |
100 | ||
63f956c8 DM |
101 | CAUTION: The cluster name is used to compute the default multicast |
102 | address. Please use unique cluster names if you run more than one | |
103 | cluster inside your network. | |
104 | ||
8a865621 DM |
105 | To check the state of your cluster use: |
106 | ||
107 | hp1# pvecm status | |
108 | ||
109 | ||
110 | Adding Nodes to the Cluster | |
ceabe189 | 111 | --------------------------- |
8a865621 | 112 | |
8c1189b6 | 113 | Login via `ssh` to the node you want to add. |
8a865621 DM |
114 | |
115 | hp2# pvecm add IP-ADDRESS-CLUSTER | |
116 | ||
117 | For `IP-ADDRESS-CLUSTER` use the IP from an existing cluster node. | |
118 | ||
5eba0743 | 119 | CAUTION: A new node cannot hold any VMs, because you would get |
7980581f | 120 | conflicts about identical VM IDs. Also, all existing configuration in |
8c1189b6 FG |
121 | `/etc/pve` is overwritten when you join a new node to the cluster. To |
122 | workaround, use `vzdump` to backup and restore to a different VMID after | |
7980581f | 123 | adding the node to the cluster. |
8a865621 DM |
124 | |
125 | To check the state of cluster: | |
126 | ||
127 | # pvecm status | |
128 | ||
ceabe189 | 129 | .Cluster status after adding 4 nodes |
8a865621 DM |
130 | ---- |
131 | hp2# pvecm status | |
132 | Quorum information | |
133 | ~~~~~~~~~~~~~~~~~~ | |
134 | Date: Mon Apr 20 12:30:13 2015 | |
135 | Quorum provider: corosync_votequorum | |
136 | Nodes: 4 | |
137 | Node ID: 0x00000001 | |
138 | Ring ID: 1928 | |
139 | Quorate: Yes | |
140 | ||
141 | Votequorum information | |
142 | ~~~~~~~~~~~~~~~~~~~~~~ | |
143 | Expected votes: 4 | |
144 | Highest expected: 4 | |
145 | Total votes: 4 | |
146 | Quorum: 2 | |
147 | Flags: Quorate | |
148 | ||
149 | Membership information | |
150 | ~~~~~~~~~~~~~~~~~~~~~~ | |
151 | Nodeid Votes Name | |
152 | 0x00000001 1 192.168.15.91 | |
153 | 0x00000002 1 192.168.15.92 (local) | |
154 | 0x00000003 1 192.168.15.93 | |
155 | 0x00000004 1 192.168.15.94 | |
156 | ---- | |
157 | ||
158 | If you only want the list of all nodes use: | |
159 | ||
160 | # pvecm nodes | |
161 | ||
5eba0743 | 162 | .List nodes in a cluster |
8a865621 DM |
163 | ---- |
164 | hp2# pvecm nodes | |
165 | ||
166 | Membership information | |
167 | ~~~~~~~~~~~~~~~~~~~~~~ | |
168 | Nodeid Votes Name | |
169 | 1 1 hp1 | |
170 | 2 1 hp2 (local) | |
171 | 3 1 hp3 | |
172 | 4 1 hp4 | |
173 | ---- | |
174 | ||
e4ec4154 TL |
175 | Adding Nodes With Separated Cluster Network |
176 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
177 | ||
178 | When adding a node to a cluster with a separated cluster network you need to | |
179 | use the 'ringX_addr' parameters to set the nodes address on those networks: | |
180 | ||
181 | [source,bash] | |
4d19cb00 | 182 | ---- |
e4ec4154 | 183 | pvecm add IP-ADDRESS-CLUSTER -ring0_addr IP-ADDRESS-RING0 |
4d19cb00 | 184 | ---- |
e4ec4154 TL |
185 | |
186 | If you want to use the Redundant Ring Protocol you will also want to pass the | |
187 | 'ring1_addr' parameter. | |
188 | ||
8a865621 DM |
189 | |
190 | Remove a Cluster Node | |
ceabe189 | 191 | --------------------- |
8a865621 DM |
192 | |
193 | CAUTION: Read carefully the procedure before proceeding, as it could | |
194 | not be what you want or need. | |
195 | ||
196 | Move all virtual machines from the node. Make sure you have no local | |
197 | data or backups you want to keep, or save them accordingly. | |
198 | ||
8c1189b6 | 199 | Log in to one remaining node via ssh. Issue a `pvecm nodes` command to |
7980581f | 200 | identify the node ID: |
8a865621 DM |
201 | |
202 | ---- | |
203 | hp1# pvecm status | |
204 | ||
205 | Quorum information | |
206 | ~~~~~~~~~~~~~~~~~~ | |
207 | Date: Mon Apr 20 12:30:13 2015 | |
208 | Quorum provider: corosync_votequorum | |
209 | Nodes: 4 | |
210 | Node ID: 0x00000001 | |
211 | Ring ID: 1928 | |
212 | Quorate: Yes | |
213 | ||
214 | Votequorum information | |
215 | ~~~~~~~~~~~~~~~~~~~~~~ | |
216 | Expected votes: 4 | |
217 | Highest expected: 4 | |
218 | Total votes: 4 | |
219 | Quorum: 2 | |
220 | Flags: Quorate | |
221 | ||
222 | Membership information | |
223 | ~~~~~~~~~~~~~~~~~~~~~~ | |
224 | Nodeid Votes Name | |
225 | 0x00000001 1 192.168.15.91 (local) | |
226 | 0x00000002 1 192.168.15.92 | |
227 | 0x00000003 1 192.168.15.93 | |
228 | 0x00000004 1 192.168.15.94 | |
229 | ---- | |
230 | ||
231 | IMPORTANT: at this point you must power off the node to be removed and | |
232 | make sure that it will not power on again (in the network) as it | |
233 | is. | |
234 | ||
235 | ---- | |
236 | hp1# pvecm nodes | |
237 | ||
238 | Membership information | |
239 | ~~~~~~~~~~~~~~~~~~~~~~ | |
240 | Nodeid Votes Name | |
241 | 1 1 hp1 (local) | |
242 | 2 1 hp2 | |
243 | 3 1 hp3 | |
244 | 4 1 hp4 | |
245 | ---- | |
246 | ||
247 | Log in to one remaining node via ssh. Issue the delete command (here | |
8c1189b6 | 248 | deleting node `hp4`): |
8a865621 DM |
249 | |
250 | hp1# pvecm delnode hp4 | |
251 | ||
252 | If the operation succeeds no output is returned, just check the node | |
8c1189b6 | 253 | list again with `pvecm nodes` or `pvecm status`. You should see |
8a865621 DM |
254 | something like: |
255 | ||
256 | ---- | |
257 | hp1# pvecm status | |
258 | ||
259 | Quorum information | |
260 | ~~~~~~~~~~~~~~~~~~ | |
261 | Date: Mon Apr 20 12:44:28 2015 | |
262 | Quorum provider: corosync_votequorum | |
263 | Nodes: 3 | |
264 | Node ID: 0x00000001 | |
265 | Ring ID: 1992 | |
266 | Quorate: Yes | |
267 | ||
268 | Votequorum information | |
269 | ~~~~~~~~~~~~~~~~~~~~~~ | |
270 | Expected votes: 3 | |
271 | Highest expected: 3 | |
272 | Total votes: 3 | |
273 | Quorum: 3 | |
274 | Flags: Quorate | |
275 | ||
276 | Membership information | |
277 | ~~~~~~~~~~~~~~~~~~~~~~ | |
278 | Nodeid Votes Name | |
279 | 0x00000001 1 192.168.15.90 (local) | |
280 | 0x00000002 1 192.168.15.91 | |
281 | 0x00000003 1 192.168.15.92 | |
282 | ---- | |
283 | ||
284 | IMPORTANT: as said above, it is very important to power off the node | |
285 | *before* removal, and make sure that it will *never* power on again | |
286 | (in the existing cluster network) as it is. | |
287 | ||
288 | If you power on the node as it is, your cluster will be screwed up and | |
289 | it could be difficult to restore a clean cluster state. | |
290 | ||
291 | If, for whatever reason, you want that this server joins the same | |
292 | cluster again, you have to | |
293 | ||
26ca7ff5 | 294 | * reinstall {pve} on it from scratch |
8a865621 DM |
295 | |
296 | * then join it, as explained in the previous section. | |
d8742b0c | 297 | |
38ae8db3 | 298 | [[pvecm_separate_node_without_reinstall]] |
555e966b TL |
299 | Separate A Node Without Reinstalling |
300 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
301 | ||
302 | CAUTION: This is *not* the recommended method, proceed with caution. Use the | |
303 | above mentioned method if you're unsure. | |
304 | ||
305 | You can also separate a node from a cluster without reinstalling it from | |
306 | scratch. But after removing the node from the cluster it will still have | |
307 | access to the shared storages! This must be resolved before you start removing | |
308 | the node from the cluster. A {pve} cluster cannot share the exact same | |
309 | storage with another cluster, as it leads to VMID conflicts. | |
310 | ||
3be22308 TL |
311 | Its suggested that you create a new storage where only the node which you want |
312 | to separate has access. This can be an new export on your NFS or a new Ceph | |
313 | pool, to name a few examples. Its just important that the exact same storage | |
314 | does not gets accessed by multiple clusters. After setting this storage up move | |
315 | all data from the node and its VMs to it. Then you are ready to separate the | |
316 | node from the cluster. | |
555e966b TL |
317 | |
318 | WARNING: Ensure all shared resources are cleanly separated! You will run into | |
319 | conflicts and problems else. | |
320 | ||
321 | First stop the corosync and the pve-cluster services on the node: | |
322 | [source,bash] | |
4d19cb00 | 323 | ---- |
555e966b TL |
324 | systemctl stop pve-cluster |
325 | systemctl stop corosync | |
4d19cb00 | 326 | ---- |
555e966b TL |
327 | |
328 | Start the cluster filesystem again in local mode: | |
329 | [source,bash] | |
4d19cb00 | 330 | ---- |
555e966b | 331 | pmxcfs -l |
4d19cb00 | 332 | ---- |
555e966b TL |
333 | |
334 | Delete the corosync configuration files: | |
335 | [source,bash] | |
4d19cb00 | 336 | ---- |
555e966b TL |
337 | rm /etc/pve/corosync.conf |
338 | rm /etc/corosync/* | |
4d19cb00 | 339 | ---- |
555e966b TL |
340 | |
341 | You can now start the filesystem again as normal service: | |
342 | [source,bash] | |
4d19cb00 | 343 | ---- |
555e966b TL |
344 | killall pmxcfs |
345 | systemctl start pve-cluster | |
4d19cb00 | 346 | ---- |
555e966b TL |
347 | |
348 | The node is now separated from the cluster. You can deleted it from a remaining | |
349 | node of the cluster with: | |
350 | [source,bash] | |
4d19cb00 | 351 | ---- |
555e966b | 352 | pvecm delnode oldnode |
4d19cb00 | 353 | ---- |
555e966b TL |
354 | |
355 | If the command failed, because the remaining node in the cluster lost quorum | |
356 | when the now separate node exited, you may set the expected votes to 1 as a workaround: | |
357 | [source,bash] | |
4d19cb00 | 358 | ---- |
555e966b | 359 | pvecm expected 1 |
4d19cb00 | 360 | ---- |
555e966b TL |
361 | |
362 | And the repeat the 'pvecm delnode' command. | |
363 | ||
364 | Now switch back to the separated node, here delete all remaining files left | |
365 | from the old cluster. This ensures that the node can be added to another | |
366 | cluster again without problems. | |
367 | ||
368 | [source,bash] | |
4d19cb00 | 369 | ---- |
555e966b | 370 | rm /var/lib/corosync/* |
4d19cb00 | 371 | ---- |
555e966b TL |
372 | |
373 | As the configuration files from the other nodes are still in the cluster | |
374 | filesystem you may want to clean those up too. Remove simply the whole | |
375 | directory recursive from '/etc/pve/nodes/NODENAME', but check three times that | |
376 | you used the correct one before deleting it. | |
377 | ||
378 | CAUTION: The nodes SSH keys are still in the 'authorized_key' file, this means | |
379 | the nodes can still connect to each other with public key authentication. This | |
380 | should be fixed by removing the respective keys from the | |
381 | '/etc/pve/priv/authorized_keys' file. | |
d8742b0c | 382 | |
806ef12d DM |
383 | Quorum |
384 | ------ | |
385 | ||
386 | {pve} use a quorum-based technique to provide a consistent state among | |
387 | all cluster nodes. | |
388 | ||
389 | [quote, from Wikipedia, Quorum (distributed computing)] | |
390 | ____ | |
391 | A quorum is the minimum number of votes that a distributed transaction | |
392 | has to obtain in order to be allowed to perform an operation in a | |
393 | distributed system. | |
394 | ____ | |
395 | ||
396 | In case of network partitioning, state changes requires that a | |
397 | majority of nodes are online. The cluster switches to read-only mode | |
5eba0743 | 398 | if it loses quorum. |
806ef12d DM |
399 | |
400 | NOTE: {pve} assigns a single vote to each node by default. | |
401 | ||
e4ec4154 TL |
402 | Cluster Network |
403 | --------------- | |
404 | ||
405 | The cluster network is the core of a cluster. All messages sent over it have to | |
406 | be delivered reliable to all nodes in their respective order. In {pve} this | |
407 | part is done by corosync, an implementation of a high performance low overhead | |
408 | high availability development toolkit. It serves our decentralized | |
409 | configuration file system (`pmxcfs`). | |
410 | ||
411 | [[cluster-network-requirements]] | |
412 | Network Requirements | |
413 | ~~~~~~~~~~~~~~~~~~~~ | |
414 | This needs a reliable network with latencies under 2 milliseconds (LAN | |
415 | performance) to work properly. While corosync can also use unicast for | |
416 | communication between nodes its **highly recommended** to have a multicast | |
417 | capable network. The network should not be used heavily by other members, | |
418 | ideally corosync runs on its own network. | |
419 | *never* share it with network where storage communicates too. | |
420 | ||
421 | Before setting up a cluster it is good practice to check if the network is fit | |
422 | for that purpose. | |
423 | ||
424 | * Ensure that all nodes are in the same subnet. This must only be true for the | |
425 | network interfaces used for cluster communication (corosync). | |
426 | ||
427 | * Ensure all nodes can reach each other over those interfaces, using `ping` is | |
428 | enough for a basic test. | |
429 | ||
430 | * Ensure that multicast works in general and a high package rates. This can be | |
431 | done with the `omping` tool. The final "%loss" number should be < 1%. | |
432 | [source,bash] | |
433 | ---- | |
434 | omping -c 10000 -i 0.001 -F -q NODE1-IP NODE2-IP ... | |
435 | ---- | |
436 | ||
437 | * Ensure that multicast communication works over an extended period of time. | |
438 | This covers up problems where IGMP snooping is activated on the network but | |
439 | no multicast querier is active. This test has a duration of around 10 | |
440 | minutes. | |
441 | [source,bash] | |
4d19cb00 | 442 | ---- |
e4ec4154 | 443 | omping -c 600 -i 1 -q NODE1-IP NODE2-IP ... |
4d19cb00 | 444 | ---- |
e4ec4154 TL |
445 | |
446 | Your network is not ready for clustering if any of these test fails. Recheck | |
447 | your network configuration. Especially switches are notorious for having | |
448 | multicast disabled by default or IGMP snooping enabled with no IGMP querier | |
449 | active. | |
450 | ||
451 | In smaller cluster its also an option to use unicast if you really cannot get | |
452 | multicast to work. | |
453 | ||
454 | Separate Cluster Network | |
455 | ~~~~~~~~~~~~~~~~~~~~~~~~ | |
456 | ||
457 | When creating a cluster without any parameters the cluster network is generally | |
458 | shared with the Web UI and the VMs and its traffic. Depending on your setup | |
459 | even storage traffic may get sent over the same network. Its recommended to | |
460 | change that, as corosync is a time critical real time application. | |
461 | ||
462 | Setting Up A New Network | |
463 | ^^^^^^^^^^^^^^^^^^^^^^^^ | |
464 | ||
465 | First you have to setup a new network interface. It should be on a physical | |
466 | separate network. Ensure that your network fulfills the | |
467 | <<cluster-network-requirements,cluster network requirements>>. | |
468 | ||
469 | Separate On Cluster Creation | |
470 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
471 | ||
472 | This is possible through the 'ring0_addr' and 'bindnet0_addr' parameter of | |
473 | the 'pvecm create' command used for creating a new cluster. | |
474 | ||
475 | If you have setup a additional NIC with a static address on 10.10.10.1/25 | |
476 | and want to send and receive all cluster communication over this interface | |
477 | you would execute: | |
478 | ||
479 | [source,bash] | |
4d19cb00 | 480 | ---- |
e4ec4154 | 481 | pvecm create test --ring0_addr 10.10.10.1 --bindnet0_addr 10.10.10.0 |
4d19cb00 | 482 | ---- |
e4ec4154 TL |
483 | |
484 | To check if everything is working properly execute: | |
485 | [source,bash] | |
4d19cb00 | 486 | ---- |
e4ec4154 | 487 | systemctl status corosync |
4d19cb00 | 488 | ---- |
e4ec4154 TL |
489 | |
490 | [[separate-cluster-net-after-creation]] | |
491 | Separate After Cluster Creation | |
492 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
493 | ||
494 | You can do this also if you have already created a cluster and want to switch | |
495 | its communication to another network, without rebuilding the whole cluster. | |
496 | This change may lead to short durations of quorum loss in the cluster, as nodes | |
497 | have to restart corosync and come up one after the other on the new network. | |
498 | ||
499 | Check how to <<edit-corosync-conf,edit the corosync.conf file>> first. | |
500 | The open it and you should see a file similar to: | |
501 | ||
502 | ---- | |
503 | logging { | |
504 | debug: off | |
505 | to_syslog: yes | |
506 | } | |
507 | ||
508 | nodelist { | |
509 | ||
510 | node { | |
511 | name: due | |
512 | nodeid: 2 | |
513 | quorum_votes: 1 | |
514 | ring0_addr: due | |
515 | } | |
516 | ||
517 | node { | |
518 | name: tre | |
519 | nodeid: 3 | |
520 | quorum_votes: 1 | |
521 | ring0_addr: tre | |
522 | } | |
523 | ||
524 | node { | |
525 | name: uno | |
526 | nodeid: 1 | |
527 | quorum_votes: 1 | |
528 | ring0_addr: uno | |
529 | } | |
530 | ||
531 | } | |
532 | ||
533 | quorum { | |
534 | provider: corosync_votequorum | |
535 | } | |
536 | ||
537 | totem { | |
538 | cluster_name: thomas-testcluster | |
539 | config_version: 3 | |
540 | ip_version: ipv4 | |
541 | secauth: on | |
542 | version: 2 | |
543 | interface { | |
544 | bindnetaddr: 192.168.30.50 | |
545 | ringnumber: 0 | |
546 | } | |
547 | ||
548 | } | |
549 | ---- | |
550 | ||
551 | The first you want to do is add the 'name' properties in the node entries if | |
552 | you do not see them already. Those *must* match the node name. | |
553 | ||
554 | Then replace the address from the 'ring0_addr' properties with the new | |
555 | addresses. You may use plain IP addresses or also hostnames here. If you use | |
556 | hostnames ensure that they are resolvable from all nodes. | |
557 | ||
558 | In my example I want to switch my cluster communication to the 10.10.10.1/25 | |
559 | network. So I replace all 'ring0_addr' respectively. I also set the bindetaddr | |
560 | in the totem section of the config to an address of the new network. It can be | |
561 | any address from the subnet configured on the new network interface. | |
562 | ||
563 | After you increased the 'config_version' property the new configuration file | |
564 | should look like: | |
565 | ||
566 | ---- | |
567 | ||
568 | logging { | |
569 | debug: off | |
570 | to_syslog: yes | |
571 | } | |
572 | ||
573 | nodelist { | |
574 | ||
575 | node { | |
576 | name: due | |
577 | nodeid: 2 | |
578 | quorum_votes: 1 | |
579 | ring0_addr: 10.10.10.2 | |
580 | } | |
581 | ||
582 | node { | |
583 | name: tre | |
584 | nodeid: 3 | |
585 | quorum_votes: 1 | |
586 | ring0_addr: 10.10.10.3 | |
587 | } | |
588 | ||
589 | node { | |
590 | name: uno | |
591 | nodeid: 1 | |
592 | quorum_votes: 1 | |
593 | ring0_addr: 10.10.10.1 | |
594 | } | |
595 | ||
596 | } | |
597 | ||
598 | quorum { | |
599 | provider: corosync_votequorum | |
600 | } | |
601 | ||
602 | totem { | |
603 | cluster_name: thomas-testcluster | |
604 | config_version: 4 | |
605 | ip_version: ipv4 | |
606 | secauth: on | |
607 | version: 2 | |
608 | interface { | |
609 | bindnetaddr: 10.10.10.1 | |
610 | ringnumber: 0 | |
611 | } | |
612 | ||
613 | } | |
614 | ---- | |
615 | ||
616 | Now after a final check whether all changed information is correct we save it | |
617 | and see again the <<edit-corosync-conf,edit corosync.conf file>> section to | |
618 | learn how to bring it in effect. | |
619 | ||
620 | As our change cannot be enforced live from corosync we have to do an restart. | |
621 | ||
622 | On a single node execute: | |
623 | [source,bash] | |
4d19cb00 | 624 | ---- |
e4ec4154 | 625 | systemctl restart corosync |
4d19cb00 | 626 | ---- |
e4ec4154 TL |
627 | |
628 | Now check if everything is fine: | |
629 | ||
630 | [source,bash] | |
4d19cb00 | 631 | ---- |
e4ec4154 | 632 | systemctl status corosync |
4d19cb00 | 633 | ---- |
e4ec4154 TL |
634 | |
635 | If corosync runs again correct restart corosync also on all other nodes. | |
636 | They will then join the cluster membership one by one on the new network. | |
637 | ||
638 | Redundant Ring Protocol | |
639 | ~~~~~~~~~~~~~~~~~~~~~~~ | |
640 | To avoid a single point of failure you should implement counter measurements. | |
641 | This can be on the hardware and operating system level through network bonding. | |
642 | ||
643 | Corosync itself offers also a possibility to add redundancy through the so | |
644 | called 'Redundant Ring Protocol'. This protocol allows running a second totem | |
645 | ring on another network, this network should be physically separated from the | |
646 | other rings network to actually increase availability. | |
647 | ||
648 | RRP On Cluster Creation | |
649 | ~~~~~~~~~~~~~~~~~~~~~~~ | |
650 | ||
651 | The 'pvecm create' command provides the additional parameters 'bindnetX_addr', | |
652 | 'ringX_addr' and 'rrp_mode', can be used for RRP configuration. | |
653 | ||
654 | NOTE: See the <<corosync-conf-glossary,glossary>> if you do not know what each parameter means. | |
655 | ||
656 | So if you have two networks, one on the 10.10.10.1/24 and the other on the | |
657 | 10.10.20.1/24 subnet you would execute: | |
658 | ||
659 | [source,bash] | |
4d19cb00 | 660 | ---- |
e4ec4154 TL |
661 | pvecm create CLUSTERNAME -bindnet0_addr 10.10.10.1 -ring0_addr 10.10.10.1 \ |
662 | -bindnet1_addr 10.10.20.1 -ring1_addr 10.10.20.1 | |
4d19cb00 | 663 | ---- |
e4ec4154 TL |
664 | |
665 | RRP On A Created Cluster | |
666 | ~~~~~~~~~~~~~~~~~~~~~~~~ | |
667 | ||
668 | When enabling an already running cluster to use RRP you will take similar steps | |
7d48940b DM |
669 | as describe in |
670 | <<separate-cluster-net-after-creation,separating the cluster network>>. You | |
671 | just do it on another ring. | |
e4ec4154 TL |
672 | |
673 | First add a new `interface` subsection in the `totem` section, set its | |
674 | `ringnumber` property to `1`. Set the interfaces `bindnetaddr` property to an | |
675 | address of the subnet you have configured for your new ring. | |
676 | Further set the `rrp_mode` to `passive`, this is the only stable mode. | |
677 | ||
678 | Then add to each node entry in the `nodelist` section its new `ring1_addr` | |
679 | property with the nodes additional ring address. | |
680 | ||
681 | So if you have two networks, one on the 10.10.10.1/24 and the other on the | |
682 | 10.10.20.1/24 subnet, the final configuration file should look like: | |
683 | ||
684 | ---- | |
685 | totem { | |
686 | cluster_name: tweak | |
687 | config_version: 9 | |
688 | ip_version: ipv4 | |
689 | rrp_mode: passive | |
690 | secauth: on | |
691 | version: 2 | |
692 | interface { | |
693 | bindnetaddr: 10.10.10.1 | |
694 | ringnumber: 0 | |
695 | } | |
696 | interface { | |
697 | bindnetaddr: 10.10.20.1 | |
698 | ringnumber: 1 | |
699 | } | |
700 | } | |
701 | ||
702 | nodelist { | |
703 | node { | |
704 | name: pvecm1 | |
705 | nodeid: 1 | |
706 | quorum_votes: 1 | |
707 | ring0_addr: 10.10.10.1 | |
708 | ring1_addr: 10.10.20.1 | |
709 | } | |
710 | ||
711 | node { | |
712 | name: pvecm2 | |
713 | nodeid: 2 | |
714 | quorum_votes: 1 | |
715 | ring0_addr: 10.10.10.2 | |
716 | ring1_addr: 10.10.20.2 | |
717 | } | |
718 | ||
719 | [...] # other cluster nodes here | |
720 | } | |
721 | ||
722 | [...] # other remaining config sections here | |
723 | ||
724 | ---- | |
725 | ||
7d48940b DM |
726 | Bring it in effect like described in the |
727 | <<edit-corosync-conf,edit the corosync.conf file>> section. | |
e4ec4154 TL |
728 | |
729 | This is a change which cannot take live in effect and needs at least a restart | |
730 | of corosync. Recommended is a restart of the whole cluster. | |
731 | ||
732 | If you cannot reboot the whole cluster ensure no High Availability services are | |
733 | configured and the stop the corosync service on all nodes. After corosync is | |
734 | stopped on all nodes start it one after the other again. | |
735 | ||
736 | Corosync Configuration | |
737 | ---------------------- | |
738 | ||
739 | The `/ect/pve/corosync.conf` file plays a central role in {pve} cluster. It | |
740 | controls the cluster member ship and its network. | |
741 | For reading more about it check the corosync.conf man page: | |
742 | [source,bash] | |
4d19cb00 | 743 | ---- |
e4ec4154 | 744 | man corosync.conf |
4d19cb00 | 745 | ---- |
e4ec4154 TL |
746 | |
747 | For node membership you should always use the `pvecm` tool provided by {pve}. | |
748 | You may have to edit the configuration file manually for other changes. | |
749 | Here are a few best practice tips for doing this. | |
750 | ||
751 | [[edit-corosync-conf]] | |
752 | Edit corosync.conf | |
753 | ~~~~~~~~~~~~~~~~~~ | |
754 | ||
755 | Editing the corosync.conf file can be not always straight forward. There are | |
756 | two on each cluster, one in `/etc/pve/corosync.conf` and the other in | |
757 | `/etc/corosync/corosync.conf`. Editing the one in our cluster file system will | |
758 | propagate the changes to the local one, but not vice versa. | |
759 | ||
760 | The configuration will get updated automatically as soon as the file changes. | |
761 | This means changes which can be integrated in a running corosync will take | |
762 | instantly effect. So you should always make a copy and edit that instead, to | |
763 | avoid triggering some unwanted changes by an in between safe. | |
764 | ||
765 | [source,bash] | |
4d19cb00 | 766 | ---- |
e4ec4154 | 767 | cp /etc/pve/corosync.conf /etc/pve/corosync.conf.new |
4d19cb00 | 768 | ---- |
e4ec4154 TL |
769 | |
770 | Then open the Config file with your favorite editor, `nano` and `vim.tiny` are | |
771 | preinstalled on {pve} for example. | |
772 | ||
773 | NOTE: Always increment the 'config_version' number on configuration changes, | |
774 | omitting this can lead to problems. | |
775 | ||
776 | After making the necessary changes create another copy of the current working | |
777 | configuration file. This serves as a backup if the new configuration fails to | |
778 | apply or makes problems in other ways. | |
779 | ||
780 | [source,bash] | |
4d19cb00 | 781 | ---- |
e4ec4154 | 782 | cp /etc/pve/corosync.conf /etc/pve/corosync.conf.bak |
4d19cb00 | 783 | ---- |
e4ec4154 TL |
784 | |
785 | Then move the new configuration file over the old one: | |
786 | [source,bash] | |
4d19cb00 | 787 | ---- |
e4ec4154 | 788 | mv /etc/pve/corosync.conf.new /etc/pve/corosync.conf |
4d19cb00 | 789 | ---- |
e4ec4154 TL |
790 | |
791 | You may check with the commands | |
792 | [source,bash] | |
4d19cb00 | 793 | ---- |
e4ec4154 TL |
794 | systemctl status corosync |
795 | journalctl -b -u corosync | |
4d19cb00 | 796 | ---- |
e4ec4154 TL |
797 | |
798 | If the change could applied automatically. If not you may have to restart the | |
799 | corosync service via: | |
800 | [source,bash] | |
4d19cb00 | 801 | ---- |
e4ec4154 | 802 | systemctl restart corosync |
4d19cb00 | 803 | ---- |
e4ec4154 TL |
804 | |
805 | On errors check the troubleshooting section below. | |
806 | ||
807 | Troubleshooting | |
808 | ~~~~~~~~~~~~~~~ | |
809 | ||
810 | Issue: 'quorum.expected_votes must be configured' | |
811 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
812 | ||
813 | When corosync starts to fail and you get the following message in the system log: | |
814 | ||
815 | ---- | |
816 | [...] | |
817 | corosync[1647]: [QUORUM] Quorum provider: corosync_votequorum failed to initialize. | |
818 | corosync[1647]: [SERV ] Service engine 'corosync_quorum' failed to load for reason | |
819 | 'configuration error: nodelist or quorum.expected_votes must be configured!' | |
820 | [...] | |
821 | ---- | |
822 | ||
823 | It means that the hostname you set for corosync 'ringX_addr' in the | |
824 | configuration could not be resolved. | |
825 | ||
826 | ||
827 | Write Configuration When Not Quorate | |
828 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
829 | ||
830 | If you need to change '/etc/pve/corosync.conf' on an node with no quorum, and you | |
831 | know what you do, use: | |
832 | [source,bash] | |
4d19cb00 | 833 | ---- |
e4ec4154 | 834 | pvecm expected 1 |
4d19cb00 | 835 | ---- |
e4ec4154 TL |
836 | |
837 | This sets the expected vote count to 1 and makes the cluster quorate. You can | |
838 | now fix your configuration, or revert it back to the last working backup. | |
839 | ||
840 | This is not enough if corosync cannot start anymore. Here its best to edit the | |
841 | local copy of the corosync configuration in '/etc/corosync/corosync.conf' so | |
842 | that corosync can start again. Ensure that on all nodes this configuration has | |
843 | the same content to avoid split brains. If you are not sure what went wrong | |
844 | it's best to ask the Proxmox Community to help you. | |
845 | ||
846 | ||
847 | [[corosync-conf-glossary]] | |
848 | Corosync Configuration Glossary | |
849 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
850 | ||
851 | ringX_addr:: | |
852 | This names the different ring addresses for the corosync totem rings used for | |
853 | the cluster communication. | |
854 | ||
855 | bindnetaddr:: | |
856 | Defines to which interface the ring should bind to. It may be any address of | |
857 | the subnet configured on the interface we want to use. In general its the | |
858 | recommended to just use an address a node uses on this interface. | |
859 | ||
860 | rrp_mode:: | |
861 | Specifies the mode of the redundant ring protocol and may be passive, active or | |
862 | none. Note that use of active is highly experimental and not official | |
863 | supported. Passive is the preferred mode, it may double the cluster | |
864 | communication throughput and increases availability. | |
865 | ||
806ef12d DM |
866 | |
867 | Cluster Cold Start | |
868 | ------------------ | |
869 | ||
870 | It is obvious that a cluster is not quorate when all nodes are | |
871 | offline. This is a common case after a power failure. | |
872 | ||
873 | NOTE: It is always a good idea to use an uninterruptible power supply | |
8c1189b6 | 874 | (``UPS'', also called ``battery backup'') to avoid this state, especially if |
806ef12d DM |
875 | you want HA. |
876 | ||
8c1189b6 FG |
877 | On node startup, service `pve-manager` is started and waits for |
878 | quorum. Once quorate, it starts all guests which have the `onboot` | |
612417fd DM |
879 | flag set. |
880 | ||
881 | When you turn on nodes, or when power comes back after power failure, | |
882 | it is likely that some nodes boots faster than others. Please keep in | |
883 | mind that guest startup is delayed until you reach quorum. | |
806ef12d DM |
884 | |
885 | ||
d8742b0c DM |
886 | ifdef::manvolnum[] |
887 | include::pve-copyright.adoc[] | |
888 | endif::manvolnum[] |