pvecm: qdevice faq section improvements

[pve-docs.git] / pvecm.adoc

diff --git a/pvecm.adoc b/pvecm.adoc
index 0144d113a3adacc9bdd9784a5590e315525b7e82..86cfc76d96505077e275c13bf218eca11e6bc17f 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,34 @@ 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 there are no negative implications
+when setting up a QDevice. If it fails to work, you are as good as without
+QDevice at all.
+
+Adding/Deleting Nodes After QDevice 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 the QDevice first. After
+that, you can add or remove nodes normally. Once you have a cluster with an
+even node count again, you can set up the QDevice again as described above.
+
+Removing the QDevice
+^^^^^^^^^^^^^^^^^^^^
+
+If you used the official `pvecm` tool to add the QDevice, you can remove it trivially
+by running:
+
+----
+pve# pvecm qdevice remove
+----
+
+//Still TODO
+//^^^^^^^^^^
+//There ist still stuff to add here
 
 
 Corosync Configuration