Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify QDevice/QNetd configuration #405

Merged
merged 3 commits into from
Sep 4, 2024
Merged

Clarify QDevice/QNetd configuration #405

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d0eb636
Clarify QDevice/QNetd configuration
tahliar Aug 2, 2024
abec557
Add root
tahliar Aug 13, 2024
362f66d
Apply suggestions from editorial review
tahliar Sep 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 29 additions & 18 deletions xml/ha_qdevice-qnetd.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -207,8 +207,8 @@
<sect1 xml:id="sec-ha-qdevice-setup-qnetd">
<title>Setting up the &qnet; server</title>
<para>
The &qnet; server is not part of the cluster stack, and it is also
not a real member of your cluster. As such, you cannot move resources
The &qnet; server runs outside the cluster, and can support multiple clusters
tahliar marked this conversation as resolved.
Show resolved Hide resolved
(as long as each cluster has a unique name). As such, you cannot move resources
to this server.
</para>
<para>
Expand Down Expand Up @@ -251,8 +251,8 @@

<para>
Your &qnet; server is ready to accept connections from a &qdevice; client
<systemitem>corosync-qdevice</systemitem>.
Further configuration is not needed.
(<systemitem>corosync-qdevice</systemitem>).
Further configuration is handled by &crmsh; when you connect &qdevice; clients.
</para>
</sect1>

Expand All @@ -264,6 +264,12 @@
of your cluster, or you can add them later. This procedure documents how
to add them later.
</para>
<important role="compact">
<para>
To complete the &qnet; configuration, the clients must have SSH access
tahliar marked this conversation as resolved.
Show resolved Hide resolved
to the &qnet; server.
</para>
</important>
<procedure>
<step>
<para>
Expand All @@ -289,22 +295,27 @@ Heuristics COMMAND to run with absolute path; For multiple commands, use ";" to
remaining fields, you can accept the default values or change them
if required.
</para>
<important>
<title><literal>SBD_WATCHDOG_TIMEOUT</literal> for diskless SBD and &qdevice;</title>
<para>
If you use &qdevice; with diskless SBD, the <literal>SBD_WATCHDOG_TIMEOUT</literal>
value must be greater than &qdevice;'s <literal>sync_timeout</literal> value,
or SBD will time out and fail to start.
</para>
<para>
The default value for <literal>sync_timeout</literal> is 30 seconds.
Therefore, in the file <filename>/etc/sysconfig/sbd</filename>, make sure
that <literal>SBD_WATCHDOG_TIMEOUT</literal> is set to a greater value,
such as <literal>35</literal>.
</para>
</important>
</step>
</procedure>
<para>
The script configures &qdevice; on the nodes and completes the &qnet; configuration
on the &qnet; server, including generating CA and server certificates, starting the
&qnet; daemon, and updating the cluster's quorum configuration.
</para>
<important>
<title><literal>SBD_WATCHDOG_TIMEOUT</literal> for diskless SBD and &qdevice;</title>
<para>
If you use &qdevice; with diskless SBD, the <literal>SBD_WATCHDOG_TIMEOUT</literal>
value must be greater than &qdevice;'s <literal>sync_timeout</literal> value,
or SBD will time out and fail to start.
</para>
<para>
The default value for <literal>sync_timeout</literal> is 30 seconds.
Therefore, in the file <filename>/etc/sysconfig/sbd</filename>, make sure
that <literal>SBD_WATCHDOG_TIMEOUT</literal> is set to a greater value,
such as <literal>35</literal>.
</para>
</important>
</sect1>

<sect1 xml:id="sec-ha-qdevice-heuristic">
Expand Down