Used storageApplianceName instead of nexus...

Author: matternst7258

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

@@ -5,7 +5,7 @@ author: bartpinto
 ms.author: bpinto
 ms.service: azure-operator-nexus
 ms.topic: how-to
-ms.date: 03/31/2025
+ms.date: 05/22/2025
 ms.custom: template-how-to, devx-track-arm-template
 ---
 
@@ -61,7 +61,7 @@ ms.custom: template-how-to, devx-track-arm-template
               "username": "<COMPX_SVRY_BMC_USER>",
               "password": "<COMPX_SVRY_BMC_PASS>"
             },
-            "nexusSharedStorageApplianceName": "<SA_NAME>",
+            "storageApplianceName": "<SA_NAME>",
             "serialNumber": "<SA_SN>"
           }
         ],

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

@@ -5,7 +5,7 @@ author: pjw711
 ms.author: peterwhiting
 ms.service: azure-operator-nexus
 ms.topic: conceptual
-ms.date: 01/06/2025
+ms.date: 05/22/2025
 ms.custom: template-concept
 ---
 
@@ -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 *nexusSharedStorageApplianceName* 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 *storageApplianceName* annotation. More information is available in [this document](./concepts-storage-multiple-appliances.md).
 
 ### StorageClass: nexus-shared
 

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

@@ -5,7 +5,7 @@ author: pjw711
 ms.author: peterwhiting
 ms.service: azure-operator-nexus
 ms.topic: conceptual
-ms.date: 03/12/2025
+ms.date: 05/22/2025
 ms.custom: template-concept
 ---
 
@@ -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 `nexusSharedStorageApplianceName` 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 `storageApplianceName` annotation.
 
 ```yml
 apiVersion: v1
@@ -58,7 +58,7 @@ metadata:
   name: testPvc
   namespace: default
   annotations:
-    nexusSharedStorageApplianceName: exampleStorageAppliance
+    storageApplianceName: exampleStorageAppliance
 spec:
   accessModes:
   - ReadWriteOnce
@@ -76,11 +76,11 @@ status:
   phase: Bound
 ```
 
-`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.
+`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.
 
 #### Nexus-volume limitations
 
-- Azure Operator Nexus doesn't support moving a PVC from one storage appliance to another. Attempts to change the `nexusSharedStorageApplianceName` annotation have no effect.
+- Azure Operator Nexus doesn't support moving a PVC from one storage appliance to another. Attempts to change the `storageApplianceName` 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
@@ -89,11 +89,11 @@ Azure Operator Nexus provides a shared filesystem storage solution for container
 
 You can create the shared storage service on either storage appliance when the CSN is created. All nexus-shared PVCs using that shared storage service consume storage from the storage appliance backing the shared service. The configuration applies to all nexus-shared PVCs using the shared storage service provided by the CSN. All nexus-shared PVCs using the same shared storage service use the same storage appliance.
 
-The `nexusSharedStorageApplianceName` Azure resource tag controls which storage appliance is used to back the shared storage service. See [Prerequisites for deploying tenant workloads](./quickstarts-tenant-workload-prerequisites.md#create-a-cloud-services-network) for instructions on creating the shared storage service on a specific storage appliance.
+The `storageApplianceName` Azure resource tag controls which storage appliance is used to back the shared storage service. See [Prerequisites for deploying tenant workloads](./quickstarts-tenant-workload-prerequisites.md#create-a-cloud-services-network) for instructions on creating the shared storage service on a specific storage appliance.
 
 If no storage appliance configuration is provided at CSN creation time, the shared storage service uses the first storage appliance. If the configuration is present but doesn't match a storage appliance then the CSN creation will fail.
 
-Subsequent updates to the `nexusSharedStorageApplianceName` Azure resource tag have no effect. There is no support for moving the shared filesystem storage solution between storage appliances after initial deployment.
+Subsequent updates to the `storageApplianceName` Azure resource tag have no effect. There is no support for moving the shared filesystem storage solution between storage appliances after initial deployment.
 
 #### Nexus-shared limitations
 

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

@@ -5,7 +5,7 @@ author: bartpinto
 ms.author: bpinto
 ms.service: azure-operator-nexus
 ms.topic: how-to
-ms.date: 03/31/2025
+ms.date: 05/22/2025
 ms.custom: template-how-to, devx-track-azurecli
 ---
 
@@ -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>","nexusSharedStorageApplianceName":"<SA1_NAME>"}]' \
+  --storage-appliance-configuration-data '[{"adminCredentials":{"password":"<SA1_PASS>","username":"<SA_USER>"},"rackSlot":1,"serialNumber":"<SA1_SN>","storageApplianceName":"<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>","nexusSharedStorageApplianceName":"<SA1_NAME>"},{"adminCredentials":{"password":"<SA2_PASS>","username":"<SA_USER>"},"rackSlot":2,"serialNumber":"<SA2_SN>","nexusSharedStorageApplianceName":"<SA2_NAME>"}]' \
+  --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>"}]' \
   --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/quickstarts-tenant-workload-prerequisites.md

@@ -5,7 +5,7 @@ author: dramasamy
 ms.author: dramasamy
 ms.service: azure-operator-nexus
 ms.topic: how-to
-ms.date: 01/25/2023
+ms.date: 05/22/2023
 ms.custom: template-how-to-pattern, devx-track-azurecli, devx-track-azurepowershell
 ---
 
@@ -185,7 +185,7 @@ Deployments with multiple storage appliances support selecting the storage appli
     --extended-location name="<ClusterCustomLocationId >" type="CustomLocation" \
     --location "<ClusterAzureRegion>" \
     --additional-egress-endpoints "[{\"category\":\"<YourCategory >\",\"endpoints\":[{\"<domainName1 >\":\"< endpoint1 >\",\"port\":<portnumber1 >}]}]"
-    --tags "nexusSharedStorageApplianceName": "<YourStorageApplianceName>""
+    --tags "storageApplianceName": "<YourStorageApplianceName>""
 ```
 
 ### [Azure PowerShell](#tab/azure-powershell)
@@ -201,7 +201,7 @@ $additionalEgressEndpoint = New-AzNetworkCloudEgressEndpointObject `
   -Category "YourCategory" `
   -Endpoint $endpointList
 $endpointEgressList+= $additionalEgressEndpoint
-$tags @{"nexusSharedStorageApplianceName"="<YourStorageApplianceName>"}
+$tags @{"storageApplianceName"="<YourStorageApplianceName>"}
 
 New-AzNetworkCloudServicesNetwork -CloudServicesNetworkName "<YourCloudServicesNetworkName>" `
 -ResourceGroupName "<YourResourceGroupName>" `

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

@@ -4,7 +4,7 @@ description: Troubleshooting common issues with multiple Storage Appliances
 ms.service: azure-operator-nexus
 ms.custom: troubleshooting
 ms.topic: troubleshooting
-ms.date: 08/12/2024
+ms.date: 05/22/2024
 ms.author: peterwhiting
 author: pjw711
 ---
@@ -35,26 +35,26 @@ 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 `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.
+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.
 
 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 `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:
+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:
 
 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 `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.
+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.
 
 ## Cloud Service Network (CSN) fails to create
 
-A CSN fails to create if the `nexusSharedStorageApplianceName` Azure resource tag 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` Azure resource tag is correct by:
+A CSN fails to create if the `storageApplianceName` Azure resource tag 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` Azure resource tag 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 `nexusSharedStorageApplianceName` Azure resource tag must match one of the storage appliances in the Storage Appliance definitions list. You must delete the CSN and recreate it with the correct Azure Resource tag to resolve this issue.
+The `storageApplianceName` Azure resource tag must match one of the storage appliances in the Storage Appliance definitions list. You must delete the CSN and recreate it with the correct Azure Resource tag to resolve this issue.