Skip to content

Commit 4fbaca1

Browse files
authored
Update howto-configure-cluster.md
1 parent 4726987 commit 4fbaca1

File tree

1 file changed

+31
-13
lines changed

1 file changed

+31
-13
lines changed

articles/operator-nexus/howto-configure-cluster.md

Lines changed: 31 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -154,8 +154,9 @@ deployment state are returned as a result of a successful `cluster create`.
154154
View the status of the Cluster:
155155

156156
```azurecli
157-
az networkcloud cluster show --resource-group "$CLUSTER_RG" \
158-
--cluster-name "$CLUSTER_RESOURCE_NAME"
157+
az networkcloud cluster show --cluster-name "<clusterName>" /
158+
--resource-group "<resourceGroupName>" /
159+
--subscription <SUBSCRIPTION_ID>
159160
```
160161

161162
The Cluster creation is complete when the `provisioningState` of the resource
@@ -187,13 +188,16 @@ If the customer requests a `compute-deployment-threshold` that it is different f
187188
The example below is for a customer requesting type "PercentSuccess" with a success rate of 97%.
188189

189190
```azurecli
190-
az networkcloud cluster update --name <CLUSTER_NAME> --resource-group <CLUSTER_RG> --compute-deployment-threshold type="PercentSuccess" grouping="PerCluster" value=97 --subscription <SUBSCRIPTION_ID>
191+
az networkcloud cluster update --name "<clusterName>" /
192+
--resource-group "<resourceGroup>" /
193+
--compute-deployment-threshold type="PercentSuccess" grouping="PerCluster" value=97 /
194+
--subscription <SUBSCRIPTION_ID>
191195
```
192196

193197
### Validate update:
194198

195199
```
196-
az networkcloud cluster show -g <CLUSTER_RG> -n <CLUSTER_NAME> | grep -a3 computeDeploymentThreshold
200+
az networkcloud cluster show --resource-group "<resourceGroup>" --name "<clusterName>" | grep -a3 computeDeploymentThreshold
197201
198202
"clusterType": "MultiRack",
199203
"clusterVersion": "<CLUSER_VERSION>",
@@ -211,7 +215,11 @@ In this example, if less than 97% of the compute nodes being deployed pass hardw
211215
If the customer requests an `update-strategy` threshold that it is different from the default of 80%, you can run the following cluster update command.
212216

213217
```azurecli
214-
az networkcloud cluster update -n <CLUSTER_NAME> -g <CLUSTER_RG> --update-strategy strategy-type="Rack" threshold-type="PercentSuccess" threshold-value=<DEPLOYMENT_THRESHOLD> wait-time-minutes=<DEPLOYMENT_PAUSE_MINS> --subscription <SUBSCRIPTION_ID>
218+
az networkcloud cluster update --name "<clusterName>" /
219+
--resource-group "<resourceGroup>" /
220+
--update-strategy strategy-type="Rack" threshold-type="PercentSuccess" /
221+
threshold-value="<thresholdValue>" wait-time-minutes=<waitTimeBetweenRacks> /
222+
--subscription <SUBSCRIPTION_ID>
215223
```
216224

217225
strategy-type can be "Rack" (Rack by Rack) OR "PauseAfterRack" (Wait for customer response to continue)
@@ -227,19 +235,23 @@ If updateStrategy is not set, the default are as follows:
227235
"waitTimeMinutes": 1
228236
```
229237

230-
231-
232238
The example below is for a customer using Rack by Rack strategy with a Percent Success of 60% and a 1 minute pause.
233239

234240
```azurecli
235-
az networkcloud cluster update -n <CLUSTER_NAME> -g <CLUSTER_RG> --update-strategy strategy-type="Rack" threshold-type="PercentSuccess" threshold-value=60 wait-time-minutes=1 --subscription <SUBSCRIPTION_ID>
241+
az networkcloud cluster update --name "<clusterName>" /
242+
--resource-group "<resourceGroup>" /
243+
--update-strategy strategy-type="Rack" threshold-type="PercentSuccess" /
244+
threshold-value=60 wait-time-minutes=1 /
245+
--subscription <SUBSCRIPTION_ID>
236246
```
237247

238-
239248
Verify update:
240249

241250
```
242-
az networkcloud cluster show -g <CLUSTER_RG> -n <CLUSTER_NAME> --subscription <SUBSCRIPTION_ID>| grep -a5 updateStrategy
251+
az networkcloud cluster show --resource-group "<resourceGroup>" /
252+
--name "<clusterName>" /
253+
--subscription <SUBSCRIPTION_ID>| grep -a5 updateStrategy
254+
243255
"strategyType": "Rack",
244256
"thresholdType": "PercentSuccess",
245257
"thresholdValue": 60,
@@ -251,14 +263,20 @@ In this example, if less than 60% of the compute nodes being provisioned in a ra
251263
The example below is for a customer using Rack by Rack strategy with a threshold type CountSuccess of 10 nodes per rack and a 1 minute pause.
252264

253265
```azurecli
254-
az networkcloud cluster update -n <CLUSTER_NAME> -g <CLUSTER_RG> --update-strategy strategy-type="Rack" threshold-type="CountSuccess" threshold-value=10 wait-time-minutes=1 --subscription <SUBSCRIPTION_ID>
266+
az networkcloud cluster update --name "<clusterName>" /
267+
--resource-group "<resourceGroup>" /
268+
--update-strategy strategy-type="Rack" threshold-type="CountSuccess" /
269+
threshold-value=10 wait-time-minutes=1 /
270+
--subscription <SUBSCRIPTION_ID>
255271
```
256272

257-
258273
Verify update:
259274

260275
```
261-
az networkcloud cluster show -g <CLUSTER_RG> -n <CLUSTER_NAME> --subscription <SUBSCRIPTION_ID>| grep -a5 updateStrategy
276+
az networkcloud cluster show --resource-group "<resourceGroup>" /
277+
--name "<clusterName>" /
278+
--subscription <SUBSCRIPTION_ID>| grep -a5 updateStrategy
279+
262280
"strategyType": "Rack",
263281
"thresholdType": "CountSuccess",
264282
"thresholdValue": 10,

0 commit comments

Comments
 (0)