|
| 1 | +--- |
| 2 | +title: "Azure Operator Nexus: Runtime upgrade with PauseAfterRack strategy" |
| 3 | +description: Learn to execute a Cluster runtime upgrade for Operator Nexus with a PauseAfterRack strategy |
| 4 | +author: bartpinto |
| 5 | +ms.author: bpinto |
| 6 | +ms.service: azure-operator-nexus |
| 7 | +ms.topic: how-to |
| 8 | +ms.date: 02/25/2025 |
| 9 | +# ms.custom: template-include |
| 10 | +--- |
| 11 | + |
| 12 | +# Upgrading Cluster runtime with `PauseAfterRack` strategy |
| 13 | + |
| 14 | +Executing Cluster runtime upgrade with `PauseAfterRack` strategy will pause to wait for user confirmation before upgrading the next rack of worker nodes. The complete list of Cluster upgrade settings are discussed in [Upgrading Cluster runtime from Azure CLI](./howto-cluster-runtime-upgrade.md). |
| 15 | + |
| 16 | +## Prerequisites |
| 17 | + |
| 18 | +> [!NOTE] |
| 19 | +> Upgrade with the PauseAfterRack strategy is available starting API version 2024-07-01. |
| 20 | +
|
| 21 | +1. Install the latest version of the [appropriate CLI extensions](howto-install-cli-extensions.md). |
| 22 | +1. The latest `networkcloud` CLI extension is required. It can be installed following the steps listed [here](./howto-install-cli-extensions.md). |
| 23 | +1. Subscription access to run the Azure Operator Nexus network fabric (NF) and network cloud (NC) CLI extension commands. |
| 24 | +1. Collect the following information: |
| 25 | + - Subscription ID (`SUBSCRIPTION`) |
| 26 | + - Cluster name (`CLUSTER`) |
| 27 | + - Resource group (`CLUSTER_RG`) |
| 28 | +1. Target Cluster must be healthy in a running state, with all control plane nodes healthy. |
| 29 | + |
| 30 | +## Procedure |
| 31 | + |
| 32 | +1. Enable `PauseAfterRack` upgrade strategy on a Nexus Cluster |
| 33 | + |
| 34 | + ```azurecli |
| 35 | + az networkcloud cluster update --name "<CLUSTER>" \ |
| 36 | + --resource-group "<CLUSTER_RG>" \ |
| 37 | + --update-strategy strategy-type="PauseAfterRack" wait-time-minutes=0 \ |
| 38 | + --subscription "<SUBSCRIPTION>" |
| 39 | + ``` |
| 40 | + |
| 41 | +2. Confirm that the Cluster resource JSON in the JSON View reflects the `PauseAfterRack` upgrade strategy. |
| 42 | + |
| 43 | + ```azurecli |
| 44 | + az networkcloud cluster show --cluster-name "<CLUSTER>" \ |
| 45 | + --resource-group "<CLUSTER_RG>" \ |
| 46 | + --subscription "<SUBSCRIPTION>" | grep -A5 updateStrategy |
| 47 | +
|
| 48 | + "updateStrategy": { |
| 49 | + "maxUnavailable": 32767, |
| 50 | + "strategyType": "PauseAfterRack", |
| 51 | + "thresholdType": "PercentSuccess", |
| 52 | + "thresholdValue": 70, |
| 53 | + "waitTimeMinutes": 15, |
| 54 | + ``` |
| 55 | + |
| 56 | +3. Trigger runtime bundle upgrade as usual from Azure portal or CLI. See [Upgrading Cluster runtime from Azure CLI](./howto-cluster-runtime-upgrade.md). |
| 57 | + |
| 58 | +4. Once the control plane and management plane upgrades complete, the runtime upgrade is paused, awaiting user action to start the upgrade for Rack 1. |
| 59 | + |
| 60 | +:::image type="content" source="media/runtime-upgrade-cluster-paused.png" alt-text="Screenshot showing Paused Runtime Upgrade."::: |
| 61 | + |
| 62 | +> [!NOTE] |
| 63 | +> This message is available in logs for programmatic access. For more details, follow [List of logs available for streaming in Azure Operator Nexus](list-logs-available.md) |
| 64 | +
|
| 65 | +5. To resume the runtime upgrade, execute the following `az networkcloud` cli command. |
| 66 | + |
| 67 | + ```azurecli |
| 68 | + az networkcloud cluster continue-update-version --cluster-name "<CLUSTER>" \ |
| 69 | + --resource-group="<CLUSTER_RG>" \ |
| 70 | + --subscription="<SUBSCRIPTION>" |
| 71 | + ``` |
| 72 | + |
| 73 | +6. Repeat step 5 for each rack until all racks are upgraded to the latest runtime bundle. |
| 74 | + |
| 75 | +## Related content |
| 76 | + |
| 77 | +- [Upgrading Cluster runtime from Azure CLI](./howto-cluster-runtime-upgrade.md) |
0 commit comments