Skip to content

Commit dbc0757

Browse files
authored
Update howto-nexus-instance-deployment-template.md
1 parent 7700243 commit dbc0757

File tree

1 file changed

+30
-22
lines changed

1 file changed

+30
-22
lines changed

articles/operator-nexus/howto-nexus-instance-deployment-template.md

Lines changed: 30 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -230,7 +230,7 @@ If any failures occur, report the <MISE_CID>, <CORRELATION_ID>, status code, and
230230
--parameters "clusterManager.parameters.jsonc" --debug --no-wait
231231
```
232232

233-
Follow these links for the structure of the ARM template and parameters files:
233+
Follow these links for the structure of the ARM template and parameters files for the CM:
234234
- [`clusterManager.jsonc`](clustermanager-jsonc-example.md)
235235
- [`clusterManager.parameters.jsonc`](clustermanager-parameters-jsonc-example.md)
236236

@@ -363,46 +363,48 @@ If any failures occur, report the <MISE_CID>, <CORRELATION_ID>, status code, and
363363
<summary> Detailed steps for deploying a Cluster </summary>
364364

365365
### Create Cluster
366-
1. Prework
366+
1. Create group if it doesn't exist from Azure CLI:
367367
```
368368
az group list --query "[?location=='<AZURE_REGION>'] | [?contains(name,'<CLUSTER_RG>')]" --subscription <CUSTOMER_SUB_ID> -o table
369-
370-
# If group does not exist, then create the group:
371369
az group create -l <AZURE_REGION> -n <CLUSTER_RG> --subscription <CUSTOMER_SUB_ID>
370+
```
372371

373-
# Check if Cluster exists
372+
2. Check if Cluster already exists from Azure CLI:
373+
```
374374
az networkcloud cluster list --subscription <CUSTOMER_SUB_ID> -o table
375375
```
376376

377-
2. Create Cluster from payload
377+
> [!IMPORTANT]
378+
> Do not continue if a Cluster already exists for <CLUSTER_NAME>.
379+
380+
3. Create Cluster from Telco Input template with ARM Deployment from Azure CLI:
378381
```
379-
cd <PAYLOAD_DIR>
380-
export PL_DIR=`pwd`
381-
source $PL_DIR/set_env.sh
382-
chmod +x cluster.sh
383-
./cluster.sh
382+
az deployment sub create --name "<CLUSTER_NAME>-deployment" --subscription <CUSTOMER_SUB_ID> --location <REGION> --template-file "cluster.jsonc" --parameters "cluster.parameters.jsonc" --debug --no-wait
384383
```
385-
386-
3. Update deployment threshold to customer requested value from default of 80%:
384+
Follow these links for the structure of the ARM template and parameters files for the Cluster:
385+
- [`cluster.jsonc`](cluster-jsonc-example.md)
386+
- [`cluster.parameters.jsonc`](cluster-parameters-jsonc-example.md)
387+
388+
4. Verify Cluster `Provisioning state` is `Succeeded` from Azure CLI:
389+
```
390+
az networkcloud cluster list --subscription <CUSTOMER_SUB_ID> -o table
391+
```
392+
393+
5. Update deployment threshold to custom value with Azure CLI (if desired threshold is different from default of 80%):
387394
```
388395
az networkcloud cluster update --name <CLUSTER_NAME> --resource-group <CLUSTER_RG> --subscription <CUSTOMER_SUB_ID> --compute-deployment-threshold type=<CLUSTER_DEPLOY_TYPE> grouping=<CLUSTER_DEPLOY_GROUPING> value=<CLUSTER_DEPLOY_THRESHOLD>
389396
390397
# Validate update:
391398
az networkcloud cluster show -g <CLUSTER_RG> -n <CLUSTER_NAME> --subscription <CUSTOMER_SUB_ID> | grep -a3 computeDeploymentThreshold
392399
393400
"clusterType": "MultiRack",
394-
"clusterVersion": "<CLUSER_VERSION>",
401+
"clusterVersion": "<CLUSTER_VERSION>",
395402
"computeDeploymentThreshold": {
396403
"grouping": "<CLUSTER_DEPLOY_GROUPING>",
397404
"type": "<CLUSTER_DEPLOY_TYPE>",
398405
"value": <CLUSTER_DEPLOY_THRESHOLD>
399406
```
400407

401-
4. Verify Cluster status:
402-
```
403-
az networkcloud cluster list -o table
404-
```
405-
406408
### Add resource tag on Cluster resource in Azure portal
407409
To increase visibility of the deployment, add a tag to the Cluster resource in Azure portal (optional):
408410
```
@@ -412,12 +414,11 @@ If any failures occur, report the <MISE_CID>, <CORRELATION_ID>, status code, and
412414
```
413415

414416
### Deploy Cluster
415-
The Cluster deployment can be initiated from Azure portal or Azure CLI.
416417

417-
To initiate deployment through Azure portal:
418+
To initiate Cluster deployment through Azure portal:
418419
Azure portal -> `Clusters (Operator Nexus)` -> `<CLUSTER_NAME>` -> `Deploy`
419420

420-
To initiate deployment through Azure CLI:
421+
To initiate Cluster deployment through Azure CLI:
421422
```
422423
az networkcloud cluster deploy --resource-group <CLUSTER_RG> --name <CLUSTER_NAME> --subscription <CUSTOMER_SUB_ID> --no-wait --debug
423424
```
@@ -539,5 +540,12 @@ CC: stakeholders_list
539540
- [ARM Template Editor](https://portal.azure.com/#create/Microsoft.Template)
540541
- [Azure CLI](https://aka.ms/azcli)
541542
- [Install CLI Extension](howto-install-cli-extensions.md)
543+
- [Troubleshoot hardware validation failure](troubleshoot-hardware-validation-failure.md)
544+
- [Troubleshoot BMM provisioning](troubleshoot-bare-metal-machine-provisioning.md)
545+
- [Troubleshoot BMM provisioning](troubleshoot-bare-metal-machine-provisioning.md)
546+
- [Troubleshoot BMM degraded](troubleshoot-bare-metal-machine-degraded.md)
547+
- [Troubleshoot BMM warning](troubleshoot-bare-metal-machine-warning.md)
548+
- [Telco Input Template](concepts-telco-input-template.md).
549+
- [Platform Prerequisites](howto-platform-prerequisites.md).
542550

543551
</details>

0 commit comments

Comments
 (0)