Expected votes: 4
Highest expected: 4
Total votes: 4
-Quorum: 2
+Quorum: 3
Flags: Quorate
Membership information
Expected votes: 3
Highest expected: 3
Total votes: 3
-Quorum: 3
+Quorum: 2
Flags: Quorate
Membership information
~~~~~~~~~~~~~~~~~
We recommend to run any daemon which provides votes to corosync-qdevice as an
-unprivileged user. {pve} and Debian Stretch provide a package which is
-already configured to do so.
+unprivileged user. {pve} and Debian provides a package which is already
+configured to do so.
The traffic between the daemon and the cluster must be encrypted to ensure a
safe and secure QDevice integration in {pve}.
Tie Breaking
^^^^^^^^^^^^
-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
+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.
+Possible Negative Implications
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+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