Add crm cluster join procedure

xml/ha_add_nodes.xml

@@ -25,10 +25,79 @@
     </dm:docmanager>
   </info>
 
-  <sect1 xml:id="sec-ha-install-node-bootstrap">
+  <sect1 xml:id="sec-ha-install-node-join-bootstrap">
     <title>Adding nodes with <command>crm cluster join</command></title>
     <para>
-
+      You can add more nodes to the cluster with the <command>crm cluster join</command> bootstrap script.
+      The script only needs access to an existing cluster node, and completes the basic setup
+      on the current machine automatically.
+    </para>
+    <para>
+      For more information, run the <command>crm cluster join --help</command> command.
+    </para>
+    <procedure xml:id="pro-ha-install-node-join-bootstrap">
+    <title>Adding nodes with <command>crm cluster join</command></title>
+    <step>
+      <para>
+        Log in to a node as &rootuser;, or as a user with <command>sudo</command> privileges.
+      </para>
+    </step>
+    <step>
+      <para>
+        Start the bootstrap script:
+      </para>
+      <itemizedlist>
+        <listitem>
+          <para>
+            If you set up the first node as &rootuser;, you can run this command with
+            no additional parameters:
+          </para>
+<screen>&prompt.root;<command>crm cluster join</command></screen>
+        </listitem>
+        <listitem>
+          <para>
+            If you set up the first node as a <command>sudo</command> user, you must
+            specify the user and node with the <option>-c</option> option:
+          </para>
+<screen>&prompt.user;<command>sudo crm cluster join -c <replaceable>USER</replaceable>@&node1;</command></screen>
+        </listitem>
+        <listitem>
+          <para>
+            If you set up the first node as a <command>sudo</command> user with SSH agent forwarding,
+            use the following command:
+          </para>
+<screen>&prompt.user;<command>sudo --preserve-env=SSH_AUTH_SOCK crm cluster join --use-ssh-agent -c <replaceable>USER</replaceable>@&node1;</command></screen>
+        </listitem>
+      </itemizedlist>
+      <para>
+        If NTP is not configured to start at boot time, a message
+        appears. The script also checks for a hardware watchdog device.
+        You are warned if none is present.
+      </para>
+    </step>
+    <step>
+      <para>
+      If you did not already specify <systemitem class="server">&node1;</systemitem>
+      with <option>-c</option>, you will be prompted for the IP address of the first node.
+      </para>
+    </step>
+    <step>
+      <para>
+        If you did not already configure passwordless SSH access between
+        both machines, you will be prompted for the password of the first node.
+      </para>
+      <para>
+        After logging in to the specified node, the script copies the
+        &corosync; configuration, configures SSH and &csync;,
+        brings the current machine online as a new cluster node, and
+        starts the service needed for &hawk2;.
+      </para>
+    </step>
+    </procedure>
+    <para>
+      Repeat this procedure for each node. You can check the status of the cluster at any time
+      with the <command>crm status</command> command, or by logging in to &hawk2; and navigating to
+      <menuchoice><guimenu>Status</guimenu><guimenu>Nodes</guimenu></menuchoice>.
     </para>
   </sect1>