Moving some things around

SUSE · Jan 31, 2024 · c6da1fa · c6da1fa
1 parent 16d31bc
commit c6da1fa
Show file tree

Hide file tree

Showing 5 changed files with 88 additions and 39 deletions.
diff --git a/xml/book_full_install.xml b/xml/book_full_install.xml
@@ -53,7 +53,7 @@
 <!-- Part: Installing nodes                                           -->
 <!-- ===================================================================== -->
  <part xml:id="part-install">
-  <title>Installing HA nodes</title>
+  <title>Installing cluster nodes</title>
   <info/>
   <xi:include href="ha_install.xml"/>
   <xi:include href="ha_bootstrap_install.xml"/>

diff --git a/xml/ha_add_nodes.xml b/xml/ha_add_nodes.xml
@@ -25,6 +25,19 @@
     </dm:docmanager>
   </info>
 
+  <sect1 xml:id="sec-ha-install-node-bootstrap">
+    <title>Adding nodes with <command>crm cluster join</command></title>
+    <para>
+
+    </para>
+  </sect1>
+
+  <sect1 xml:id="sec-ha-install-node-manual">
+    <title>Adding nodes manually</title>
+    <para>
+
+    </para>
+  </sect1>
 
   <sect1 xml:id="sec-ha-installation-autoyast">
   <title>Adding nodes with &ay;</title>

diff --git a/xml/ha_install.xml b/xml/ha_install.xml
@@ -4,21 +4,19 @@
   <!ENTITY % entities SYSTEM "generic-entities.ent">
     %entities;
 ]>
-<!-- Converted by suse-upgrade version 1.1 -->
+
 <chapter xmlns="http://docbook.org/ns/docbook"
  xmlns:xi="http://www.w3.org/2001/XInclude"
  xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
  xml:id="cha-ha-install">
-<?dbfo-need height="20em"?>
+
  <title>Installing &productname;</title>
  <info>
   <abstract>
-   <para>If you are setting up a &ha; cluster with &productnamereg; for the first time, the
-    easiest way is to start with a basic two-node cluster. You can also use the
-    two-node cluster to run some tests. Afterward, you can add more
-    nodes by cloning existing cluster nodes with &ay;. The cloned nodes will
-    have the same packages installed and the same system configuration as the
-    original ones.
+   <para>
+     The packages for configuring and managing a cluster are included in the &ha; installation pattern.
+     This pattern is only available after the &productname; extension (&slehaa;) is installed.
+     &slehaa; can be installed along with &sles; (&slsa;), or after &slsa; is already installed.
    </para>
   </abstract>
   <dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager">
@@ -33,13 +31,44 @@
   </dm:docmanager>
  </info>
 
- <sect1 xml:id="sec-ha-install-manual">
-  <title>Manual installation</title>
   <para>
-   For the manual installation of the packages for &ha; refer to
-   <xref linkend="article-installation"/>. It leads you through the setup of a
-   basic two-node cluster.
+    To install &slehaa; along with &slsa;, see the
+    <link xlink:href="https://documentation.suse.com/sles/15-SP5/html/SLES-all/cha-install.html#sec-yast-install-scc-registration">
+    <citetitle>&deploy;</citetitle> for &sles;</link>.
+    To install &slehaa; after &slsa; is already installed, use this procedure:
   </para>
- </sect1>
+  <itemizedlist>
+    <title>Requirements</title>
+    <listitem>
+      <para>
+        &sles; is installed and registered with the &scc;.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        You have an additional registration code for &productname;.
+      </para>
+    </listitem>
+  </itemizedlist>
+  <procedure xml:id="pro-ha-install-manual">
+    <title>Installing the &ha; packages</title>
+    <step>
+      <para>
+        Enable the &ha; extension:
+      </para>
+<screen>&prompt.user;<command>sudo SUSEConnect -p sle-ha/&product-ga;.&product-sp;/x86_64 -r <replaceable>ADDITIONAL_REGCODE</replaceable></command></screen>
+    </step>
+    <step>
+      <para>
+        Install the &ha; pattern:</para>
+<screen>&prompt.user;<command>sudo zypper install -t pattern ha_sles</command></screen>
+    </step>
+    <step>
+      <para>
+        Install the &ha; pattern on <emphasis>all</emphasis> machines that
+        will be part of your cluster.
+      </para>
+    </step>
+  </procedure>
 
 </chapter>
diff --git a/xml/ha_installation_overview.xml b/xml/ha_installation_overview.xml
@@ -24,5 +24,27 @@ You can also use a combination of both setup methods, for example: set up one no
       <dm:translation>yes</dm:translation>
     </dm:docmanager>
   </info>
+  <para>
+  If you are setting up a &ha; cluster with &productnamereg; for the first time, the
+    easiest way is to start with a basic two-node cluster. You can also use the
+    two-node cluster to run some tests. Afterward, you can add more
+    nodes by cloning existing cluster nodes with &ay;. The cloned nodes will
+    have the same packages installed and the same system configuration as the
+    original ones.
+  </para>
+
+  <sect1 xml:id="sec-ha-installation-workflow-options">
+    <title>Workflow options</title>
+    <para>
+
+    </para>
+  </sect1>
+
+  <sect1 xml:id="sec-ha-installation-preconfig-options">
+    <title>Preconfiguration options</title>
+    <para>
+
+    </para>
+  </sect1>
 
 </chapter>
diff --git a/xml/ha_yast_cluster.xml b/xml/ha_yast_cluster.xml
@@ -16,17 +16,6 @@
    <para>The &yast; cluster module allows you to set up a cluster manually
     (from scratch) or to modify options for an existing cluster.
    </para>
-   <para>
-    However, if you prefer an automated approach for setting up a cluster,
-    refer to <xref linkend="article-installation"/>. It describes how to install the
-    needed packages and leads you to a basic two-node cluster, which is
-    set up with the bootstrap scripts provided by the &crmshell;.
-   </para>
-   <para>
-    You can also use a combination of both setup methods, for example: set up
-    one node with &yast; cluster and then use one of the bootstrap scripts
-    to integrate more nodes (or vice versa).
-   </para>
   </abstract>
       <dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager">
         <dm:maintainer/>
@@ -211,7 +200,12 @@
     module from the command line:
    </para>
   <screen>&prompt.user;<command>sudo yast2 cluster</command></screen>
-
+  <para>
+    If you start the cluster module for the first time, it appears as a
+    wizard, guiding you through all the steps necessary for basic setup.
+    Otherwise, click the categories on the left panel to access the
+    configuration options for each step.
+  </para>
   <para>
    The following list shows an overview of the available screens in the
    &yast; cluster module. It also mentions whether the screen contains parameters that
@@ -229,9 +223,8 @@
      <important>
       <title>Redundant communication paths</title>
       <para>For a supported cluster setup two or more redundant communication
-       paths are required. The preferred way is to use network device bonding as
-       described in <xref linkend="cha-ha-netbonding"/>.</para>
-      <para>If this is impossible, you need to define a second communication
+       paths are required. The preferred way is to use network device bonding.
+       If this is impossible, you must define a second communication
        channel in &corosync;.</para>
      </important>
     </listitem>
@@ -279,14 +272,6 @@
     </listitem>
    </varlistentry>
   </variablelist>
-
-   <para>
-    If you start the cluster module for the first time, it appears as a
-    wizard, guiding you through all the steps necessary for basic setup.
-    Otherwise, click the categories on the left panel to access the
-    configuration options for each step.
-   </para>
-
    <note>
     <title>Settings in the &yast; <guimenu>Cluster</guimenu> module</title>
      <para>Some settings in the &yast; cluster module apply only to the
@@ -1019,7 +1004,7 @@ Finished with 1 errors.</screen>
       <command>crm&nbsp;status</command> command. If all nodes are
       online, the output should be similar to the following:
      </para>
-<screen>&prompt.root;crm status
+<screen>&prompt.root;<command>crm status</command>
 Cluster Summary:
   * Stack: corosync
   * Current DC: &node1; (version ...) - partition with quorum