Skip to content

Commit 470a156

Browse files
committed
more acrolinx check
1 parent 9a0dbf3 commit 470a156

File tree

3 files changed

+13
-13
lines changed

3 files changed

+13
-13
lines changed

articles/cyclecloud/how-to/ccws/plan-your-deployment.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ When doing a deployment, the Azure user account used need to be granted the foll
1818
- Optional: permission to register a Microsoft Entra application
1919

2020
> [!NOTE]
21-
> Recommendation is to predeploy a [Hub VNet](/azure/architecture/networking/architecture/hub-spoke) to connect to your enterprise network if one isn't already established. This hub can accommodate a [VPN Gateway](/azure/vpn-gateway/tutorial-create-gateway-portal) and an Azure Bastion. The CycleCloud Workspace for Slurm environment will be a spoke and peered during deployment.
21+
> Recommendation is to predeploy a [Hub virtual network](/azure/architecture/networking/architecture/hub-spoke) to connect to your enterprise network if one isn't already established. This hub can accommodate a [VPN Gateway](/azure/vpn-gateway/tutorial-create-gateway-portal) and an Azure Bastion. The CycleCloud Workspace for Slurm environment will be a spoke and peered during deployment.
2222
> Contact Azure HPC Support if VPN or Azure Bastion don't meet your requirements or are blocked by your organization
2323
2424
## Greenfield Deployment
@@ -35,19 +35,19 @@ In a greenfield deployment, the following resources and role assignments are cre
3535
- Optionally a NAT gateway named `ccw-nat-gateway` and public IP `pip-ccw-nat-gateway`.
3636
- Optionally an Azure NetApp Files account, pool, and volume with subnet `hpc-anf-subnet`.
3737
- Optionally an Azure Managed Lustre Filesystem with subnet `ccw-lustre-subnet`.
38-
- Optionally a VNET Peering.
38+
- Optionally a virtual network Peering.
3939
- Optionally a Private Endpoint to an existing Azure Database for MySQL flexible server instance.
4040

4141
## Brownfield Deployment
4242

4343
In a brownfield deployment, you can provide existing resources for:
44-
- The VNET and subnets in which the environment is deployed.
44+
- The virtual network and subnets in which the environment is deployed.
4545
- Filesystem Storage for the user's home directories and/or other filers, such as external NFS mount points or Azure Managed Lustre Filesystem (AMLS).
4646
- An Azure Database for MySQL flexible server instance for Slurm Job Accounting.
4747
- A registered Microsoft Entra ID application for Open OnDemand authentication.
4848
- A User-Assigned Managed Identity used by the registered Microsoft Entra ID application for the federated credentials.
4949

50-
If you're bringing your own VNET, follow these prerequisites:
50+
If you're bringing your own virtual network, follow these prerequisites:
5151
- A /29 **cyclecloud** subnet for the CycleCloud VM.
5252
- A **compute** subnet for the nodes, where the scheduler, login, and compute nodes are created.
5353
- When using Azure NetApp Files, a dedicated **netapp** subnet with the `Microsoft.NetApp/volumes` delegation as documented here [Azure NetApp Files](/azure/azure-netapp-files/azure-netapp-files-introduction).

articles/cyclecloud/qs-deploy-ccws.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -84,15 +84,15 @@ Specify here if you want to create a new Virtual Network and subnets or use an e
8484
- Select the CIDR that corresponds to the number of compute nodes you're targeting and specify a base IP address.
8585
- Creating a Bastion is recommended if direct connectivity isn't provided by your corporate IT.
8686
- Creating a NAT Gateway is required to provide outbound connectivity to internet.
87-
- Peer to an existing Virtual Network if you already have a HUB that can deliver services like Bastion and a VPN gateway. Ensure that you select a base IP address compatible with your peered VNET. If the peered VNET has a gateway, check the **Allow** gateway transit option.
87+
- Peer to an existing Virtual Network if you already have a HUB that can deliver services like Bastion and a VPN gateway. Ensure that you select a base IP address compatible with your peered virtual network. If the peered virtual network has a gateway, check the **Allow** gateway transit option.
8888

8989
#### Use existing Virtual Network
9090

9191
Before using an existing virtual network, check for the prerequisites in [Plan your CycleCloud Workspace for Slurm Deployment.](./how-to/ccws/plan-your-deployment.md#brownfield-deployment)
9292

9393
:::image type="content" source="./images/ccws/marketplace-networking-002.png" alt-text="Screenshot of the Networking options for using an existing one.":::
9494

95-
Please specify how to manage the registration of the private endpoint used for the storage account created to store CycleCloud projects with a private DNS zone. Options include creating a new private DNS zone, using an existing one, or not registering it.
95+
Specify how to manage the registration of the private endpoint used for the storage account created to store CycleCloud projects with a private DNS zone. Options include creating a new private DNS zone, using an existing one, or not registering it.
9696

9797
:::image type="content" source="./images/ccws/marketplace-networking-003.png" alt-text="Screenshot of the Networking options for Private DNS zone.":::
9898

@@ -120,18 +120,18 @@ You can postpone the start of the cluster if you need additional configuration t
120120

121121
To enable Slurm Job Accounting, check the box to display connectivity options. Ensure you have an Azure Database for MySQL flexible server resource that was deployed earlier.
122122

123-
You can connect using an FQDN or private IP if you supply your own virtual network or use VNET peering when creating a new virtual network as part of your deployment. Connection via private endpoint is also available if you choose to create a new virtual network.
123+
You can connect using an FQDN or private IP if you supply your own virtual network or use virtual network peering when creating a new virtual network as part of your deployment. Connection via private endpoint is also available if you choose to create a new virtual network.
124124

125125
:::image type="content" source="./images/ccws/marketplace-slurm-accounting-001.png" alt-text="Screenshot of the Slurm Setting options for job accounting database, direct FQDN.":::
126126

127127
:::image type="content" source="./images/ccws/marketplace-slurm-accounting-002.png" alt-text="Screenshot of the Slurm Setting options for job accounting database with Private Endpoint.":::
128128

129129
### Partition Settings
130130

131-
Azure CycleCloud Workspace for Slurm comes with 3 defined Slurm partitions:
132-
- HTC : For embarrassingly parallel non-MPI jobs.
133-
- HPC : For tightly coupled MPI jobs mostly using VM types with or without InfiniBand support.
134-
- GPU : For MPI and non-MPI GPU jobs using VM types with or without InfiniBand support.
131+
Azure CycleCloud Workspace for Slurm comes with three defined Slurm partitions:
132+
- HTC: For embarrassingly parallel non-MPI jobs.
133+
- HPC: For tightly coupled MPI jobs mostly using VM types with or without InfiniBand support.
134+
- GPU: For MPI and non-MPI GPU jobs using VM types with or without InfiniBand support.
135135

136136
You can configure the image and the maximum number of nodes for each partition that CycleCloud dynamically provisions. Only the HTC partition allows the use of spot instances, as spot instances aren't suitable for HPC and GPU jobs.
137137

articles/cyclecloud/release-notes/ccws/2024-09-18.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,12 +29,12 @@ Azure CycleCloud Workspace for Slurm is updated regularly. Stay up to date with
2929

3030
This release contains the following new features:
3131

32-
* Support to build a ready-to-go HPC/AI Slurm infrastructure.
32+
* Support to build a ready-to-go HPC/AI Slurm infrastructure.
3333
* Support to build or use an existing Azure NetApp Files NFS Volume for users home directories and more NFS mounts.
3434
* Support to build or use an existing Azure Managed Lustre Filesystem for another project storage.
3535
* Optionally create an Azure Bastion.
3636
* Optionally create NAT Gateway for outbound connections.
37-
* Optionally create a VNET Peering for enterprise connectivity.
37+
* Optionally create a virtual network Peering for enterprise connectivity.
3838
* Support connecting to an existing Azure Database for MySQL flexible server instance for Slurm job accounting.
3939
* Support AlmaLinux 8.7, Ubuntu 20.04, and Ubuntu 22.04 Azure HPC marketplace images for Scheduler, Login and, compute nodes.
4040
* Preset of HTC, HPC, and GPU Slurm Partitions with autoscaling enabled.

0 commit comments

Comments
 (0)