Merge pull request #113234 from georgewallace/release-preview-vmware

v-shils · web-flow · commit 77a07dd8a354 · 2020-04-29T11:27:30.000-07:00
updates based on feedback
diff --git a/articles/azure-vmware/concepts-networking.md b/articles/azure-vmware/concepts-networking.md
@@ -9,7 +9,7 @@ ms.date: 05/04/2020
 
 Network interconnectivity between your Azure VMware Solution (AVS) private clouds and on-premises environments or virtual networks in Azure enables you to access and use your private cloud. A few key networking and interconnectivity concepts that establish the basis of interconnectivity are described in this article.
 
-A useful perspective on interconnectivity is to consider the two types of AVS private cloud implementations: Those implementations with basic Azure-only interconnectivity and those implementations with full on-premises to private cloud interconnectivity.
+A useful perspective on interconnectivity is to consider the two types of AVS private cloud implementations. The implementations with basic Azure-only interconnectivity and the implementations with full on-premises to private cloud interconnectivity.
 
 The use cases for AVS private clouds include:
 - new VMware VM workloads in the cloud
diff --git a/articles/azure-vmware/introduction.md b/articles/azure-vmware/introduction.md
@@ -9,17 +9,17 @@ ms.date: 05/04/2020
 
 Azure VMware Solution (AVS) provides you with private clouds in Azure. The private clouds contain vSphere clusters, built from dedicated bare-metal Azure infrastructure. You can scale private cloud clusters from 3 to 16 hosts, with the capability to have multiple clusters in a single private cloud. All private clouds are provisioned with vCenter Server, VSAN, vSphere, and NSX-T. You can migrate workloads from your on-premises environments, create or deploy new virtual machines, and consume Azure services from your private clouds.
 
-AVS is a VMware validated solution with on-going validation and testing of enhancements and upgrades. The private cloud infrastructure and software are managed and maintained through Azure, allowing you to focus on developing and running workloads in your private clouds.
+AVS is a VMware validated solution with on-going validation and testing of enhancements and upgrades. The private cloud infrastructure and software are managed and maintained by Microsoft, allowing you to focus on developing and running workloads in your private clouds.
 
 The following diagram shows the adjacency between private clouds and VNets in Azure, Azure services, and on-premises environments. Network access from private clouds to Azure services or VNets provides SLA-driven integration of Azure service endpoints. Private cloud access from on-premises environments uses ExpressRoute Global Reach for a private and secure connection.
 
 ![Image of AVS private cloud adjacency to Azure and on-premises](./media/adjacency-overview-drawing-final.png)
 
 ## Hosts, clusters, and private clouds
 
-AVS private clouds and clusters are built from two types of bare-metal, hyper-converged Azure infrastructure hosts. A general-purpose (GP) host configuration is available for evaluation clusters, and a high-end (HE) host configuration is available for any use case. The high-end hosts have 576-GB RAM and dual Intel 18 core, 2.3-GHz processors. The HE hosts have two vSAN diskgroups with a total 15.36 TB (SSD) raw vSAN capacity tier, and a 3.2 TB (NVMe) vSAN cache tier. General-purpose hosts have 192-GB RAM and dual Intel 10 core, 2.2-GHz processors. The GP hosts have a single vSAN diskgroup with a total 7.68 TB (SSD) raw vSAN capacity tier, and a 1.6 TB (NVMe) vSAN cache tier.
+AVS private clouds and clusters are built from one of two types of bare-metal, hyper-converged Azure infrastructure hosts. A general-purpose (GP) host configuration is available for evaluation clusters, and a high-end (HE) host configuration is available for any use case. The high-end hosts have 576-GB RAM and dual Intel 18 core, 2.3-GHz processors. The HE hosts have two vSAN diskgroups with a total 15.36 TB (SSD) raw vSAN capacity tier, and a 3.2 TB (NVMe) vSAN cache tier. General-purpose hosts have 192-GB RAM and dual Intel 10 core, 2.2-GHz processors. The GP hosts have a single vSAN diskgroup with a total 7.68 TB (SSD) raw vSAN capacity tier, and a 1.6 TB (NVMe) vSAN cache tier.
 
-New private clouds are deployed through the Azure portal. Other deployment options include the Azure CLI, PowerShell, or Azure Resource Manager templates.
+New private clouds are deployed through the Azure portal or Azure CLI.
 
 ## Networking
 
@@ -41,7 +41,7 @@ Regular upgrades of the AVS private cloud and VMware software ensures the latest
 
 ## Monitoring your private cloud
 
-You can use [Logs in Azure Monitor](../azure-monitor/overview.md) to collect logs on your virtual machines running in your AVS private cloud. You are able to [download and install the MMA agent](../azure-monitor/platform/log-analytics-agent.md#installation-and-configuration) on your AVS private cloud for both Linux and Windows virtual machines just like your other on-premises or Azure virtual machines. You can run the same queries you would normally run on your virtual machines just the same. To learn more about creating queries, see [how to write queries](../azure-monitor/log-query/log-query-overview.md#how-can-i-learn-how-to-write-queries).
+You can use [Logs in Azure Monitor](../azure-monitor/overview.md) to collect logs on your virtual machines running in your AVS private cloud. You can [download and install the MMA agent](../azure-monitor/platform/log-analytics-agent.md#installation-and-configuration) on Linux and Windows virtual machines running in your AVS private clouds, using the same queries that you run on your on-premises VMs. You can run the same queries you would normally run on your virtual machines just the same. To learn more about creating queries, see [how to write queries](../azure-monitor/log-query/log-query-overview.md#how-can-i-learn-how-to-write-queries).
 
 ## Next steps
 
diff --git a/articles/azure-vmware/tutorial-network-checklist.md b/articles/azure-vmware/tutorial-network-checklist.md
@@ -7,7 +7,7 @@ ms.date: 05/04/2020
 
 # Networking checklist for Azure VMware Solution (AVS)
 
-Azure VMware Solution offers a VMware private cloud environment, which is accessible for users and applications from on-premises environments and Azure resources. The connectivity is delivered through networking services such as Azure ExpressRoute and VPN connections. These networking services will require some specific network address ranges and firewall ports for enabling the services. This article provides you the information you need to know to properly configure your networking to work with AVS.
+Azure VMware Solution offers a VMware private cloud environment, which is accessible for users and applications from on-premises and Azure-based environments or resources. The connectivity is delivered through networking services such as Azure ExpressRoute and VPN connections and will require some specific network address ranges and firewall ports for enabling the services. This article provides you with the information you need to know to properly configure your networking to work with AVS.
 
 In this tutorial, you learn how about:
 
@@ -17,31 +17,22 @@ In this tutorial, you learn how about:
 
 ## Network connectivity
 
-The AVS private cloud can be connected to your Azure virtual network using Azure ExpressRoute. This high bandwidth, low latency connection allows you to
-access services running in your Azure subscription from your private cloud environment.
+The AVS private cloud is connected to your Azure virtual network using an Azure ExpressRoute connection. This high bandwidth, low latency connection allows you to access services running in your Azure subscription from your private cloud environment.
 
-`Example: 10.10.0.0/22`
+AVS private clouds require a minimum of a `/22` CIDR network address block for subnets, shown below. This network complements your on-premises networks. In order to connect to on-premises environments and virtual networks, this must be a non-overlapping network address block.
 
-This configuration will require a minimum of a `/22` CIDR block for the network dedicated to the private cloud environment. This network complements your on-premises networks. This configuration is broken down into several subnets upon deployment.
+Example `/22` CIDR network address block:  `10.10.0.0/22`
 
-The subnets will be:
-
-1. A gateway subnet (mandatory `/28`)  
-2. Private cloud vSphere and VSAN network (minimum `/24`)
-3. A virtual machine network.
+The subnets:
 
 | Network usage             | Subnet | Example        |
 | ------------------------- | ------ | -------------- |
-| Gateway Subnet            | `/28`    | `10.10.1.0/28`   |
-| VSphere/vSAN Subnet       | `/24`    | `10.10.0.0/24`   |
-| Virtual machine network 1 | `/24`   | `10.10.2.0/24`   |
-| Virtual machine network 2 | `/24`    | `10.10.3.0/24`   |
-| Virtual machine network 3 | `/25`    | `10.10.1.128/25` |
-
-### Network Ports required to communicate with the service
+| Private cloud management            | `/24`    | `10.10.0.0/24`   |
+| vMotion network       | `/24`    | `10.10.1.0/24`   |
+| VM workloads | `/24`   | `10.10.2.0/24`   |
+| ExpressRoute peering | `/24`    | `10.10.3.8/30`   |
 
-> [!NOTE]
-> The following list doesn't include any additional ports required for applications.
+### Network ports required to communicate with the service
 
 Source|Destination|Protocol |Port |Description  |Comment
 ---|-----|:-----:|:-----:|-----|-----
