Merge pull request #229597 from JAC0BSMITH/Nexus_Deploy_Restructure_0303

Syntax and other formatting for Concepts

Author: v-shils

articles/operator-nexus/concepts-observability.md

@@ -1,11 +1,11 @@
 ---
 title: "Azure Operator Nexus: observability using Azure Monitor"
-description: Operator Nexus uses Azure Monitor and collects and aggregates data in Azure Log Analytics workspace. The analysis, visualization, and alerting is performed on this collected data.
+description: Operator Nexus uses Azure Monitor and collects and aggregates data in Azure Log Analytics Workspace (LAW). The analysis, visualization, and alerting is performed on this collected data.
 author: mukesh-dua #Required; your GitHub user alias, with correct capitalization.
 ms.author: mukeshdua #Required; microsoft alias of author; optional team alias.
 ms.service: azure #Required
 ms.topic: conceptual #Required; leave this attribute/value as-is.
-ms.date: 01/31/2023 #Required; mm/dd/yyyy format.
+ms.date: 03/06/2023 #Required; mm/dd/yyyy format.
 ms.custom: template-concept #Required; leave this attribute/value as-is.
 ---
 
@@ -31,7 +31,7 @@ The key highlights of Operator Nexus observability framework are:
 This article helps you understand Operator Nexus observability framework that consists of a stack of components:
 
 - Azure Monitor collects and aggregates logging data from the Operator Nexus components
-- Azure Log Analytics workspace collects and aggregates logging data from multiple Azure subscriptions and tenants
+- Azure Log Analytics Workspace (LAW) collects and aggregates logging data from multiple Azure subscriptions and tenants
 - Analysis, visualization, and alerting are performed on the aggregated log data.
 
 ## Platform Monitoring
@@ -46,7 +46,7 @@ These logs and metrics are used to observe the state of the platform. You can se
 ### Monitoring Data
 
 Operator Nexus observability allows you to collect the same kind of data as other Azure
-resources. The data collected from each of your instances can be viewed in your LAW (Log Analytics workspace).
+resources. The data collected from each of your instances can be viewed in your LAW.
 
  You can learn about monitoring Azure resources [here](/azure/azure-monitor/essentials/monitor-azure-resource#monitoring-data).
 
@@ -60,8 +60,7 @@ The set of infrastructure components includes:
 * Undercloud Control Plane (Kubernetes cluster responsible for deployment and managing lifecycle of overall Platform).
 
 Collection of log data from these layers is enabled by default during the creation of your Operator Nexus
-instance. These collected logs are routed to your Azure Monitor Log
-Analytics Workspace.
+instance. These collected logs are routed to your Azure Monitor LAW.
 
 You can also collect data from the tenant layers
 created for running Containerized and Virtualized Network Functions. The log data that can be collected includes:
@@ -70,8 +69,7 @@ created for running Containerized and Virtualized Network Functions. The log dat
 * Collection of logs from AKS-Hybrid clusters and the applications deployed on top.
 
 You'll need to enable the collection of the logs from the tenant AKS-Hybrid clusters and Virtual Machines.
-You should follow the steps to deploy the [Azure monitoring agents](/azure/azure-monitor/agents/agents-overview#install-the-agent-and-configure-data-collection). The data would be collected in your Azure Log
-Analytics Workspace.
+You should follow the steps to deploy the [Azure monitoring agents](/azure/azure-monitor/agents/agents-overview#install-the-agent-and-configure-data-collection). The data would be collected in your Azure LAW.
 
 ### Operator Nexus Logs storage
 
@@ -111,17 +109,17 @@ See **[Getting Started with Azure Metrics Explorer](/azure/azure-monitor/essenti
 #### Workbooks
 
 Workbooks combine text, log queries, metrics, and parameters for data analysis and the creation of multiple kinds of rich visualizations.
-You can use the sample Azure Resource Manager workbook templates for [Operator Nexus Logging and Monitoring](https://github.com/microsoft/AzureMonitorCommunity/tree/master/Azure%20Services/Azure%20Operator%20Distributed%20Services) to deploy Azure Workbooks within your Azure Log Analytics Workspace.
+You can use the sample Azure Resource Manager workbook templates for [Operator Nexus Logging and Monitoring](https://github.com/microsoft/AzureMonitorCommunity/tree/master/Azure%20Services/Azure%20Operator%20Distributed%20Services) to deploy Azure Workbooks within your Azure LAW.
 
 #### Alerts
 
 You can use the sample Azure Resource Manager alarm templates for [Operator Nexus alerting rules](https://github.com/microsoft/AzureMonitorCommunity/tree/master/Azure%20Services/Azure%20Operator%20Distributed%20Services#alert-rules). You should specify thresholds and conditions for the alerts. You can then deploy these alert templates on your on-premises environment.
 
-## Log analytic workspace
+## Log Analytic Workspace
 
-A [Log Analytics workspace (LAW)](/azure/azure-monitor/logs/log-analytics-workspace-overview)
+A [LAW](/azure/azure-monitor/logs/log-analytics-workspace-overview)
 is a unique environment to log data from Azure Monitor and
 other Azure services. Each workspace has its own data repository and configuration but may
 combine data from multiple services. Each workspace consists of multiple data tables.
 
-A single Log Analytics workspace can be created to collect all relevant data or multiple workspaces based on operator requirements.
+A single LAW can be created to collect all relevant data or multiple workspaces based on operator requirements.

articles/operator-nexus/concepts-resource-types.md

@@ -5,7 +5,7 @@ author: jashobhit #Required; your GitHub user alias, with correct capitalization
 ms.author: shobhitjain #Required; microsoft alias of author; optional team alias.
 ms.service: azure
 ms.topic: conceptual #Required; leave this attribute/value as-is.
-ms.date: 01/25/2023 #Required; mm/dd/yyyy format.
+ms.date: 03/06/2023 #Required; mm/dd/yyyy format.
 ms.custom: template-concept #Required; leave this attribute/value as-is.
 ---
 
@@ -22,19 +22,19 @@ Figure: Resource model
 
 The Operator Nexus Cluster (or Instance) platform components include the infrastructure and the platform components used to manage these infrastructure resources.
 
-### Network Fabric controller
+### Network Fabric Controller
 
-The Network fabric Controller (NFC) is a resource that automates the life cycle management of all network devices deployed in an Operator Nexus instance.
+The Network Fabric Controller (NFC) is a resource that automates the life cycle management of all network devices deployed in an Operator Nexus instance.
 NFC is hosted in a [Microsoft Azure Virtual Network](/azure/virtual-network/virtual-networks-overview) in an Azure region.
 The region should be connected to your on-premises network via [Microsoft Azure ExpressRoute](/azure/expressroute/expressroute-introduction).
-An NFC can manage the network fabric of many (subject to limits) Operator Nexus instances.
+An NFC can manage the Network Fabric of many (subject to limits) Operator Nexus instances.
 
-### Network fabric
+### Network Fabric
 
-The Network fabric resource models a collection of network devices, compute servers, and storage appliances, and their interconnections. The network fabric resource also includes the networking required for your Network Functions and workloads. Each Operator Nexus instance has one Network fabric.
+The Network Fabric resource models a collection of network devices, compute servers, and storage appliances, and their interconnections. The Network Fabric resource also includes the networking required for your network functions and workloads. Each Operator Nexus instance has one Network Fabric.
 
-The Network fabric Controller (NFC) performs the lifecycle management of the network fabric.
-It configures and bootstraps the network fabric resources.
+The Network Fabric Controller (NFC) performs the lifecycle management of the Network Fabric.
+It configures and bootstraps the Network Fabric resources.
 
 ### Cluster manager
 
@@ -45,13 +45,13 @@ The CM and the NFC are hosted in the same Azure subscription.
 ### Cluster
 
 The Cluster (or Compute Cluster) resource models a collection of racks, bare metal machines, storage, and networking.
-Each cluster is mapped to the on-premises Network fabric. A cluster provides a holistic view of the deployed compute capacity.
+Each cluster is mapped to the on-premises Network Fabric. A cluster provides a holistic view of the deployed compute capacity.
 Cluster capacity examples include the number of vCPUs, the amount of memory, and the amount of storage space. A cluster is also the basic unit for compute and storage upgrades.
 
-### Network rack
+### Network Rack
 
-The Network rack consists of Consumer Edge (CE) routers, Top of Rack switches (ToRs), storage appliance, Network Packet Broker (NPB), and the Terminal Server.
-The rack also models the connectivity to the operator's Physical Edge switches (PEs) and the ToRs on the other racks.
+The Network Rack consists of Consumer Edge (CE) routers, Top of Rack switches (ToRs), storage appliance, Network Packet Broker (NPB), and the Terminal Server (TS).
+The Rack also models the connectivity to the operator's Physical Edge switches (PEs) and the ToRs on the other Racks.
 
 ### Rack
 
@@ -75,7 +75,7 @@ Workload components are resources that you use in hosting your workloads.
 The Network resources represent the virtual networking in support of your workloads hosted on  VMs or AKS-Hybrid clusters. 
 There are five Network resource types that represent a network attachment to an underlying isolation-domain. 
 
-- **Cloud Services Network Resource**: provides VMs/AKS-Hybrid clusters access to cloud services such as DNS, NTP, and user-specified Azure PaaS services. You must create at least one Cloud Services Network in each of your Operator Nexus instances. Each Cloud Service Network can be reused by many VMs and/or AKS-Hybrid clusters.
+- **Cloud Services Network Resource**: provides VMs/AKS-Hybrid clusters access to cloud services such as DNS, NTP, and user-specified Azure PaaS services. You must create at least one Cloud Services Network (CSN) in each of your Operator Nexus instances. Each CSN can be reused by many VMs and/or AKS-Hybrid clusters.
 
 - **Default CNI Network Resource**: supports configuring of the AKS-Hybrid cluster network resources.