You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cyclecloud/qs-deploy-ccws.md
+36-31Lines changed: 36 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ For this quickstart, you need:
24
24
* In the `Search services and marketplace` box, enter **Slurm** and then select **Azure CycleCloud Workspace for Slurm**.
25
25
* On the **Azure CycleCloud Workspace for Slurm** page, select **Create**.
26
26
27
-
27
+
.
28
28
29
29
### Basics
30
30
* On the **New Azure CycleCloud Workspace for Slurm account** page, enter or select the following details.
@@ -35,53 +35,53 @@ For this quickstart, you need:
35
35
-**Admin User**: Enter a name and a password for the CycleCloud administrator account.
36
36
-**Admin SSH Public Key**: Select the public SSH key of the administrator account directly or if stored in an SSH key resource in Azure.
37
37
38
-
38
+
.
39
39
40
40
### File-system
41
41
#### Users' home directory - Create New
42
42
Specify where the users' home directory should be located. Create a new **Builtin NFS** uses the scheduler VM as an NFS server with an attached datadisk.
43
-
43
+
.
44
44
45
45
Create a new **Azure NetApp Files** creates an ANF account, pool and, volume of the specified capacity and service level.
46
-
46
+
.
47
47
48
48
#### Users' home directory - Use Existing
49
49
50
50
If you have an existing NFS mount point, then select the **Use Existing** option and specify the settings to mount it.
51
-
51
+
.
52
52
53
53
#### Supplemental file-system mount - Create New
54
54
55
55
If you need to mount another file-system for your project data, you can either create a new one or specify an existing one. You can create a new Azure NetApp Files volume or an Azure Managed Lustre Filesystem.
56
56
57
-
57
+
.
58
58
59
-
59
+
.
60
60
61
61
#### Supplemental file-system mount - Use Existing
62
62
63
63
If you have an existing external NFS mount point or an Azure Managed Lustre Filesystem, you can specify the mount options.
64
64
65
-
65
+
.
66
66
67
67
### Networking
68
68
69
69
Specify here if you want to create a new Virtual Network and subnets or use an existing one.
70
70
71
71
#### Create a new Virtual Network
72
72
73
-
73
+
.
74
74
75
75
- Select the CIDR that corresponds to the number of compute nodes you're targeting and specify a base IP address.
76
76
- Creating a Bastion is recommended if direct connectivity isn't provided by your corporate IT.
77
77
- Creating a NAT Gateway is required to provide outbound connectivity to internet.
78
-
- 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.
78
+
- 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.
79
79
80
80
#### Use existing Virtual Network
81
81
82
-
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)
82
+
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).
83
83
84
-
84
+
.
85
85
86
86
### Slurm Settings
87
87
@@ -100,13 +100,15 @@ You can also check the `Use image on all nodes` if you want the Scheduler, Login
100
100
101
101
Specify the number of login nodes you want to provision initially and the maximum number allowed. Enabling health checks automatically executes node health checks for the HPC and GPU partitions, removing any unhealthy nodes when they start.
102
102
103
-
103
+
.
104
104
105
-
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. 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. Furthermore, connection via Private Endpoint is available if you choose to create a new virtual network.
105
+
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.
106
106
107
-
107
+
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.
108
108
109
-
109
+
.
110
+
111
+
.
110
112
111
113
### Partition Settings
112
114
@@ -115,33 +117,36 @@ Azure CycleCloud Workspace for Slurm comes with 3 defined Slurm partitions:
115
117
- HPC : For tightly coupled MPI jobs mostly using VM types with InfiniBand support.
116
118
- GPU : For MPI and non-MPI GPU jobs.
117
119
118
-
You can configure the image and the maximum number of nodes for each partition that CycleCloud dynamically provisions. Only the HTC partition permits the use of spot instances, as it's generally not recommended to use spot instances for HPC and GPU jobs.
120
+
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.
119
121
120
-
122
+
.
121
123
122
124
### Tags
123
125
124
-
Assign the appropriate tags to the necessary resources. Node Array tags are applied to Virtual Machines that are dynamically provisioned by CycleCloud.
126
+
Assign the appropriate tags to the necessary resources. CycleCloud dynamically provisions Virtual Machines and applies Node Array tags to them.
127
+
128
+
.
125
129
126
-
127
130
131
+
### Review and create
128
132
129
-
### Review+Create
133
+
Review your options as this step also includes some validations.
130
134
131
-
Review your options. This step also process to some validations.
132
-
135
+
.
133
136
134
-
When passed, click on the **Create** button to initialize the deployment
135
-
137
+
After the validations are complete, click **Create** to initialize the deployment.
138
+
139
+
.
136
140
137
141
Follow the deployment status and steps.
138
142
139
143
## Check your deployment
140
144
141
145
Connect to the `ccw-cyclecloud-vm` using Bastion with the username and SSH keys specified during the deployment.
142
146
143
-
144
-
147
+
.
148
+
149
+
.
145
150
146
151
After connected, check the cloud-init logs to verify everything is correct.
147
152
@@ -174,10 +179,10 @@ Cloud-init v. 23.4-7.el8_10.alma.1 running 'modules:final' at Wed, 12 Jun 2024 1
174
179
Cloud-init v. 23.4-7.el8_10.alma.1 finished at Wed, 12 Jun 2024 10:28:15 +0000. Datasource DataSourceAzure [seed=/dev/sr0]. Up 754.29 seconds
175
180
```
176
181
177
-
Next, establish connectivity between your client machine and the CycleCloud VM. Its achieved through your corporate IT, a VPN, Bastion tunneling, or an attached public IP if permitted by your company. Access the web interface by browsing to https://<cyclecloud_ip>, and authenticate using the username and password provided during deployment. Verify that both the Scheduler and the Login node are running.
182
+
Next, establish connectivity between your client machine and the CycleCloud VM. It is achieved through your corporate IT, a VPN, Bastion tunneling, or an attached public IP if permitted by your company. Access the web interface by browsing to https://<cyclecloud_ip>, and authenticate using the username and password provided during deployment. Verify that both the Scheduler and the Login node are running.
178
183
179
184
## Resources
180
185
181
-
*[How to connect to the CycleCloud Portal through Bastion](/azure/cyclecloud/how-to/ccws/connect-to-portal-with-bastion)
182
-
*[How to connect to a Login Node through Bastion](/azure/cyclecloud/how-to/ccws/connect-to-login-node-with-bastion)
183
-
*[How to deploy a CycleCloud Workspace for Slurm environment using the CLI](/azure/cyclecloud/how-to/ccws/deploy-with-cli)
186
+
*[How to connect to the CycleCloud Portal through Bastion](/azure/cyclecloud/how-to/ccws/connect-to-portal-with-bastion).
187
+
*[How to connect to a Login Node through Bastion](/azure/cyclecloud/how-to/ccws/connect-to-login-node-with-bastion).
188
+
*[How to deploy a CycleCloud Workspace for Slurm environment using the CLI](/azure/cyclecloud/how-to/ccws/deploy-with-cli).
0 commit comments