pvecm qdevice: add some FAQ points

[pve-docs.git] / pvecm.adoc

diff --git a/pvecm.adoc b/pvecm.adoc
index 0144d113a3adacc9bdd9784a5590e315525b7e82..110f4df0cfa7ca006a855da716cd360033fb1583 100644 (file)
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -778,7 +778,7 @@ subsystem based on an external running third-party arbitrator's decision.
 Its primary use is to allow a cluster to sustain more node failures than
 standard quorum rules allow. This can be done safely as the external device
 can see all nodes and thus choose only one set of nodes to give its vote.
-This will only be done if said set of nodes can quorate (again) when
+This will only be done if said set of nodes can have quorum (again) when
 receiving the third-party vote.
 
 Currently only 'QDevice Net' is supported as a third-party arbitrator. It is
@@ -897,10 +897,24 @@ In case of a tie, where two same-sized cluster partitions cannot see each
 other but the QDevice, the QDevice chooses randomly one of those partitions and
 provides a vote to it.
 
-Still TODO
-^^^^^^^^^^
+Possible Negative Implications
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-There ist still stuff to add here
+For clusters with an even node count you do not get any negative implications
+when setting up a QDevice. If it fails to work, you are as good as without
+QDevice at all.
+
+Adding/Deleting Nodes Once QDevice Got Setup
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+If you want to add a new node or remove an existing one from a cluster with a
+QDevice setup, you need to remove it first. After that, you can add or remove
+nodes normally. Once you have again a cluster with an even node count you can
+also setup the QDevice again as described above.
+
+//Still TODO
+//^^^^^^^^^^
+//There ist still stuff to add here
 
 
 Corosync Configuration