Deployed 16cabbb to dev with MkDocs 1.6.1 and mike 2.1.3

Author: Doc Deploy Bot

dev/guides/ha-cluster/readme/index.html

@@ -905,6 +905,45 @@
     </span>
   </a>
 
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#dynamic-cluster-lifecycle" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Dynamic Cluster Lifecycle
+      
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="Dynamic Cluster Lifecycle">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#when-cluster-services-start-on-compute-nodes" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        When Cluster Services Start on Compute Nodes
+      
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#when-cluster-services-stop-on-compute-nodes" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        When Cluster Services Stop on Compute Nodes
+      
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
 
         <li class="md-nav__item">
@@ -1796,6 +1835,45 @@
     </span>
   </a>
 
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#dynamic-cluster-lifecycle" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Dynamic Cluster Lifecycle
+      
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="Dynamic Cluster Lifecycle">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#when-cluster-services-start-on-compute-nodes" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        When Cluster Services Start on Compute Nodes
+      
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#when-cluster-services-stop-on-compute-nodes" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        When Cluster Services Stop on Compute Nodes
+      
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
 
         <li class="md-nav__item">
@@ -1855,6 +1933,7 @@ <h2 id="table-of-contents">Table of Contents</h2>
 <li><a href="#common-issues">Common Issues</a></li>
 <li><a href="#testing-fence-operations">Testing Fence Operations</a></li>
 <li><a href="#gfs2-file-system-configuration">GFS2 File System Configuration</a></li>
+<li><a href="#dynamic-cluster-lifecycle">Dynamic Cluster Lifecycle</a></li>
 <li><a href="#references">References</a></li>
 </ul>
 <h2 id="background-pacemaker-and-corosync">Background: Pacemaker and Corosync</h2>
@@ -2232,6 +2311,40 @@ <h2 id="gfs2-file-system-configuration">GFS2 File System Configuration</h2>
 <ul>
 <li><a href="https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/configuring_and_managing_high_availability_clusters/assembly_configuring-gfs2-in-a-cluster-configuring-and-managing-high-availability-clusters">Configuring a GFS2 File System in a Cluster</a></li>
 </ul>
+<h2 id="dynamic-cluster-lifecycle">Dynamic Cluster Lifecycle</h2>
+<p>Unlike traditional HA clusters that run continuously on all nodes, NNF manages Pacemaker cluster services dynamically on compute nodes based on workflow requirements. Cluster services run <strong>continuously on the Rabbit</strong> but are <strong>started and stopped dynamically on compute nodes</strong>.</p>
+<h3 id="when-cluster-services-start-on-compute-nodes">When Cluster Services Start on Compute Nodes</h3>
+<p>NNF software starts Pacemaker/Corosync cluster services on compute nodes when:</p>
+<ol>
+<li>A workflow requests GFS2 storage</li>
+<li>The NNF software provisions the GFS2 file system</li>
+<li>Compute nodes need to mount the shared storage</li>
+</ol>
+<p>At this point, cluster services are started on participating compute nodes, they join the Rabbit's cluster, fencing is enabled, and the GFS2 file system is mounted.</p>
+<blockquote>
+<p>See <a href="https://nearnodeflash.github.io/latest/guides/storage-profiles/readme/">Storage Profiles</a> for more information about how to start cluster services using the <code>PreActivate</code> command.</p>
+</blockquote>
+<h3 id="when-cluster-services-stop-on-compute-nodes">When Cluster Services Stop on Compute Nodes</h3>
+<p>When the GFS2 workflow completes:</p>
+<ol>
+<li>The GFS2 file system is unmounted from all compute nodes</li>
+<li>Storage resources are cleaned up</li>
+<li>Pacemaker/Corosync cluster services are stopped on compute nodes</li>
+<li>The Rabbit continues running cluster services</li>
+</ol>
+<blockquote>
+<p>See <a href="https://nearnodeflash.github.io/latest/guides/storage-profiles/readme/">Storage Profiles</a> for more information about how to stop cluster services using the <code>PostDeactivate</code> command.</p>
+</blockquote>
+<p>This dynamic lifecycle means:</p>
+<ul>
+<li><strong>Rabbit runs cluster services continuously</strong>: Always ready to accept compute nodes</li>
+<li><strong>Compute node services are transient</strong>: They run only for the duration of GFS2 workflows</li>
+<li><strong>Resource efficiency</strong>: Cluster overhead on compute nodes is incurred only when needed</li>
+<li><strong>Reduced complexity</strong>: No long-running cluster services to maintain on compute nodes between jobs</li>
+</ul>
+<blockquote>
+<p><strong>Note:</strong> The cluster configuration (node membership, quorum votes, STONITH resources) is set up during system provisioning and persists on all nodes. Only the cluster <em>services</em> on compute nodes are started and stopped dynamically.</p>
+</blockquote>
 <h2 id="references">References</h2>
 <ul>
 <li><a href="https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/configuring_and_managing_high_availability_clusters/">Red Hat: Configuring and Managing High Availability Clusters</a></li>