Merge pull request #231860 from dramasamy/dramasamy-zone

Availability Zone and nodepool command addition

Author: Stacyrch140

articles/operator-nexus/howto-hybrid-aks.md

@@ -1,21 +1,21 @@
 ---
 title: "Azure Operator Nexus: Interact with AKS-Hybrid Cluster"
 description: Learn how to manage (view, list, update, delete) AKS-Hybrid clusters.
-author: pvapheas
-ms.author: pvapheas
+author: dramasamy
+ms.author: dramasamy
 ms.service: azure 
 ms.topic: how-to
 ms.date: 02/02/2023
 ms.custom: template-how-to
 ---
 
-# How to manage and lifecyle the AKS-Hybrid cluster
+# How to manage and lifecycle the AKS-Hybrid cluster
 
 This document shows how to manage an AKS-Hybrid cluster that you use for CNF workloads.
 
 ## Before you begin
 
-You'll need:
+You need:
 
 1. You should have created an [AKS-Hybrid Cluster](./quickstarts-tenant-workload-deployment.md#section-k-how-to-create-aks-hybrid-cluster-for-deploying-cnf-workloads)
 2. <`YourAKS-HybridClusterName`>: the name of your previously created AKS-Hybrid cluster
@@ -31,8 +31,8 @@ To get a list of AKS_Hybrid clusters in your Resource group:
 
 ```azurecli
     az hybridaks list -o table \
-    --resource-group "<YourResourceGroupName>" \
-    --subscription "<YourSubscription>"
+      --resource-group "<YourResourceGroupName>" \
+      --subscription "<YourSubscription>"
 ```
 
 ## Show command
@@ -41,8 +41,8 @@ To see the properties of AKS-Hybrid cluster named `YourAKS-HybridClustername`:
 
 ```azurecli
   az hybridaks show --name "<YourAKS-HybridClusterName>" \
-    --resource-group "< YourResourceGroupName >" \
-    --subscription "< YourSubscription >"
+    --resource-group "<YourResourceGroupName>" \
+    --subscription "<YourSubscription>"
 ```
 
 ## Update command
@@ -51,9 +51,9 @@ To update the properties of your AKS-Hybrid cluster:
 
 ```azurecli
     az hybridaks update --name "<YourAKS-HybridClustername>" \
-    --resource-group "<YourResourceGroupName>" \
-    --subscription "< YourSubscription>" \
-    --tags "<YourAKS-HybridClusterTags>"
+      --resource-group "<YourResourceGroupName>" \
+      --subscription "<YourSubscription>" \
+      --tags "<YourAKS-HybridClusterTags>"
 ```
 
 ## Delete command
@@ -62,6 +62,31 @@ To delete the AKS-Hybrid cluster named `YourAKS-HybridClustername`:
 
 ```azurecli
     az hybridaks delete --name "<YourAKS-HybridClustername>" \
-    --resource-group "<YourResourceGroupName >" \
-    --subscription "<YourSubscription>"
+      --resource-group "<YourResourceGroupName >" \
+      --subscription "<YourSubscription>"
+```
+
+## Add node pool command
+
+To add a node pool to the AKS-Hybrid cluster named `YourAKS-HybridClustername`:
+```azurecli
+    az hybridaks nodepool add \
+      --name <name of the nodepool> \
+      --cluster-name "<YourAKS-HybridClustername>" \
+      --resource-group "<YourResourceGroupName>" \
+      --location <dc-location> \
+      --node-count <worker node count> \
+      --node-vm-size <Operator Nexus SKU> \
+      --zones <comma separated list of availability zones>
+```
+
+## Delete node pool command
+
+To delete a node pool from the AKS-Hybrid cluster named `YourAKS-HybridClustername`:
+
+```azurecli
+    az hybridaks nodepool delete \
+      --name <name of the nodepool> \
+      --cluster-name "<YourAKS-HybridClustername>" \
+      --resource-group "<YourResourceGroupName>"
 ```

articles/operator-nexus/quickstarts-tenant-workload-deployment.md

@@ -1,7 +1,7 @@
 ---
 title: How to deploy tenant workloads
 description: Learn the steps for creating VMs for VNF workloads and for creating AKS-Hybrid clusters for CNF workloads
-author: dramasamymsft #Required; your GitHub user alias, with correct capitalization.
+author: dramasamy #Required; your GitHub user alias, with correct capitalization.
 ms.author: dramasamy #Required; microsoft alias of author; optional team alias.
 ms.service: azure #Required; service per approved list. slug assigned by ACOM.
 ms.topic: quickstart #Required; leave this attribute/value as-is.
@@ -42,7 +42,6 @@ You should have the following information already:
 - VLAN/subnet info for each of the layer 3 network(s)
 - Which network(s) would need to talk to each other (remember to put VLANs/subnets that needs to
   talk to each other into the same L3 Isolation Domain)
-- VLAN/subnet info for your `defaultcninetwork` for AKS-Hybrid cluster
 - BGP peering and network policies information for your L3 Isolation Domain(s)
 - VLANs for all your layer 2 network(s)
 - VLANs for all your trunked network(s)
@@ -148,7 +147,7 @@ Your VM requires at least one Cloud Services Network. You need the egress endpoi
 
 ### Step V3: create a VM
 
-Operator Nexus Virtual Machines (VMs) are used for hosting VNF(s) within a Telco network.
+Operator Nexus Virtual Machines (VMs) is used for hosting VNF(s) within a Telco network.
 The Nexus platform provides `az networkcloud virtualmachine create` to create a customized VM.
 For hosting a VNF on your VM, have it [Microsoft Azure Arc-enrolled](/azure/azure-arc/servers/overview),
 and provide a way to ssh to it via Azure CLI.
@@ -244,7 +243,7 @@ Gather this information:
 
 - The `resourceId` of the `cloudservicesnetwork`
 - The `resourceId(s)` for each of the L2/L3/Trunked Networks
-- Determine which network will serve as your default gateway (can only choose 1)
+- Determine which network serves as your default gateway (can only choose 1)
 - If you want to specify `networkAttachmentName` (interface name) for any of your networks
 - Determine the `ipAllocationMethod` for each of your L3 Network (static/dynamic)
 - The dimension of your VM
@@ -456,7 +455,7 @@ You need the egress endpoints you want to add to the proxy for your VM to access
 
 For each previously created tenant network, a corresponding AKS-Hybrid vNET network needs to be created
 
-You'll need the Azure Resource Manager resource ID for each of the networks you created earlier. You can retrieve the Azure Resource Manager resource IDs as follows:
+You need the Azure Resource Manager resource ID for each of the networks you created earlier. You can retrieve the Azure Resource Manager resource IDs as follows:
 
 ```azurecli
 az networkcloud cloudservicesnetwork show -g "<YourResourceGroupName>" -n "<YourCloudServicesNetworkName>" --subscription "<YourSubscription>" -o tsv --query id
@@ -498,7 +497,8 @@ This section describes how to create an AKS-Hybrid cluster
     --control-plane-count <count> \
     --location <dc-location> \
     --node-count <worker node count> \
-    --node-vm-size <Operator Nexus SKU>
+    --node-vm-size <Operator Nexus SKU> \
+    --zones <comma separated list of availability zones>
 ```
 
 After a few minutes, the command completes and returns JSON-formatted information about the cluster.

articles/operator-nexus/quickstarts-tenant-workload-prerequisites.md

@@ -1,8 +1,8 @@
 ---
 title: How to deploy tenant workloads prerequisites
 description: Learn the prerequisites for creating VMs for VNF workloads and for creating AKS-Hybrid clusters for CNF workloads
-author: jwheeler60 #Required; your GitHub user alias, with correct capitalization.
-ms.author: johnwheeler #Required; microsoft alias of author; optional team alias.
+author: dramasamy #Required; your GitHub user alias, with correct capitalization.
+ms.author: dramasamy #Required; microsoft alias of author; optional team alias.
 ms.service: azure #Required; service per approved list. slug assigned by ACOM.
 ms.topic: quickstart #Required; leave this attribute/value as-is.
 ms.date: 01/25/2023 #Required; mm/dd/yyyy format.
@@ -49,6 +49,20 @@ You need:
 - your Azure account and the subscription ID of Operator Nexus cluster deployment
 - the `custom location` resource ID of your Operator Nexus cluster
 
+## AKS-Hybrid availability zone
+`--zones` option in `az hybridaks create` or `az hybridaks nodepool add` can be used to distribute the AKS-Hybrid clusters across different zones for better fault tolerance and performance. When creating an AKS-Hybrid cluster, you can use the `--zones` option to schedule the cluster onto specific racks or distribute it evenly across multiple racks, improving resource utilization and fault tolerance.
+
+If you do not specify a zone when creating an AKS-Hybrid cluster through the `--zones` option, the Operator Nexus platform automatically implements a default anti-affinity rule. This anti-affinity rule aims to prevent scheduling the cluster VM on a node that already has a VM from the same cluster, but it's a best-effort approach and can't guarantee it.
+
+To obtain the list of available zones in the given Operator Nexus instance, you can use the following command.
+
+```azurecli
+    az networkcloud cluster show \
+      --resource-group <Operator Nexus on-prem cluster Resource Group> \
+      --name <Operator Nexus on-prem cluster name> \
+      --query computeRackDefinitions[*].availabilityZone
+```
+
 ### Review Azure container registry
 
 [Azure Container Registry](../container-registry/container-registry-intro.md) is a managed registry service to store and manage your container images and related artifacts.
@@ -133,4 +147,4 @@ This VM image build procedure is derived from [kubevirt](https://kubevirt.io/use
 To deploy your workloads, you need:
 
 - to create resource group or find a resource group to use for your workloads
-- the network fabric resource ID to create isolation-domains.
+- the network fabric resource ID to create isolation-domains.