Merge pull request #302108 from tfitzmac/0701edit4

copy edit

Author: denrea

articles/cyclecloud/how-to/bursting/setup-instructions-for-cloud-bursting.md

@@ -2,20 +2,20 @@
 title: Cloud Bursting Setup Instruction
 description: Learn how to set up Cloud bursting using Azure CycleCloud and Slurm.
 author: vinil-v
-ms.date: 04/17/2025
+ms.date: 07/01/2025
 ms.author: padmalathas
 ---
 
-# Setup Instructions
+# Setup instructions
 
-After we have the prerequisites ready, we can follow these steps to integrate the external Slurm Scheduler node with the CycleCloud cluster:
+After you prepare the prerequisites, follow these steps to integrate the external Slurm Scheduler node with the CycleCloud cluster:
 
-## Importing a Cluster Using the Slurm Headless Template in CycleCloud
+## Import a cluster by using the Slurm headless template in CycleCloud
 
-- This step must be executed on the **CycleCloud VM**.
-- Make sure that the **CycleCloud 8.6.4 VM** is running and accessible via the `cyclecloud` CLI.
-- Execute the `cyclecloud-project-build.sh` script and provide the desired cluster name (for example, `hpc1`). This sets a custom project based on the `cyclecloud-slurm-3.0.9` version and import the cluster using the Slurm headless template.
-- In the example provided, `<clustername>` is used as the cluster name. Choose any cluster name you like, but same name must be consistently used throughout the entire setup.
+- Run this step on the **CycleCloud VM**.
+- Make sure that the **CycleCloud 8.6.4 VM** is running and accessible through the `cyclecloud` CLI.
+- Run the `cyclecloud-project-build.sh` script and enter the cluster name you want (for example, `hpc1`). The script sets a custom project based on the `cyclecloud-slurm-3.0.9` version and imports the cluster by using the Slurm headless template.
+- In the following example, `<clustername>` is the cluster name. You can choose any cluster name you want, but you must use the same name throughout the entire setup.
 
 
 ```bash
@@ -45,20 +45,20 @@ Fetching CycleCloud project
 Uploading CycleCloud project to the locker
 ```
 
-## Slurm Scheduler Installation and Configuration
+## Slurm scheduler installation and configuration
 
-- A VM should be deployed using the specified **AlmaLinux HPC 8.7** or **Ubuntu HPC 22.04** image. 
-- If you already have a Slurm Scheduler installed, you can skip this step. However, it's advisable to review the script to make sure it's compatible with your current setup.
-- Run the Slurm scheduler installation script (`slurm-scheduler-builder.sh`) and provide the cluster name (`<clustername>`) when prompted.
-- This script sets up the NFS server and installs and configures the Slurm Scheduler.
+- Deploy a VM by using the **AlmaLinux HPC 8.7** or **Ubuntu HPC 22.04** image.
+- If you already have a Slurm scheduler installed, you can skip this step. However, we recommend that you review the script to make sure it's compatible with your current setup.
+- Run the Slurm scheduler installation script (`slurm-scheduler-builder.sh`) and enter the cluster name (`<clustername>`) when prompted.
+- The script sets up the NFS server and installs and configures the Slurm scheduler.
 - If you're using an external NFS server, you can delete the NFS setup entries from the script.
 
 ```bash
 git clone https://github.com/Azure/cyclecloud-slurm.git
 cd cyclecloud-slurm/cloud_bursting/slurm-23.11.9-1/scheduler
 sh slurm-scheduler-builder.sh
 ```
-Output: 
+Output:
 
 ```bash
 ------------------------------------------------------------------------------------------------------------------------------
@@ -74,20 +74,20 @@ Scheduler Hostname: <scheduler hostname>
 NFSServer IP Address: 10.222.xxx.xxx
 ```
 
-## CycleCloud UI Configuration
+## CycleCloud UI configuration
 
-- Access the **CycleCloud UI** and navigate to the settings for the `<clustername>` cluster.
-- Edit the cluster settings to configure the VM SKUs and networking options as needed.
+- Access the **CycleCloud UI** and go to the settings for the `<clustername>` cluster.
+- Edit the cluster settings to set up the VM versions and networking options.
 - In the **Network Attached Storage** section, enter the NFS server IP address for the `/sched` and `/shared` mounts.
 - On the Advance setting tab, from the dropdown menu choose the OS: either **Ubuntu 22.04** or **AlmaLinux 8** based on the scheduler VM.
-- Once all settings are configured, click **Save** and then **Start** the `<clustername>` cluster.
+- When you finish configuring the settings, select **Save** and then **Start** the `<clustername>` cluster.
 
 ![NFS settings](../../images/slurm-cloud-burst/cyclecloud-ui-config.png)
 
 ## CycleCloud Autoscaler Integration on Slurm Scheduler
 
-- Integrate Slurm with CycleCloud using the `cyclecloud-integrator.sh` script.
-- Provide CycleCloud details (username, password, and ip address) when prompted.
+- Integrate Slurm with CycleCloud by using the `cyclecloud-integrator.sh` script.
+- Enter your CycleCloud username, password, and IP address when prompted.
 
 ```bash
 cd cyclecloud-slurm/cloud_bursting/slurm-23.11.9-1/scheduler
@@ -115,19 +115,19 @@ CycleCloud URL: https://<ip address>
 
 ## User and Group Setup (Optional)
 
-- Ensure consistent user and group IDs across all nodes.
-- It's advisable to use a centralized User Management system like LDAP to maintain consistent UID and GID across all nodes.
-- In this example, we're using the `useradd_example.sh` script to create a test user `<username>` and a group for job submission. (User `<username>` already exists in CycleCloud)
+- Make sure user and group IDs are consistent across all nodes.
+- To keep UID and GID consistent across all nodes, use a centralized User Management system like LDAP.
+- In this example, use the `useradd_example.sh` script to create a test user `<username>` and a group for job submission. (User `<username>` already exists in CycleCloud)
 
 ```bash
 cd cyclecloud-slurm/cloud_bursting/slurm-23.11.9-1/scheduler
 sh useradd_example.sh
 ```
 
-## Testing the Setup
+## Testing the setup
 
-- Log in as a test user (example, `<username>`) on the Scheduler node.
-- Submit a test job to verify that the setup is functioning correctly.
+- Sign in as a test user (for example, `<username>`) on the scheduler node.
+- Submit a test job to verify that the setup is working correctly.
 
 ```bash
 su - <username>
@@ -146,6 +146,6 @@ Last login: Tue May 14 04:54:51 UTC 2024 on pts/0
 ```
 ![Node Creation](../../images/slurm-cloud-burst/cyclecloud-ui-new-node.png)
 
-You should see the job running successfully, indicating a successful integration with CycleCloud.
+You should see the job running successfully, which indicates a successful integration with CycleCloud.
 
 For more information and advanced configurations, see the scripts and documentation within this repository.

articles/cyclecloud/how-to/bursting/slurm-cloud-bursting-setup.md

@@ -2,70 +2,69 @@
 title: Cloud Bursting Using Azure CycleCloud and Slurm
 description: Learn how to configure Cloud bursting using Azure CycleCloud and Slurm.
 author: vinil-v
-ms.date: 04/17/2025
+ms.date: 07/01/2025
 ms.author: padmalathas
 ---
 
-# What is Cloud Bursting?
+# What is cloud bursting?
 
-Cloud bursting is a configuration in cloud computing that allows an organization to handle peaks in IT demand by using a combination of private and public clouds. When the resources in a private cloud reach their maximum capacity, the overflow traffic is directed to a public cloud to ensure there's no interruption in services. This setup provides flexibility and cost savings, as you only pay for the supplemental resources when there's a demand for them.
+Cloud bursting is a configuration in cloud computing that helps your organization handle peaks in IT demand by using a combination of private and public clouds. When the resources in a private cloud reach their maximum capacity, the configuration directs the overflow traffic to a public cloud. This setup ensures there's no interruption in services. Cloud bursting provides flexibility and cost savings, as you only pay for the supplemental resources when there's a demand for them.
 
-For example, an application can run on a private cloud and "burst" to a public cloud only when necessary to meet peak demands. This approach helps avoid the costs associated with maintaining extra capacity that isn't always in use.
+For example, an application can run on a private cloud and "burst" to a public cloud only when necessary to meet peak demands. This approach helps you avoid the costs associated with maintaining extra capacity that isn't always in use.
 
-Cloud bursting can be used in various scenarios, such as enabling on-premises workloads to be sent to the cloud for processing, known as hybrid HPC (High-Performance Computing). It allows users to optimize their resource utilization and cost efficiency while accessing the scalability and flexibility of the cloud.
+You can use cloud bursting in various scenarios, such as enabling on-premises workloads to be sent to the cloud for processing, known as hybrid HPC (High-Performance Computing). It allows you to optimize your resource utilization and cost efficiency while accessing the scalability and flexibility of the cloud.
 
 ## Overview
 
 This document offers a step-by-step guide on installing and configuring a Slurm scheduler to burst computing resources into the cloud using Azure CycleCloud. It explains how to create a hybrid HPC environment by extending on-premises Slurm clusters into Azure, allowing for seamless access to scalable and flexible cloud computing resources. The guide provides a practical example of optimizing compute capacity by integrating local infrastructure with cloud-based solutions.
 
 
-## Requirements to Setup Slurm Cloud Bursting Using CycleCloud on Azure
+## Requirements to Set Up Slurm Cloud Bursting Using CycleCloud on Azure
 
 ## Azure subscription account
-You must obtain an Azure subscription or be assigned as an Owner role of the subscription.
+You must have an Azure subscription or be assigned the Owner role for a subscription.
 
-* To create an Azure subscription, go to the [Create a Subscription](/azure/cost-management-billing/manage/create-subscription#create-a-subscription) documentation.
+* To create an Azure subscription, see [Create a Subscription](/azure/cost-management-billing/manage/create-subscription#create-a-subscription).
 * To access an existing subscription, go to the [Azure portal](https://portal.azure.com/).
 
 ## Network infrastructure
-If you intend to create a Slurm cluster entirely within Azure, you must deploy both the head nodes and the CycleCloud compute nodes within a single Azure Virtual Network (VNET). 
+To create a Slurm cluster entirely within Azure, deploy both the head nodes and the CycleCloud compute nodes within a single Azure Virtual Network (VNET). 
 
 ![Slurm cluster](../../images/slurm-cloud-burst/slurm-cloud-burst-architecture.png)
 
-To create a hybrid HPC cluster with head nodes on your on-premises corporate network and compute nodes in Azure, set up a [Site-to-Site](/azure/vpn-gateway/tutorial-site-to-site-portal) VPN or an [ExpressRoute](/azure/expressroute/) connection. This links your network to the Azure VNET. The head nodes must be able to connect to Azure services online. You might need to work with your network administrator to set this up.
-
-## Network Ports and Security
-The following NSG rules must be configured for successful communication between Master node, CycleCloud server, and compute nodes.
+To create a hybrid HPC cluster with head nodes on your on-premises corporate network and compute nodes in Azure, set up a [Site-to-Site](/azure/vpn-gateway/tutorial-site-to-site-portal) VPN or an [ExpressRoute](/azure/expressroute/) connection. This setup links your network to the Azure VNET. The head nodes must be able to connect to Azure services online. You might need to work with your network administrator to set up this connection.
 
+## Network ports and security
+To enable communication between the primary node, CycleCloud server, and compute nodes, configure the following NSG rules.
 
 | **Service**                        | **Port**        | **Protocol** | **Direction**    | **Purpose**                                                            | **Requirement**                                                                 |
 |------------------------------------|-----------------|--------------|------------------|------------------------------------------------------------------------|---------------------------------------------------------------------------------|
-| **SSH (Secure Shell)**             | 22              | TCP          | Inbound/Outbound | Secure command-line access to the Slurm Master node                     | Open on both on-premises firewall and Azure NSGs                                |
-| **Slurm Control (slurmctld, slurmd)** | 6817, 6818   | TCP          | Inbound/Outbound | Communication between Slurm Master and compute nodes                    | Open in on-premises firewall and Azure NSGs                                     |
-| **Munge Authentication Service**   | 4065            | TCP          | Inbound/Outbound | Authentication between Slurm Master and compute nodes                   | Open on both on-premises network and Azure NSGs                                 |
-| **CycleCloud Service**             | 443             | TCP          | Outbound         | Communication between Slurm Master node and Azure CycleCloud            | Allow outbound connections to Azure CycleCloud services from the Slurm Master node |
-| **NFS ports**                      | 2049            | TCP          | Inbound/Outbound | Shared filesystem access between Master node and Azure CycleCloud       | Open on both on-premises network and Azure NSGs                                 |
-| **LDAP port** (Optional)           | 389             | TCP          | Inbound/Outbound | Centralized authentication mechanism for user management                | Open on both on-premises network and Azure NSGs                             
+| **SSH (Secure Shell)**             | 22              | TCP          | Inbound/Outbound | Secure command-line access to the Slurm primary node                   | Open on both on-premises firewall and Azure NSGs                                |
+| **Slurm Control (slurmctld, slurmd)** | 6817, 6818   | TCP          | Inbound/Outbound | Communication between Slurm primary and compute nodes                  | Open in on-premises firewall and Azure NSGs                                     |
+| **Munge Authentication Service**   | 4065            | TCP          | Inbound/Outbound | Authentication between Slurm primary and compute nodes                   | Open on both on-premises network and Azure NSGs                                 |
+| **CycleCloud Service**             | 443             | TCP          | Outbound         | Communication between Slurm primary node and Azure CycleCloud            | Allow outbound connections to Azure CycleCloud services from the Slurm primary node |
+| **NFS ports**                      | 2049            | TCP          | Inbound/Outbound | Shared filesystem access between primary node and Azure CycleCloud       | Open on both on-premises network and Azure NSGs                                 |
+| **LDAP port** (Optional)           | 389             | TCP          | Inbound/Outbound | Centralized authentication mechanism for user management                | Open on both on-premises network and Azure NSGs
 
-Refer [Slurm Network Configuration Guide](https://slurm.schedmd.com/network.html)
+See [Slurm Network Configuration Guide](https://slurm.schedmd.com/network.html).
 
-## Software Requirement
+## Software requirements
 
-- **OS Version**: AlmaLinux release 8.x or Ubuntu 22.04
-- **CycleCloud Version**: 8.x or later
-- **CycleCloud-Slurm Project Version**: 3.0.x 
+- **OS version**: AlmaLinux release 8.x or Ubuntu 22.04
+- **CycleCloud version**: 8.x or later
+- **CycleCloud-Slurm project version**: 3.0.x
 
-## NFS File server
-A shared file system between the external Slurm Scheduler node and the CycleCloud cluster. You can use Azure NetApp Files, Azure Files, NFS, or other methods to mount the same file system on both sides. In this example, we're using a Scheduler VM as an NFS server.
+## NFS file server
+A shared file system between the external Slurm scheduler node and the CycleCloud cluster. You can use Azure NetApp Files, Azure Files, NFS, or other methods to mount the same file system on both sides. In this example, use a scheduler VM as an NFS server.
 
-## Centralized User management system (LDAP or AD)
+## Centralized user management system (LDAP or AD)
 In HPC environments, maintaining consistent user IDs (UIDs) and group IDs (GIDs) across the cluster is critical for seamless user access and resource management. A centralized user management system, such as LDAP or Active Directory (AD), ensures that UIDs and GIDs are synchronized across all compute nodes and storage systems.
 
 > [!Important]
 > 
-> For more information on how to setup and instructions, see the blog post about [Slurm Cloud Bursting Using CycleCloud on Azure](https://techcommunity.microsoft.com/blog/azurehighperformancecomputingblog/setting-up-slurm-cloud-bursting-using-cyclecloud-on-azure/4140922).
+> For more information on how to set up a centralized user management system, see the blog post about [Slurm Cloud Bursting Using CycleCloud on Azure](https://techcommunity.microsoft.com/blog/azurehighperformancecomputingblog/setting-up-slurm-cloud-bursting-using-cyclecloud-on-azure/4140922).
 
-### Next Steps
+### Next steps
 
 * [GitHub repo - cyclecloud-slurm](https://github.com/Azure/cyclecloud-slurm/tree/master)
 * [Azure CycleCloud Documentation](../../overview.md)