Move crm cluster join to bootstrap chapter

xml/book_full_install.xml

@@ -67,7 +67,7 @@
   <xi:include href="ha_sbd_watchdog.xml"/>
   <xi:include href="ha_bootstrap_install.xml"/>
   <xi:include href="ha_yast_cluster.xml"/>
-  <xi:include href="ha_add_nodes.xml"/>
+  <xi:include href="ha_autoyast_deploy.xml"/>
  </part>
 
 <!-- ===================================================================== -->

xml/ha_autoyast_deploy.xml

@@ -0,0 +1,148 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?xml-stylesheet href="urn:x-suse:xslt:profiling:docbook51-profile.xsl"
+ type="text/xml"
+ title="Profiling step"?>
+<!DOCTYPE chapter
+[
+  <!ENTITY % entities SYSTEM "generic-entities.ent">
+    %entities;
+]>
+
+<!--trichardson 2024-06-03: sec- instead of cha- to avoid changing existing IDs-->
+<chapter xml:id="sec-ha-installation-autoyast" xml:lang="en"
+ xmlns="http://docbook.org/ns/docbook" version="5.1"
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ xmlns:xlink="http://www.w3.org/1999/xlink">
+  <title>Deploying nodes with &ay;</title>
+  <info>
+    <abstract>
+      <para>
+        After you have installed and set up a two-node cluster, you can extend the
+        cluster by cloning existing nodes with &ay; and adding the clones to the cluster.
+      </para>
+      <para>&ay; uses profiles that contains installation and configuration data.
+        A profile tells &ay; what to install and how to configure the installed system to
+        get a ready-to-use system in the end. This profile can then be used
+        for mass deployment in different ways (for example, to clone existing cluster nodes).
+      </para>
+      <para>
+        For detailed instructions on how to use &ay; in various scenarios, see the
+        <link xlink:href="https://documentation.suse.com/sles-15/html/SLES-all/book-autoyast.html">
+        &ayguide; for &sls; &productnumber;</link>.
+      </para>
+    </abstract>
+    <dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager">
+      <dm:bugtracker></dm:bugtracker>
+      <dm:translation>yes</dm:translation>
+    </dm:docmanager>
+  </info>
+
+
+
+  <important>
+    <title>Identical hardware</title>
+    <para>
+     <xref linkend="pro-ha-installation-clone-node"/> assumes you are rolling
+     out &productname; &productnumber; to a set of machines with identical hardware
+     configurations.
+    </para>
+    <para>
+     If you need to deploy cluster nodes on non-identical hardware, refer to the
+     &deploy; for &sls; &productnumber;,
+     chapter <citetitle>Automated Installation</citetitle>, section
+     <citetitle>Rule-Based Autoinstallation</citetitle>.
+    </para>
+  </important>
+
+  <procedure xml:id="pro-ha-installation-clone-node">
+   <title>Cloning a cluster node with &ay;</title>
+   <step>
+    <para>
+     Make sure the node you want to clone is correctly installed and
+     configured. For details, see the &haquick; or
+     <xref linkend="cha-ha-ycluster"/>.
+    </para>
+   </step>
+   <step>
+    <para>
+     Follow the description outlined in the &sle;
+     &productnumber; &deploy; for simple mass
+     installation. This includes the following basic steps:
+    </para>
+    <substeps performance="required">
+     <step>
+      <para>
+       Creating an &ay; profile. Use the &ay; GUI to create and modify
+       a profile based on the existing system configuration. In &ay;,
+       choose the <guimenu>&ha;</guimenu> module and click the
+       <guimenu>Clone</guimenu> button. If needed, adjust the configuration
+       in the other modules and save the resulting control file as XML.
+      </para>
+      <para>
+       If you have configured DRBD, you can select and clone this module in
+       the &ay; GUI, too.
+      </para>
+     </step>
+     <step>
+      <para>
+       Determining the source of the &ay; profile and the parameter to
+       pass to the installation routines for the other nodes.
+      </para>
+     </step>
+     <step>
+      <para>
+       Determining the source of the &sls; and &productname;
+       installation data.
+      </para>
+     </step>
+     <step>
+      <para>
+       Determining and setting up the boot scenario for autoinstallation.
+      </para>
+     </step>
+     <step>
+      <para>
+       Passing the command line to the installation routines, either by
+       adding the parameters manually or by creating an
+       <filename>info</filename> file.
+      </para>
+     </step>
+     <step>
+      <para>
+       Starting and monitoring the autoinstallation process.
+      </para>
+     </step>
+    </substeps>
+   </step>
+  </procedure>
+
+  <para>
+   After the clone has been successfully installed, execute the following
+   steps to make the cloned node join the cluster:
+  </para>
+
+  <procedure xml:id="pro-ha-installation-clone-start">
+   <title>Bringing the cloned node online</title>
+   <step>
+    <para>
+     Transfer the key configuration files from the already configured nodes
+     to the cloned node with &csync; as described in
+     <xref linkend="sec-ha-installation-setup-csync2"/>.
+    </para>
+   </step>
+   <step>
+    <para>
+     To bring the node online, start the cluster services on the cloned
+     node as described in <xref linkend="sec-ha-installation-start"/>.
+    </para>
+   </step>
+  </procedure>
+
+  <para>
+   The cloned node now joins the cluster because the
+   <filename>/etc/corosync/corosync.conf</filename> file has been applied to
+   the cloned node via &csync;. The CIB is automatically synchronized
+   among the cluster nodes.
+  </para>
+
+</chapter>