Update storageApplianceName to new tag, nexusSharedStorageApplianceName

Author: matternst7258

articles/operator-nexus/cluster-parameters-jsonc-example.md

@@ -61,7 +61,7 @@ ms.custom: template-how-to, devx-track-arm-template
               "username": "<COMPX_SVRY_BMC_USER>",
               "password": "<COMPX_SVRY_BMC_PASS>"
             },
-            "storageApplianceName": "<SA_NAME>",
+            "nexusSharedStorageApplianceName": "<SA_NAME>",
             "serialNumber": "<SA_SN>"
           }
         ],

articles/operator-nexus/concepts-storage-kubernetes.md

@@ -42,7 +42,7 @@ status:
   phase: Bound
 ```
 
-Some Azure Operator Nexus deployments may have two storage appliances installed. Persistent volume claims (PVCs) using the *nexus-volume* storage class can place the associated persistent volumes onto a specific storage appliance by using the *storageApplianceName* annotation. More information is available in [this document](./concepts-storage-multiple-appliances.md).
+Some Azure Operator Nexus deployments may have two storage appliances installed. Persistent volume claims (PVCs) using the *nexus-volume* storage class can place the associated persistent volumes onto a specific storage appliance by using the *nexusSharedStorageApplianceName* annotation. More information is available in [this document](./concepts-storage-multiple-appliances.md).
 
 ### StorageClass: nexus-shared
 

articles/operator-nexus/concepts-storage-multiple-appliances.md

@@ -49,7 +49,7 @@ The default storage appliance is the appliance in rack slot 1. You can set the d
 
 ### Nexus-volume storage class
 
-Azure Operator Nexus supports creating Persistent Volume Claims (PVCs) using the *nexus-volume* storage class. Nexus-volume PVCs are backed by a volume on the storage appliance which is created and managed by Azure Operator Nexus. You can select the storage appliance to provide the backing storage by using the `storageApplianceName` annotation.
+Azure Operator Nexus supports creating Persistent Volume Claims (PVCs) using the *nexus-volume* storage class. Nexus-volume PVCs are backed by a volume on the storage appliance which is created and managed by Azure Operator Nexus. You can select the storage appliance to provide the backing storage by using the `nexusSharedStorageApplianceName` annotation.
 
 ```yml
 apiVersion: v1
@@ -58,7 +58,7 @@ metadata:
   name: testPvc
   namespace: default
   annotations:
-    storageApplianceName: exampleStorageAppliance
+    nexusSharedStorageApplianceName: exampleStorageAppliance
 spec:
   accessModes:
   - ReadWriteOnce
@@ -76,11 +76,11 @@ status:
   phase: Bound
 ```
 
-`storageApplianceName` must match the Azure resource name of the storage appliance resource managed by your Azure Operator Nexus cluster on which you want to create the volume backing your PVC. If there's no `storageApplianceName` annotation, Azure Operator Nexus places the volume on the default storage appliance. If there is a `storageApplianceName` annotation, but it does not match the Azure resource name of a storage appliance managed by your Azure Operator Nexus cluster, the PVC creation will fail.
+`nexusSharedStorageApplianceName` must match the Azure resource name of the storage appliance resource managed by your Azure Operator Nexus cluster on which you want to create the volume backing your PVC. If there's no `nexusSharedStorageApplianceName` annotation, Azure Operator Nexus places the volume on the default storage appliance. If there is a `nexusSharedStorageApplianceName` annotation, but it does not match the Azure resource name of a storage appliance managed by your Azure Operator Nexus cluster, the PVC creation will fail.
 
 #### Nexus-volume limitations
 
-- Azure Operator Nexus doesn't support moving a PVC from one storage appliance to another. Attempts to change the `storageApplianceName` annotation have no effect.
+- Azure Operator Nexus doesn't support moving a PVC from one storage appliance to another. Attempts to change the `nexusSharedStorageApplianceName` annotation have no effect.
 - There's no support for placing volumes on a specific storage appliance when creating volumes through the Azure Resource Manager APIs. All volumes created directly through Azure Resource Manager will be placed on the storage appliance in rack slot 1.
 
 ### Nexus-shared storage class

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

@@ -71,7 +71,7 @@ az networkcloud cluster create --name "<CLUSTER_NAME>" --location "<LOCATION>" \
   --rack-serial-number "<AGGR_RACK_SN>" \
   --rack-location "<AGGR_RACK_LOCATION>" \
   --bare-metal-machine-configuration-data "["<AGGR_RACK_BMM>"]" \
-  --storage-appliance-configuration-data '[{"adminCredentials":{"password":"<SA1_PASS>","username":"<SA_USER>"},"rackSlot":1,"serialNumber":"<SA1_SN>","storageApplianceName":"<SA1_NAME>"}]' \
+  --storage-appliance-configuration-data '[{"adminCredentials":{"password":"<SA1_PASS>","username":"<SA_USER>"},"rackSlot":1,"serialNumber":"<SA1_SN>","nexusSharedStorageApplianceName":"<SA1_NAME>"}]' \
   --compute-rack-definitions '[{"networkRackId": "<COMPX_RACK_RESOURCE_ID>", "rackSkuId": "<COMPX_RACK_SKU>", "rackSerialNumber": "<COMPX_RACK_SN>", "rackLocation": "<COMPX_RACK_LOCATION>", "storageApplianceConfigurationData": [], "bareMetalMachineConfigurationData":[{"bmcCredentials": {"password":"<COMPX_SVRY_BMC_PASS>", "username":"<COMPX_SVRY_BMC_USER>"}, "bmcMacAddress":"<COMPX_SVRY_BMC_MAC>", "bootMacAddress":"<COMPX_SVRY_BOOT_MAC>", "machineDetails":"<COMPX_SVRY_SERVER_DETAILS>", "machineName":"<COMPX_SVRY_SERVER_NAME>"}]}]'\
   --managed-resource-group-configuration name="<MRG_NAME>" location="<MRG_LOCATION>" \
   --network fabric-id "<NF_ID>" \
@@ -98,7 +98,7 @@ az networkcloud cluster create --name "<CLUSTER_NAME>" --location "<LOCATION>" \
   --rack-serial-number "<AGGR_RACK_SN>" \
   --rack-location "<AGGR_RACK_LOCATION>" \
   --bare-metal-machine-configuration-data "["<AGGR_RACK_BMM>"]" \
-  --storage-appliance-configuration-data '[{"adminCredentials":{"password":"<SA1_PASS>","username":"<SA_USER>"},"rackSlot":1,"serialNumber":"<SA1_SN>","storageApplianceName":"<SA1_NAME>"},{"adminCredentials":{"password":"<SA2_PASS>","username":"<SA_USER>"},"rackSlot":2,"serialNumber":"<SA2_SN>","storageApplianceName":"<SA2_NAME>"}]' \
+  --storage-appliance-configuration-data '[{"adminCredentials":{"password":"<SA1_PASS>","username":"<SA_USER>"},"rackSlot":1,"serialNumber":"<SA1_SN>","nexusSharedStorageApplianceName":"<SA1_NAME>"},{"adminCredentials":{"password":"<SA2_PASS>","username":"<SA_USER>"},"rackSlot":2,"serialNumber":"<SA2_SN>","nexusSharedStorageApplianceName":"<SA2_NAME>"}]' \
   --compute-rack-definitions '[{"networkRackId": "<COMPX_RACK_RESOURCE_ID>", "rackSkuId": "<COMPX_RACK_SKU>", "rackSerialNumber": "<COMPX_RACK_SN>", "rackLocation": "<COMPX_RACK_LOCATION>", "storageApplianceConfigurationData": [], "bareMetalMachineConfigurationData":[{"bmcCredentials": {"password":"<COMPX_SVRY_BMC_PASS>", "username":"<COMPX_SVRY_BMC_USER>"}, "bmcMacAddress":"<COMPX_SVRY_BMC_MAC>", "bootMacAddress":"<COMPX_SVRY_BOOT_MAC>", "machineDetails":"<COMPX_SVRY_SERVER_DETAILS>", "machineName":"<COMPX_SVRY_SERVER_NAME>"}]}]'\
   --managed-resource-group-configuration name="<MRG_NAME>" location="<MRG_LOCATION>" \
   --network fabric-id "<NF_ID>" \

articles/operator-nexus/troubleshoot-multiple-storage-appliances.md

@@ -35,19 +35,19 @@ If any of the configurations was incorrect:
 
 ## Nexus-volume Persistent Volume Claim (PVC) on the wrong storage appliance
 
-PVCs using the nexus-volume storage class can select the storage appliance to use for backing storage using the `storageApplianceName` annotation. If this annotation isn't present, the PVC uses the first storage appliance. You can check this by using `kubectl get pvc <pvcName> -o yaml` and checking the `storageApplianceName` annotation. The value tells you which storage appliance the PVC is using.
+PVCs using the nexus-volume storage class can select the storage appliance to use for backing storage using the `nexusSharedStorageApplianceName` annotation. If this annotation isn't present, the PVC uses the first storage appliance. You can check this by using `kubectl get pvc <pvcName> -o yaml` and checking the `nexusSharedStorageApplianceName` annotation. The value tells you which storage appliance the PVC is using.
 
 If you wanted to create the PVC on the other storage appliance then you must delete and recreate the PVC, and then provide the correct annotation. There's no support for moving the volumes consumed by a PVC between storage appliances.
 
 ## Failure to create nexus-volume PVC
 
-A PVC fails to create if the `storageApplianceName` annotation is present but doesn't match the Azure Resource name of a storage appliance managed by the Nexus Cluster. You can check that the `storageApplianceName` annotation is correct by:
+A PVC fails to create if the `nexusSharedStorageApplianceName` annotation is present but doesn't match the Azure Resource name of a storage appliance managed by the Nexus Cluster. You can check that the `nexusSharedStorageApplianceName` annotation is correct by:
 
 1. Opening the Cluster (Operator Nexus) resource in the Azure portal
 1. Clicking on Rack definitions in the resource menu.
 1. Navigating to the aggregator rack and selecting Storage Appliance definitions.
 
-The `storageApplianceName` annotation must match one of the storage appliances in the Storage Appliance definitions list. You must delete the PVC and recreate it with the correct annotation to resolve this issue.
+The `nexusSharedStorageApplianceName` annotation must match one of the storage appliances in the Storage Appliance definitions list. You must delete the PVC and recreate it with the correct annotation to resolve this issue.
 
 ## Cloud Service Network (CSN) fails to create