Merge pull request #286895 from vnikolin/vnikolin-hwv3

HWV Updates for Release 3.13

Author: prmerger-automator[bot]

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

@@ -86,12 +86,12 @@ az networkcloud cluster create --name "$CLUSTER_NAME" --location "$LOCATION" \
 | COMPX_RACK_SKU            | Rack SKU for CompX Rack; repeat for each rack in compute-rack-definitions                                             |
 | COMPX_RACK_SN             | Rack Serial Number for CompX Rack; repeat for each rack in compute-rack-definitions                                   |
 | COMPX_RACK_LOCATION       | Rack physical location for CompX Rack; repeat for each rack in compute-rack-definitions                               |
-| COMPX_SVRY_BMC_PASS       | CompX Rack ServerY BMC password; repeat for each rack in compute-rack-definitions and for each server in rack         |
+| COMPX_SVRY_BMC_PASS       | CompX Rack ServerY Baseboard Management Controller (BMC) password; repeat for each rack in compute-rack-definitions and for each server in rack         |
 | COMPX_SVRY_BMC_USER       | CompX Rack ServerY BMC user; repeat for each rack in compute-rack-definitions and for each server in rack             |
 | COMPX_SVRY_BMC_MAC        | CompX Rack ServerY BMC MAC address; repeat for each rack in compute-rack-definitions and for each server in rack      |
-| COMPX_SVRY_BOOT_MAC       | CompX Rack ServerY boot NIC MAC address; repeat for each rack in compute-rack-definitions and for each server in rack |
+| COMPX_SVRY_BOOT_MAC       | CompX Rack ServerY boot Network Interface Card (NIC) MAC address; repeat for each rack in compute-rack-definitions and for each server in rack |
 | COMPX_SVRY_SERVER_DETAILS | CompX Rack ServerY details; repeat for each rack in compute-rack-definitions and for each server in rack              |
-| COMPX_SVRY_SERVER_NAME    | CompX Rack ServerY name, repeat for each rack in compute-rack-definitions and for each server in rack                 |
+| COMPX_SVRY_SERVER_NAME    | CompX Rack ServerY name; repeat for each rack in compute-rack-definitions and for each server in rack                 |
 | MRG_NAME                  | Cluster managed resource group name                                                                                   |
 | MRG_LOCATION              | Cluster Azure region                                                                                                  |
 | NF_ID                    | Reference to Network Fabric                                                                               |
@@ -101,8 +101,8 @@ az networkcloud cluster create --name "$CLUSTER_NAME" --location "$LOCATION" \
 | TENANT_ID                 | Subscription tenant ID                                                                                                |
 | SUBSCRIPTION_ID           | Subscription ID                                                                                                       |
 | KV_RESOURCE_ID            | Key Vault ID                                                                                                          |
-| CLUSTER_TYPE              | Type of cluster, Single, or MultiRack                                                                                  |
-| CLUSTER_VERSION           | NC Version of cluster                                                                                                 |
+| CLUSTER_TYPE              | Type of cluster, Single, or MultiRack                                                                                 |
+| CLUSTER_VERSION           | Network Cloud (NC) Version of cluster                                                                                 |
 | TAG_KEY1                  | Optional tag1 to pass to Cluster Create                                                                               |
 | TAG_VALUE1                | Optional tag1 value to pass to Cluster Create                                                                         |
 | TAG_KEY2                  | Optional tag2 to pass to Cluster Create                                                                               |
@@ -131,23 +131,23 @@ You can find examples for an 8-Rack 2M16C SKU cluster using these two files:
 >[!NOTE]
 >To get the correct formatting, copy the raw code file. The values within the cluster.parameters.jsonc file are customer specific and may not be a complete list. Update the value fields for your specific environment.
 
-1. In a web browser, go to the [Azure portal](https://portal.azure.com/) and sign in.
-1. From the Azure portal search bar, search for 'Deploy a custom template' and then select it from the available services.
+1. Navigate to [Azure portal](https://portal.azure.com/) in a web browser and sign in.
+1. Search for 'Deploy a custom template' in the Azure portal search bar, and then select it from the available services.
 1. Click on Build your own template in the editor.
 1. Click on Load file. Locate your cluster.jsonc template file and upload it.
 1. Click Save.
 1. Click Edit parameters.
 1. Click Load file. Locate your cluster.parameters.jsonc parameters file and upload it.
 1. Click Save.
 1. Select the correct Subscription.
-1. Search for the Resource group to see if it already exists.  If not, create a new Resource group.
+1. Search for the Resource group to see if it already exists. If not, create a new Resource group.
 1. Make sure all Instance Details are correct.
 1. Click Review + create.
 
 
 ### Cluster validation
 
-A successful Operator Nexus Cluster creation results in the creation of an AKS cluster
+A successful Operator Nexus Cluster creation results in the creation of an Azure Kubernetes Service (AKS) cluster
 inside your subscription. The cluster ID, cluster provisioning state, and
 deployment state are returned as a result of a successful `cluster create`.
 
@@ -170,16 +170,16 @@ Cluster create Logs can be viewed in the following locations:
 
 ## Deploy Cluster
 
-After creating the cluster, the deploy cluster action can be triggered.
+The deploy Cluster action can be triggered after creating the Cluster.
 The deploy Cluster action creates the bootstrap image and deploys the Cluster.
 
 Deploy Cluster initiates a sequence of events that occur in the Cluster Manager.
 
-1.  Validation of the cluster/rack properties
+1.  Validation of the cluster/rack properties.
 2.  Generation of a bootable image for the ephemeral bootstrap cluster
     (Validation of Infrastructure).
-3.  Interaction with the IPMI interface of the targeted bootstrap machine.
-4.  Perform hardware validation checks
+3.  Interaction with the Intelligent Platform Management Interface (IPMI) interface of the targeted bootstrap machine.
+4.  Performing hardware validation checks.
 5.  Monitoring of the Cluster deployment process.
 
 Deploy the on-premises Cluster:
@@ -198,7 +198,7 @@ az networkcloud cluster deploy \
 > See the section [Cluster Deploy Failed](#cluster-deploy-failed) for more detailed steps.
 > Optionally, the command can run asynchronously using the `--no-wait` flag.
 
-### Cluster Deploy with hardware validation
+### Cluster Deployment with hardware validation
 
 During a Cluster deploy process, one of the steps executed is hardware validation.
 The hardware validation procedure runs various test and checks against the machines
@@ -211,6 +211,9 @@ passed and/or are available to meet the thresholds necessary for deployment to c
 > Additionally, the provided Service Principal in the Cluster object is used for authentication against the Log Analytics Workspace Data Collection API.
 > This capability is only visible during a new deployment (Green Field); existing cluster will not have the logs available retroactively.
 
+> [!NOTE]
+> The RAID controller is reset during Cluster deployment wiping all data from the server's virtual disks. Any Baseboard Management Controller (BMC) virtual disk alerts can typically be ignored unless there are additional physical disk and/or RAID controllers alerts.
+
 By default, the hardware validation process writes the results to the configured Cluster `analyticsWorkspaceId`.
 However, due to the nature of Log Analytics Workspace data collection and schema evaluation, there can be ingestion delay that can take several minutes or more.
 For this reason, the Cluster deployment proceeds even if there was a failure to write the results to the Log Analytics Workspace.
@@ -219,9 +222,9 @@ To help address this possible event, the results, for redundancy, are also logge
 In the provided Cluster object's Log Analytics Workspace, a new custom table with the Cluster's name as prefix and the suffix `*_CL` should appear.
 In the _Logs_ section of the LAW resource, a query can be executed against the new `*_CL` Custom Log table.
 
-#### Cluster Deploy Action with skipping specific bare-metal-machine
+#### Cluster Deployment with skipping specific bare-metal-machine
 
-A parameter can be passed in to the deploy command that represents the names of
+The `--skip-validation-for-machines` parameter represents the names of
 bare metal machines in the cluster that should be skipped during hardware validation.
 Nodes skipped aren't validated and aren't added to the node pool.
 Additionally, nodes skipped don't count against the total used by threshold calculations.
@@ -279,7 +282,7 @@ az networkcloud cluster show --resource-group "$CLUSTER_RG" \
 ```
 
 The Cluster deployment is in-progress when detailedStatus is set to `Deploying` and detailedStatusMessage shows the progress of deployment.
-Some examples of deployment progress shown in detailedStatusMessage are `Hardware validation is in progress.` (if cluster is deployed with hardware validation) ,`Cluster is bootstrapping.`, `KCP initialization in progress.`, `Management plane deployment in progress.`, `Cluster extension deployment in progress.`, `waiting for "<rack-ids>" to be ready`, etc.
+Some examples of deployment progress shown in detailedStatusMessage are `Hardware validation is in progress.` (if cluster is deployed with hardware validation), `Cluster is bootstrapping.`, `KCP initialization in progress.`, `Management plane deployment in progress.`, `Cluster extension deployment in progress.`, `waiting for "<rack-ids>" to be ready`, etc.
 
 :::image type="content" source="./media/nexus-deploy-kcp-status.png" lightbox="./media/nexus-deploy-kcp-status.png" alt-text="Screenshot of Azure portal showing cluster deploy progress kcp init.":::
 
@@ -372,7 +375,7 @@ Note, `<APIVersion>` is the API version 2024-07-01 or newer.
 
 ## Delete a cluster
 
-When deleting a cluster, it deletes the resources in Azure and the cluster that resides in the on-premises environment.
+Deleting a cluster deletes the resources in Azure and the cluster that resides in the on-premises environment.
 
 >[!NOTE]
 >If there are any tenant resources that exist in the cluster, it will not be deleted until those resources are deleted.