Merge pull request #229442 from JAC0BSMITH/Nexus_Deploy_Restructure_0303

Restructure Platform Deployment Articles for Operator Nexus

Author: v-dirichards

articles/operator-nexus/.openpublishing.redirection.operator-nexus.json

@@ -10,6 +10,21 @@
             "source_path": "howto-monitoring-virtualized-network-functions-virtual-machines.md",
             "redirect_url": "howto-monitor-virtualized-network-functions-virtual-machines.md",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "quickstart-network-fabric-controller-cluster-manager-create.md",
+            "redirect_url": "howto-azure-operator-nexus-prerequisites.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "quickstarts-platform-deployment.md",
+            "redirect_url": "howto-configure-cluster.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "quickstarts-platform-prerequisites.md",
+            "redirect_url": "howto-platform-prerequisites.md",
+            "redirect_document_id": false
         }
     ]
 }

articles/operator-nexus/TOC.yml

@@ -12,27 +12,27 @@
     href: concepts-observability.md
 - name: Quickstarts
   items:
-  - name: Create Network fabric Controller and Cluster Manager
-    href: quickstart-network-fabric-controller-cluster-manager-create.md
-  - name: Before you start platform deployment
-    href: quickstarts-platform-prerequisites.md
-  - name: Platform deployment
-    href: quickstarts-platform-deployment.md
   - name: Before you start workload deployment
     href: quickstarts-tenant-workload-prerequisites.md
   - name: Tenant workload deployment
     href: quickstarts-tenant-workload-deployment.md
 - name: How-To Guides
   items:
-  - name: Network fabric Controller
+  - name: Before you start Operator Nexus NFC and CM deployment
+    href: howto-azure-operator-nexus-prerequisites.md
+  - name: Network Fabric Controller
     href: howto-configure-network-fabric-controller.md
   - name: Cluster Manager
     href: howto-cluster-manager.md
-  - name: Network fabric
+  - name: Before you start Operator Nexus platform deployment
+    href: howto-platform-prerequisites.md
+  - name: Network Fabric
     href: howto-configure-network-fabric.md
+  - name: Cluster
+    href: howto-configure-cluster.md
   - name: BareMetal Functions
     href: howto-baremetal-functions.md
-  - name: Isolation-domain
+  - name: Isolation Domain
     href: howto-configure-isolation-domain.md
   - name: AKS-Hybrid
     href: howto-hybrid-aks.md

articles/operator-nexus/howto-azure-operator-nexus-prerequisites.md

@@ -0,0 +1,85 @@
+---
+title: "Azure Operator Nexus: Before you start Network Fabric Controller and Cluster Manger creation"
+description: Prepare for create the Azure Operator Nexus Network Fabric Controller and Cluster Manger.
+author: JAC0BSMITH
+ms.author: jacobsmith
+ms.service: azure #Required; service per approved list. slug assigned by ACOM.
+ms.topic: how-to #Required; leave this attribute/value as-is.
+ms.date: 03/03/2023 #Required; mm/dd/yyyy format.
+ms.custom: template-how-to #Required; leave this attribute/value as-is.
+---
+
+# Operator Nexus Azure resources prerequisites
+
+To get started with Operator Nexus, you need to create a Network Fabric Controller (NFC) and then a Cluster Manager (CM)
+in your target Azure region.
+
+Each NFC is associated with a CM in the same Azure region and your subscription.
+The NFC/CM pair lifecycle manages up to 32 Azure Operator Nexus instances deployed in your sites connected to this Azure region.
+
+You'll need to complete the prerequisites before you can deploy the Operator Nexus first NFC and CM pair.
+In subsequent deployments of Operator Nexus, you can skip to creating the NFC and CM.
+
+## Resource Provider Registration
+
+- Ensure Azure Subscription for Operator Nexus resources has been permitted access to the
+  necessary Azure Resource Providers:
+  - Microsoft.NetworkCloud
+  - Microsoft.ManagedNetworkFabric
+  - Microsoft.HybridContainerService
+  - Microsoft.HybridNetwork
+  - Microsoft.Storage 
+  - Microsoft.Keyvault 
+  - Microsoft.Network 
+  - Microsoft.ExtendedLocation 
+  - Microsoft.HybridCompute 
+  - Microsoft.HybridConnectivity 
+  - Microsoft.HybridContainerService 
+  - Microsoft.Insights 
+  - Microsoft.Kubernetes 
+  - Microsoft.KubernetesConfiguration 
+  - Microsoft.OperationalInsights 
+  - Microsoft.OperationsManagement
+  - Microsoft.ResourceConnector 
+  - Microsoft.Resources
+
+## Dependant Azure resources setup
+- Establish [ExpressRoute](/azure/azure/expressroute/expressroute-introduction) connectivity
+  from your on-premises network to an Azure Region:
+  - ExpressRoute circuit [creation and verification](/azure/azure/expressroute/expressroute-howto-circuit-portal-resource-manager)
+    can be performed via the Azure portal
+  - In the ExpressRoute blade, ensure Circuit status indicates the status
+    of the circuit on the Microsoft side. Provider status indicates if
+    the circuit has been provisioned or not provisioned on the
+    service-provider side. For an ExpressRoute circuit to be operational,
+    Circuit status must be Enabled, and Provider status must be
+    Provisioned
+- Set up Azure Key Vault to store encryption and security tokens, service principals,
+  passwords, certificates, and API keys
+- Set up Log Analytics WorkSpace (LAW) to store logs and analytics data for
+  Operator Nexus subcomponents (Network Fabric, Cluster, etc.)
+- Set up Azure Storage account to store Operator Nexus data objects:
+  - Azure Storage supports blobs and files accessible from anywhere in the world over HTTP or HTTPS
+  - this storage isn't for user/consumer data.
+
+## Install CLI Extensions and sign-in to your Azure subscription
+
+Install latest version of the
+[necessary CLI extensions](./howto-install-cli-extensions.md).
+
+### Azure subscription sign-in
+
+```azurecli
+  az login
+  az account set --subscription $SUBSCRIPTION_ID
+  az account show
+```
+
+>[!NOTE]
+>The account must have permissions to read/write/publish in the subscription
+
+## Create steps
+
+- Step 1: [Create Network Fabric Controller](./howto-configure-network-fabric-controller.md)
+- Step 2: [Create Cluster Manager](./howto-cluster-manager.md)
+- 

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

@@ -11,61 +11,18 @@ ms.service: azure
 
 # Cluster Manager: How to manage the Cluster Manager in Operator Nexus
 
-The Cluster Manager is deployed in the operator's Azure subscription to manage the lifecycle of Operator Nexus clusters. 
+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).
-- **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.
+- **Network 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.
 - **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.
+- **Azure Region** - The Cluster Manager should be created in the same Azure 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
-
-Install latest version of the [appropriate CLI extensions](./howto-install-cli-extensions.md)
-
-### Sign in to your Azure account and select your subscription
-
-To begin your configuration, sign in to your Azure account. You can use the following examples to connect:
-
-```azurecli
-az login
-```
-
-Check the subscriptions for the account.
-
-```azurecli
-az account list
-```
-
-Select the subscription for which you want to create a Cluster Manager. This subscription will be used across all Operator Nexus resources.
-
-```azurecli
-az account set --subscription "<subscription ID>"
-```
-
-## Register providers for Network Cloud
-
-You can skip this step if your subscription is already registered with the Microsoft.NetworkCloud Resource Provider. Otherwise, proceed with the following steps:
-
-In Azure CLI, enter the following commands:
-
-```azurecli
-az provider register --namespace Microsoft.NetworkCloud
-```
-
-Monitor the registration process. Registration may take up to 10 minutes.
-
-```azurecli
-az provider show -n Microsoft.NetworkCloud -o table
-```
-
-Once registered, you should see the RegistrationState state for the namespace change to Registered.
-
-If you've already registered, you can verify using the `show` command.
 
 ## Global arguments
 
@@ -164,7 +121,7 @@ az networkcloud clustermanager show \
 
 ## 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.
+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.
 
 ```azurecli
 az networkcloud clustermanager update \