public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
* [pve-devel] [PATCH v2 docs] pvecm: add qdevice status flag explanation
@ 2023-07-25 11:00 Aaron Lauterer
  2023-07-25 15:21 ` [pve-devel] applied: " Thomas Lamprecht
  0 siblings, 1 reply; 2+ messages in thread
From: Aaron Lauterer @ 2023-07-25 11:00 UTC (permalink / raw)
  To: pve-devel

They are underdocumented and finding information is not that easy.

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
changes:
* added reference anchor for easier linking
* use link to manpages.debian.org instead of github


the corosync-doc package does ship HTML documentation, but no man pages,
    therefore only the link

 pvecm.adoc | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/pvecm.adoc b/pvecm.adoc
index 45271e8..cd8e40d 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -1082,6 +1082,22 @@ Membership information
 
 ----
 
+[[pvecm_qdevice_status_flags]]
+QDevice Status Flags
+^^^^^^^^^^^^^^^^^^^^
+
+The status output of the QDevice, as seen above, will usually contain three
+columns:
+
+* `A` / `NA`: Alive or Not Alive. Indicates if the communication to the external
+    `corosync-qndetd` daemon works.
+* `V` / `NV`: If the QDevice will cast a vote for the node. In a split-brain
+    situation, where the corosync connection between the nodes is down, but they
+    both can still communicate with the external `corosync-qnetd` daemon,
+    only one node will get the vote.
+* `MW` / `NMW`: Master wins (`MV`) or not (`NMW`). Default is `NMW`, see footnote:[`votequorum_qdevice_master_wins` manual page https://manpages.debian.org/bookworm/libvotequorum-dev/votequorum_qdevice_master_wins.3.en.html].
+* `NR`: QDevice is not registered.
+
 
 Frequently Asked Questions
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
-- 
2.39.2





^ permalink raw reply	[flat|nested] 2+ messages in thread

* [pve-devel] applied: [PATCH v2 docs] pvecm: add qdevice status flag explanation
  2023-07-25 11:00 [pve-devel] [PATCH v2 docs] pvecm: add qdevice status flag explanation Aaron Lauterer
@ 2023-07-25 15:21 ` Thomas Lamprecht
  0 siblings, 0 replies; 2+ messages in thread
From: Thomas Lamprecht @ 2023-07-25 15:21 UTC (permalink / raw)
  To: Proxmox VE development discussion, Aaron Lauterer

On 25/07/2023 13:00, Aaron Lauterer wrote:
> They are underdocumented and finding information is not that easy.
> 
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
> changes:
> * added reference anchor for easier linking
> * use link to manpages.debian.org instead of github
> 
> 
> the corosync-doc package does ship HTML documentation, but no man pages,
>     therefore only the link
> 
>  pvecm.adoc | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
>

applied but split the overly long footnote line (only xref ones need
to be a single line due to our limited parser, but footnotes aren't
looked for by it so there it doesn't matter), thanks!




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-07-25 15:21 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-07-25 11:00 [pve-devel] [PATCH v2 docs] pvecm: add qdevice status flag explanation Aaron Lauterer
2023-07-25 15:21 ` [pve-devel] applied: " Thomas Lamprecht

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal