Merge pull request #228703 from jaredr80/NexusUpdates-0227

Nexus updates 0227

Author: v-shils

articles/operator-nexus/howto-baremetal-functions.md

@@ -11,16 +11,12 @@ ms.custom: template-how-to
 
 # Manage lifecycle of Bare Metal Machines
 
-This article describes how to perform lifecycle management operations on Bare Metal Machines (BMM). The commands to manage the lifecycle of the BMM include:
+This article describes how to perform lifecycle management operations on Bare Metal Machines (BMM). These steps should be used for troubleshooting purposes to recover from failures or when taking maintenance actions. The commands to manage the lifecycle of the BMM include:
 
-- power-off
-- start the BMM
-- make the BMM unschedulable or schedulable
-- reinstall the BMM image
-
-When you want to reinstall or  update the image, or replace the BMM, make the BMM unschedulable.  In these cases, you need to evacuate existing workloads. You may have a need for no new workloads to be scheduled on a BMM, in which case make it unschedulable but without evacuating the workloads.
-
-Make your BMM schedulable for it to be used.
+- Power-off
+- Start the BMM
+- Make the BMM unschedulable or schedulable
+- Reinstall the BMM image
 
 ## Prerequisites
 
@@ -50,12 +46,12 @@ This command will `start` the specified `bareMetalMachineName`.
 ## Make a BMM unschedulable (cordon)
 
 You can make a BMM unschedulable by executing the [`cordon`](#make-a-bmm-unschedulable-cordon) command.
-On execution of the `cordon` command,
-Kubernetes won't schedule any new pods on the BMM; any attempt to create a pod on a `cordoned`
-BMM results in the pod being set to `pending` state. Existing pods continue to run.
+On the execution of the `cordon` command,
+Operator Nexus workloads are not scheduled on the BMM when cordon is set; any attempt to create a workload on a `cordoned`
+BMM results in the workload being set to `pending` state. Existing workloads continue to run.
 The cordon command supports an `evacuate` parameter with the default `false` value.
 On executing the `cordon` command, with the value `true` for the `evacuate`
-parameter, the pods currently running on the BMM will be `stopped` and the BMM will be set to `pending` state.
+parameter, the workloads that are running on the BMM are `stopped` and the BMM is set to `pending` state.
 
 ```azurecli
   az networkcloud baremetalmachine cordon \
@@ -64,12 +60,12 @@ parameter, the pods currently running on the BMM will be `stopped` and the BMM w
     --resource-group "resourceGroupName"
 ```
 
-The `evacuate "True"` removes pods from that node while `evacuate "FALSE"` only prevents the scheduling of new pods.
+The `evacuate "True"` removes workloads from that node while `evacuate "FALSE"` only prevents the scheduling of new workloads.
 
 ## Make a BMM schedulable (uncordon)
 
-You can make a BMM `schedulable` (usable) by executing the [`uncordon`](#make-a-bmm-schedulable-uncordon) command. All pods in `pending`
-state on the BMM will be `re-started` when the BMM is `uncordoned`.
+You can make a BMM `schedulable` (usable) by executing the [`uncordon`](#make-a-bmm-schedulable-uncordon) command. All workloads in a `pending`
+state on the BMM are `restarted` when the BMM is `uncordoned`.
 
 ```azurecli
   az networkcloud baremetalmachine uncordon \
@@ -79,7 +75,7 @@ state on the BMM will be `re-started` when the BMM is `uncordoned`.
 
 ## Reimage a BMM (reinstall a BMM image)
 
-The existing BMM image can be **reinstalled** using the `reimage` command but won't install a new image.
+The existing BMM image can be **reinstalled** using the `reimage` command but will not install a new image.
 Make sure the BMM's workloads are drained using the [`cordon`](#make-a-bmm-unschedulable-cordon)
 command, with `evacuate "TRUE"`, prior to executing the `reimage` command.
 

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

@@ -1,30 +1,29 @@
 ---
 title: How to guide for running commands for Cluster Manager on Azure Operator Nexus
 description: Learn to create, view, list, update, delete commands for Cluster Manager on Operator Nexus
-author: krishnaposa
-ms.author: sriposa
+author: jaredr80
+ms.author: jaredro
 ms.date: 01/23/2023
 ms.topic: how-to
 # ms.prod: used for on prem applications
 ms.service: azure 
 ---
 
-# Cluster manager: lifecycle management
+# Cluster Manager: How to manage the Cluster Manager in Operator Nexus
 
-You'll need to upgrade or patch a Cluster Manager. You may need to examine or change its properties. When all Operator Nexus  instances have been deleted from your sites, you may need to delete the Cluster Manager.
-In this how-to guide you'll learn to manage a Cluster Manager. The `networkcloud` resource provider supports `create`, `list` (also known as read), `show`, `update` and `delete` operations on the `clustermanager` resource.
+The Cluster Manager is deployed in the operator's Azure subscription to manage the lifecycle of Operator Nexus clusters. 
 
 ## Before you begin
 
 You'll need:
 
-- **Azure subscription ID** - The Azure subscription ID where Cluster Manager needs to be created (should be the same subscription ID of the Network fabric Controller) or exists.
-- **Fabric Controller ID** - Network fabric Controller and Cluster Manager have a 1:1 association. You'll need the resource ID of the Network fabric Controller associated with the Cluster Manager. Both the Cluster Manager and Fabric Controller need to be in your same Resource group.
-- **analytics workspace ID** - The resource ID of the Log Analytics workspace used for the logs collection.
-- **Azure Region** - The Cluster Manager should be created in the same region as the Network fabric Controller.
+- **Azure Subscription ID** - The Azure subscription ID where Cluster Manager needs to be created (should be the same subscription ID of the Network Fabric Controller).
+- **Fabric Controller ID** - Network Fabric Controller and Cluster Manager have a 1:1 association. You'll need the resource ID of the Network Fabric Controller associated with the Cluster Manager. Both the Cluster Manager and Fabric Controller need to be in the same resource group.
+- **Log Analytics Workspace ID** - The resource ID of the Log Analytics Workspace used for the logs collection.
+- **Azure Region** - The Cluster Manager should be created in the same region as the Network Fabric Controller.
 This Azure region should be used in the `Location` field of the Cluster Manager and all associated Operator Nexus instances.
 
-## Prerequisites: install CLI extensions
+## Prerequisites: Install CLI extensions
 
 Install latest version of the [appropriate CLI extensions](./howto-install-cli-extensions.md)
 
@@ -39,21 +38,21 @@ Some arguments that are available for every Azure CLI command
 - **--query** - uses the JMESPath query language to filter the output returned from Azure services.
 - **--verbose** - prints information about resources created in Azure during an operation, and other useful information
 
-## Cluster manager elements
+## Cluster Manager elements
 
 | Elements                          | Description                                                                                                                                                                                                                              |
 | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Name, ID, location, tags, type    | Name: User friendly name <br> ID: < Resource ID > <br> Location: Azure region where the Cluster Manager is created. Values from: `az account list -locations`.<br> Tags: Resource tags <br> Type: Microsoft.NetworkCloud/clusterManagers |
 | managerExtendedLocation           | The ExtendedLocation associated with the Cluster Manager                                                                                                                                                                                 |
 | managedResourceGroupConfiguration | Information about the Managed Resource Group                                                                                                                                                                                             |
-| fabricControllerId                | A reference to the fabric controller that is 1:1 with this Cluster Manager                                                                                                                                                               |
+| fabricControllerId                | A reference to the Network Fabric Controller that is 1:1 with this Cluster Manager                                                                                                                                                               |
 | analyticsWorkspaceId              | This workspace will be where any logs that 's relevant to the customer will be relayed.                                                                                                                                                  |
 | clusterVersions[]                 | List of ClusterAvailableVersions objects. <br> Cluster versions that the manager supports. Will be used as an input in the cluster clusterVersion property.                                                                              |
 | provisioningState                 | Succeeded, Failed, Canceled, Provisioning, Accepted, Updating                                                                                                                                                                            |
 | detailedStatus                    | Detailed statuses that provide additional information about the status of the Cluster Manager.                                                                                                                                           |
 | detailedStatusMessage             | Descriptive message about the current detailedStatus.                                                                                                                                                                                    |
 
-## Create a cluster manager
+## Create a Cluster Manager
 
 Use the `az network clustermanager create` command to create a Cluster Manager. This command creates a new Cluster Manager or updates the properties of the Cluster Manager if it exists. If you have multiple Azure subscriptions, select the appropriate subscription ID using the [az account set](/cli/azure/account#az-account-set) command.
 
@@ -69,13 +68,11 @@ az networkcloud clustermanager create \
     --subscription <subscription ID>
 ```
 
-The command returns 200 OK in the successful creation or update. 201 Created is returned when the operation is performed asynchronously.
-
 - **Arguments**
   - **--name -n [Required]** - The name of the Cluster Manager.
-  - **--fabric-controller-id [Required]** - The resource ID of the Network fabric Controller that is associated with the Cluster Manager.
+  - **--fabric-controller-id [Required]** - The resource ID of the Network Fabric Controller that is associated with the Cluster Manager.
   - **--resource-group -g [Required]** - Name of resource group. You can configure the default resource group using `az configure --defaults group=<name>`.
-  - **--analytics-workspace-id** - The resource ID of the Log Analytics workspace that is used for the logs collection
+  - **--analytics-workspace-id** - The resource ID of the Log Analytics Workspace that is used for the logs collection
   - **--location -l** - Location. Azure region where the Cluster Manager is created. Values from: `az account list -locations`. You can configure the default location using `az configure --defaults location=<location>`.
   - **--managed-resource-group-configuration** - The configuration of the managed resource group associated with the resource.
     - Usage: --managed-resource-group-configuration location=XX name=XX
@@ -87,27 +84,27 @@ The command returns 200 OK in the successful creation or update. 201 Created is
   - **--tags** - Space-separated tags: key[=value] [key[=value]...]. Use '' to clear existing tags
   - **--subscription** - Name or ID of subscription. You can configure the default subscription using `az account set -s NAME_OR_ID`.
 
-## List/show cluster manager(s)
+## List/show Cluster Manager(s)
 
 List and show commands are used to get a list of existing Cluster Managers or the properties of a specific Cluster Manager.
 
-### List cluster managers in resource group
+### List Cluster Managers in resource group
 
 This command lists the Cluster Managers in the specified Resource group.
 
 ```azurecli
 az networkcloud clustermanager list --resource-group <Azure Resource group>
 ```
 
-### List cluster managers in subscription
+### List Cluster Managers in subscription
 
 This command lists the Cluster Managers in the specified subscription.
 
 ```azurecli
 az networkcloud clustermanager list  --subscription <subscription ID>
 ```
 
-### Show cluster manager properties
+### Show Cluster Manager properties
 
 This command lists the properties of the specified Cluster Manager.
 
@@ -125,7 +122,7 @@ az networkcloud clustermanager show \
 - **--resource-group -g** - Name of resource group. You can configure the default group using `az configure --defaults group=<name>`.
 - **--subscription** - Name or ID of subscription. You can configure the default subscription using `az account set -s NAME_OR_ID`.
 
-## Update cluster manager
+## Update Cluster Manager
 
 This command is used to Patch properties of the provided Cluster Manager, or update the tags assigned to the Cluster Manager. Properties and tag updates can be done independently.
 
@@ -144,10 +141,10 @@ az networkcloud clustermanager update \
   - **--resource-group -g** - Name of resource group. You can configure the default group using `az configure --defaults group=<name>`.
   - **--subscription** - Name or ID of subscription. You can configure the default subscription using `az account set -s NAME_OR_ID`.
 
-## Delete cluster manager
+## Delete Cluster Manager
 
 This command is used to Delete the provided Cluster Manager.
-A Cluster Manager that has an existing associated Network fabric Controller, or any Clusters that reference this Cluster Manager may not be deleted
+A Cluster Manager that has an existing associated Network Fabric Controller, or any Clusters that reference this Cluster Manager may not be deleted
 
 ```azurecli
 az networkcloud clustermanager delete \