Add SBD advice from archived TIDs (#359)

* Add note about /etc/crm/profiles.yml bsc#1202661 jsc#DOCTEAM-725 * Add SBD advice from TIDs bsc#1202661 jsc#DOCTEAM-725 * Add review suggestions
SUSE · Nov 30, 2023 · ccf8a89 · ccf8a89
1 parent 66871e7
commit ccf8a89
Show file tree

Hide file tree

Showing 2 changed files with 57 additions and 8 deletions.
diff --git a/xml/article_installation.xml b/xml/article_installation.xml
@@ -292,6 +292,14 @@
     </listitem>
    </varlistentry>
   </variablelist>
+  <note>
+    <title>Cluster configuration for different platforms</title>
+    <para>
+      The <command>crm cluster init</command> script detects the system environment (for example,
+      &ms; Azure) and adjusts certain cluster settings based on the profile for that environment.
+      For more information, see the file <filename>/etc/crm/profiles.yml</filename>.
+    </para>
+  </note>
  </sect1>
 
   <sect1 xml:id="sec-ha-inst-quick-installation">

diff --git a/xml/ha_storage_protection.xml b/xml/ha_storage_protection.xml
@@ -185,7 +185,7 @@
  </sect1>
 
  <sect1 xml:id="sec-ha-storage-protect-req">
-  <title>Requirements</title>
+  <title>Requirements and restrictions</title>
    <itemizedlist>
    <listitem>
     <para>You can use up to three SBD devices for storage-based fencing.
@@ -216,6 +216,18 @@
     <para>An SBD device can be shared between different clusters, as
      long as no more than 255 nodes share the device. </para>
    </listitem>
+   <listitem>
+     <para>
+       Fencing does not work with an asymmetric SBD setup. When using more
+       than one SBD device, all nodes must have a slot in all SBD devices.
+     </para>
+   </listitem>
+   <listitem>
+     <para>
+       When using more than one SBD device, all devices must have the same configuration,
+       for example, the same timeout values.
+     </para>
+   </listitem>
    <listitem>
     <para>For clusters with more than two nodes, you can also use SBD in
     <emphasis>diskless</emphasis> mode.
@@ -284,7 +296,8 @@
    <title>Calculation of timeouts</title>
     <para>
       When using SBD as a fencing mechanism, it is vital to consider the timeouts
-      of all components, because they depend on each other.
+      of all components, because they depend on each other. When using more than one
+      SBD device, all devices must have the same timeout values.
     </para>
     <variablelist>
      <varlistentry>
@@ -611,7 +624,8 @@ stonith-timeout = Timeout (msgwait) + 20%</screen>
     </step>
     <step>
      <para>If your SBD device resides on a multipath group, use the <option>-1</option>
-      and <option>-4</option> options to adjust the timeouts to use for SBD. For
+      and <option>-4</option> options to adjust the timeouts to use for SBD. If you initialized
+      more than one device, you must set the same timeout values for all devices. For
       details, see <xref linkend="sec-ha-storage-protect-watchdog-timings"/>.
       All timeouts are given in seconds:</para>
 <screen>&prompt.root;<command>sbd -d /dev/disk/by-id/<replaceable>DEVICE_ID</replaceable> -4 180</command><co xml:id="co-ha-sbd-msgwait"/> <command>-1 90</command><co xml:id="co-ha-sbd-watchdog"/> <command>create</command></screen>
@@ -689,6 +703,15 @@ Timeout (msgwait)  : 10
       <link xlink:href="https://www.suse.com/support/kb/doc/?id=000019356"/>.
     </para>
    </step>
+   <step>
+     <para>
+       Copy the configuration file to all nodes by using <command>csync2</command>:
+     </para>
+<screen>&prompt.root;<command>csync2 -xv</command></screen>
+     <para>
+       For more information, see <xref linkend="sec-ha-installation-setup-csync2"/>.
+     </para>
+   </step>
   </procedure>
 
  <para>After you have added your SBD devices to the SBD configuration file,
@@ -706,9 +729,18 @@ Timeout (msgwait)  : 10
      cluster services are started.</para>
    </step>
    <step>
-    <para>Restart the cluster services on each node:</para>
-    <screen>&prompt.root;<command>crm cluster restart</command></screen>
+    <para>Restart the cluster services on all nodes at once by using the <option>--all</option>
+     option:</para>
+    <screen>&prompt.root;<command>crm cluster restart --all</command></screen>
     <para> This automatically triggers the start of the SBD daemon. </para>
+    <important>
+     <title>Restart cluster services for SBD changes</title>
+     <para>
+       If any SBD metadata changes, you must restart the cluster services again. To keep critical
+       cluster resources running during the restart, consider putting the cluster into maintenance
+       mode first. For more information, see <xref linkend="cha-ha-maintenance"/>.
+     </para>
+   </important>
    </step>
   </procedure>
 
@@ -969,9 +1001,18 @@ SBD_WATCHDOG_TIMEOUT=5</screen>
       cluster services are started.</para>
     </step>
     <step>
-     <para>Restart the cluster services on each node:</para>
-     <screen>&prompt.root;<command>crm cluster restart</command></screen>
-     <para> This automatically triggers the start of the SBD daemon. </para>
+     <para>Restart the cluster services on all nodes at once by using the <option>--all</option>
+     option:</para>
+    <screen>&prompt.root;<command>crm cluster restart --all</command></screen>
+    <para> This automatically triggers the start of the SBD daemon. </para>
+    <important>
+     <title>Restart cluster services for SBD changes</title>
+     <para>
+       If any SBD metadata changes, you must restart the cluster services again. To keep critical
+       cluster resources running during the restart, consider putting the cluster into maintenance
+       mode first. For more information, see <xref linkend="cha-ha-maintenance"/>.
+     </para>
+   </important>
     </step>
     <step>
       <para>