avere-vfxt: add review feedback

Author: ekpgh

articles/avere-vfxt/avere-vfxt-add-storage.md

@@ -4,7 +4,7 @@ description: How to add a back-end storage system to your Avere vFXT for Azure
 author: ekpgh
 ms.service: avere-vfxt
 ms.topic: conceptual
-ms.date: 12/14/2019
+ms.date: 01/13/2020
 ms.author: rohogue
 ---
 
@@ -27,7 +27,7 @@ These steps use the Avere Control Panel. Read [Access the vFXT cluster](avere-vf
 
 ## Create a core filer
 
-"Core filer" is a vFXT term for a backend storage system. The storage can be a hardware NAS appliance like NetApp or Isilon, or it can be a cloud object store. More information about core filers can be found in the [Avere cluster settings guide](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/settings_overview.html#managing-core-filers).
+"Core filer" is a vFXT term for a back-end storage system. The storage can be a hardware NAS appliance like NetApp or Isilon, or it can be a cloud object store. More information about core filers can be found in the [Avere cluster settings guide](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/settings_overview.html#managing-core-filers).
 
 To add a core filer, choose one of the two main types of core filers:
 
@@ -64,7 +64,7 @@ Next, proceed to [Create a junction](#create-a-junction).
 
 ### Azure Blob Storage cloud core filer
 
-To use Azure Blob storage as your vFXT cluster's backend storage, you need an empty container to add as a core filer.
+To use Azure Blob storage as your vFXT cluster's back-end storage, you need an empty container to add as a core filer.
 
 Adding Blob storage to your cluster requires these tasks:
 

articles/avere-vfxt/avere-vfxt-additional-resources.md

@@ -4,7 +4,7 @@ description: Links to additional information about Avere vFXT for Azure
 author: ekpgh
 ms.service: avere-vfxt
 ms.topic: conceptual
-ms.date: 12/19/2019
+ms.date: 01/13/2020
 ms.author: rohogue
 ---
 
@@ -20,7 +20,7 @@ Additional Avere cluster documentation can be found on the website at <https://a
   * [Customizing Support and Monitoring Settings](<https://azure.github.io/Avere/legacy/create_cluster/4_8/html/config_support.html#config-support>) explains how to customize support upload settings and enable remote monitoring.
   * [Configuring VServers and Global Namespace](<https://azure.github.io/Avere/legacy/create_cluster/4_8/html/config_vserver.html#config-vserver>) has information about creating a client-facing namespace.
   * [Configuring DNS for the Avere cluster](<https://azure.github.io/Avere/legacy/create_cluster/4_8/html/config_network.html#dns-overview>) explains how to configure round-robin DNS.
-  * [Adding Backend Storage](<https://azure.github.io/Avere/legacy/create_cluster/4_8/html/config_core_filer.html#add-core-filer>) documents how to add core filers.
+  * [Adding Back-end Storage](<https://azure.github.io/Avere/legacy/create_cluster/4_8/html/config_core_filer.html#add-core-filer>) documents how to add core filers.
 
 * The [Cluster Configuration Guide](<https://azure.github.io/Avere/#operations>) is a complete reference of settings and options for an Avere cluster. A vFXT cluster uses a subset of these options, but most of the same configuration pages apply.
 

articles/avere-vfxt/avere-vfxt-data-ingest.md

@@ -10,7 +10,7 @@ ms.author: rohogue
 
 # Moving data to the vFXT cluster - Parallel data ingest
 
-After you've created a new vFXT cluster, your first task might be to move data onto a new storage volume in Azure. However, if your usual method of moving data is issuing a simple copy command from one client, you will likely see a slow copy performance. Single-threaded copying is not a good option for copying data to the Avere vFXT cluster's backend storage.
+After you've created a new vFXT cluster, your first task might be to move data onto a new storage volume in Azure. However, if your usual method of moving data is issuing a simple copy command from one client, you will likely see a slow copy performance. Single-threaded copying is not a good option for copying data to the Avere vFXT cluster's back-end storage.
 
 Because the Avere vFXT for Azure cluster is a scalable multi-client cache, the fastest and most efficient way to copy data to it is with multiple clients. This technique parallelizes ingestion of the files and objects.
 
@@ -273,7 +273,7 @@ This method is a simple and time-effective method for datasets up to the number
 
 ## Use the msrsync utility
 
-The ``msrsync`` tool also can be used to move data to a backend core filer for the Avere cluster. This tool is designed to optimize bandwidth usage by running multiple parallel ``rsync`` processes. It is available from GitHub at <https://github.com/jbd/msrsync>.
+The ``msrsync`` tool also can be used to move data to a back-end core filer for the Avere cluster. This tool is designed to optimize bandwidth usage by running multiple parallel ``rsync`` processes. It is available from GitHub at <https://github.com/jbd/msrsync>.
 
 ``msrsync`` breaks up the source directory into separate “buckets” and then runs individual ``rsync`` processes on each bucket.
 
@@ -318,7 +318,7 @@ To use ``msrsync`` to populate an Azure cloud volume with an Avere cluster, foll
 
 ## Use the parallel copy script
 
-The ``parallelcp`` script also can be useful for moving data to your vFXT cluster's backend storage.
+The ``parallelcp`` script also can be useful for moving data to your vFXT cluster's back-end storage.
 
 The script below will add the executable `parallelcp`. (This script is designed for Ubuntu; if using another distribution, you must install ``parallel`` separately.)
 

articles/avere-vfxt/avere-vfxt-deploy-overview.md

@@ -4,7 +4,7 @@ description: Overview of deploying Avere vFXT for Azure
 author: ekpgh
 ms.service: avere-vfxt
 ms.topic: conceptual
-ms.date: 01/09/2020
+ms.date: 01/13/2020
 ms.author: rohogue
 ---
 <!-- filename is linked to in the marketplace template, make sure it gets a redirect if we rename it -->
@@ -36,21 +36,23 @@ Here is an overview of all of the steps.
    Cluster creation involves these steps, which are all done by the marketplace template:
 
    * Create new network infrastructure and resource groups, if needed
-   * Create a *cluster controller*  
+   * Create a cluster controller
 
      The cluster controller is a simple VM that resides in the same virtual network as the Avere vFXT cluster and has the custom software needed to create and manage the cluster. The controller creates the vFXT nodes and forms the cluster, and it also provides a command-line interface to manage the cluster during its lifetime.
 
-     If you create a new virtual network or subnet during the deployment, your controller will have a public IP address. This means the controller can serve as a jump host for connecting to the cluster from outside the subnet.
+     If you create a new virtual network or subnet during the deployment, your controller will have a public IP address. This means the controller can serve as a jump host for connecting to the cluster from outside the virtual network.
 
    * Create the cluster node VMs
 
-   * Configure the cluster node VMs to form the cluster
+   * Create the cluster from the individual nodes
 
    * Optionally, create a new Blob container and configure it as back-end storage for the cluster
 
+  Cluster creation is described in detail in [Deploy the vFXT cluster](avere-vft-deploy.md).
+
 1. Configure the cluster
 
-   Connect to the Avere vFXT configuration interface (Avere Control Panel) to customize the cluster's settings. Opt in for support monitoring, and add your storage system if you are using an on-premises data center.
+   Connect to the Avere vFXT configuration interface (Avere Control Panel) to customize the cluster's settings. Opt in for support monitoring, and add your storage system if you are using hardware storage or additional Blob containers.
 
    * [Access the vFXT cluster](avere-vfxt-cluster-gui.md)
    * [Enable support](avere-vfxt-enable-support.md)

articles/avere-vfxt/avere-vfxt-deploy-plan.md

@@ -4,7 +4,7 @@ description: Explains planning to do before deploying Avere vFXT for Azure
 author: ekpgh
 ms.service: avere-vfxt
 ms.topic: conceptual
-ms.date: 01/09/2020
+ms.date: 01/13/2020
 ms.author: rohogue
 ---
 
@@ -41,9 +41,9 @@ Consider where the elements of your Avere vFXT for Azure deployment will be. The
 
 ![Diagram showing the cluster controller and cluster VMs within one subnet. Around the subnet boundary is a vnet boundary. Inside the vnet is a hexagon representing the storage service endpoint; it is connected with a dashed arrow to a Blob storage outside the vnet.](media/avere-vfxt-components-option.png)
 
-Follow these guidelines when planning your Avere vFXT system's network infrastructure:
+Follow these guidelines when planning your Avere vFXT cluster's network infrastructure:
 
-* Create a new subscription for each Avere vFXT for Azure deployment and manage all components in this subscription.
+* Create a new subscription for each Avere vFXT for Azure deployment. Manage all components in this subscription.
 
   Benefits of using a new subscription for each deployment include:
   * Simpler cost tracking - View and audit all costs from resources, infrastructure, and compute cycles in one subscription.
@@ -56,7 +56,7 @@ Follow these guidelines when planning your Avere vFXT system's network infrastru
 
   * In the same virtual network
   * In the same resource group
-  * In the same storage account
+  * Using the same storage account
 
   The cluster creation template handles this configuration for most situations.
 
@@ -71,7 +71,7 @@ Follow these guidelines when planning your Avere vFXT system's network infrastru
   | Resource group | Yes, if empty | Must be empty|
   | Storage account | **Yes** if connecting an existing Blob container after cluster creation <br/>  **No** if creating a new Blob container during cluster creation | Existing Blob container must be empty <br/> &nbsp; |
   | Virtual network | Yes | Must include a storage service endpoint if creating a new Azure Blob container |
-  | Subnet | Yes |   |
+  | Subnet | Yes | Cannot contain other resources |
 
 ## IP address requirements
 
@@ -81,7 +81,7 @@ The Avere vFXT cluster uses the following IP addresses:
 
 * One cluster management IP address. This address can move from node to node in the cluster as needed so that it is always available. Use this address to connect to the Avere Control Panel configuration tool.
 * For each cluster node:
-  * At least one client-facing IP address. (All client-facing addresses are managed by the cluster's *vserver*, which can move them among nodes as needed.)
+  * At least one client-facing IP address. (All client-facing addresses are managed by the cluster's *vserver*, which can move the IP addresses among nodes as needed.)
   * One IP address for cluster communication
   * One instance IP address (assigned to the VM)
 
@@ -104,21 +104,19 @@ Each vFXT node will be identical. That is, if you create a three-node cluster yo
 
 Disk cache per node is configurable and can rage from 1000 GB to 8000 GB. 4 TB per node is the recommended cache size for Standard_E32s_v3 nodes.
 
-For additional information about these VMs, read the Microsoft Azure documentation:
-
-* [Memory optimized virtual machine sizes](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-memory)
+For additional information about these VMs, read the Microsoft Azure documentation: [Memory optimized virtual machine sizes](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-memory)
 
 ## Account quota
 
 Make sure that your subscription has the capacity to run the Avere vFXT cluster as well as any computing or client systems being used. Read [Quota for the vFXT cluster](avere-vfxt-prereqs.md#quota-for-the-vfxt-cluster) for details.
 
 ## Back-end data storage
 
-Back-end storage systems both supply files to the cluster's cache and also receive changed data from the cache. Decide whether your working set will be stored long term in a new Blob container or in an existing cloud or hardware storage system. These back-end storage systems are called *core filers*.
+Back-end storage systems both supply files to the cluster's cache and also receive changed data from the cache. Decide whether your working set will be stored long term in a new Blob container or in an existing storage system (cloud or hardware). These back-end storage systems are called *core filers*.
 
 ### Hardware core filers
 
-Add hardware storage systems to the vFXT cluster after you create the cluster. You can use any existing on-premises hardware system, including on-premises systems, as long as the storage system can be reached from the cluster's subnet.
+Add hardware storage systems to the vFXT cluster after you create the cluster. You can use a variety of popular hardware systems, including on-premises systems, as long as the storage system can be reached from the cluster's subnet.
 
 Read [Configure storage](avere-vfxt-add-storage.md) for detailed instructions about how to add an existing storage system to the Avere vFXT cluster.
 
@@ -144,7 +142,7 @@ Access options include:
   > [!TIP]
   > If you set a public IP address on the cluster controller, you can use it as the jump host. Read [Cluster controller as jump host](#cluster-controller-as-jump-host) for more information.
 
-* Virtual private network (VPN) - Configure a point-to-site or site-to-site VPN to your private network.
+* Virtual private network (VPN) - Configure a point-to-site or site-to-site VPN between your private network in Azure and corporate networks.
 
 * Azure ExpressRoute - Configure a private connection through an ExpressRoute partner.
 
@@ -158,20 +156,20 @@ To improve security for a controller with a public IP address, the deployment sc
 
 When creating the cluster, you can choose whether or not to create a public IP address on the cluster controller.
 
-* If you create a **new virtual network** or a **new subnet**, the cluster controller will be assigned a **public IP address**.
+* If you create a **new virtual network** or a **new subnet**, the cluster controller will be assigned a **public** IP address.
 * If you select an existing virtual network and subnet, the cluster controller will have only **private** IP addresses.
 
 ## VM access roles
 
 Azure uses [role-based access control](../role-based-access-control/index.yml) (RBAC) to authorize the cluster VMs to perform certain tasks. For example, the cluster controller needs authorization to create and configure the cluster node VMs. Cluster nodes need to be able to assign or reassign IP addresses to other cluster nodes.
 
-Two built-in Azure roles are used for the Avere vFXT for Azure virtual machines:
+Two built-in Azure roles are used for the Avere vFXT virtual machines:
 
 * The cluster controller uses the built-in role [Avere Contributor](../role-based-access-control/built-in-roles.md#avere-contributor).
-* Cluster nodes use the built-in role [Avere Operator](../role-based-access-control/built-in-roles.md#avere-operator)
+* Cluster nodes use the built-in role [Avere Operator](../role-based-access-control/built-in-roles.md#avere-operator).
 
 If you need to customize access roles for Avere vFXT components, you must define your own role and then assign it to the VMs at the time they are created. You cannot use the deployment template in the Azure Marketplace. Consult Microsoft Customer Service and Support by opening a ticket in the Azure portal as described in [Get help with your system](avere-vfxt-open-ticket.md).
 
 ## Next step: Understand the deployment process
 
-[Deployment overview](avere-vfxt-deploy-overview.md) gives the big picture view of the steps needed to create an Avere vFXT for Azure system and get it ready to serve data.
+[Deployment overview](avere-vfxt-deploy-overview.md) gives the big-picture view of the steps needed to create an Avere vFXT for Azure system and get it ready to serve data.

articles/avere-vfxt/avere-vfxt-deploy.md

@@ -4,7 +4,7 @@ description: Steps to deploy the Avere vFXT cluster in Azure
 author: ekpgh
 ms.service: avere-vfxt
 ms.topic: conceptual
-ms.date: 12/14/2019
+ms.date: 01/13/2020
 ms.author: rohogue
 ---
 
@@ -17,7 +17,7 @@ This procedure walks you through using the deployment wizard available from the
 * Creates the cluster node VMs and configures them as the Avere cluster.
 * If requested, creates a new Azure Blob container and configures it as a cluster core filer.
 
-After following the instructions in this document, you will have a virtual network, a subnet, a controller, and a vFXT cluster as shown in the following diagram. This diagram shows the optional Azure Blob core filer, which includes a new Blob storage container (in a new storage account, not shown) and a service endpoint for Microsoft storage inside the subnet.
+After following the instructions in this document, you will have a virtual network, a subnet, a cluster controller, and a vFXT cluster as shown in the following diagram. This diagram shows the optional Azure Blob core filer, which includes a new Blob storage container (in a new storage account, not shown) and a service endpoint for Microsoft storage inside the subnet.
 
 ![diagram showing three concentric rectangles with Avere cluster components. The outer rectangle is labeled 'Resource group' and contains a hexagon labeled 'Blob storage (optional)'. The next rectangle in is labeled 'Virtual network: 10.0.0.0/16' and does not contain any unique components. The innermost rectangle is labeled 'Subnet:10.0.0.0/24' and contains a VM labeled 'Cluster controller', a stack of three VMs labeled 'vFXT nodes (vFXT cluster)', and a hexagon labeled 'Service endpoint'. There is an arrow connecting the service endpoint (which is inside the subnet) and the blob storage (which is outside the subnet and vnet, in the resource group). The arrow passes through the subnet and virtual network boundaries.](media/avere-vfxt-deployment.png)
 
@@ -26,7 +26,7 @@ Before using the creation template, make sure you have addressed these prerequis
 1. [New subscription](avere-vfxt-prereqs.md#create-a-new-subscription)
 1. [Subscription owner permissions](avere-vfxt-prereqs.md#configure-subscription-owner-permissions)
 1. [Quota for the vFXT cluster](avere-vfxt-prereqs.md#quota-for-the-vfxt-cluster)
-1. [Storage service endpoint (if needed)](avere-vfxt-prereqs.md#create-a-storage-service-endpoint-in-your-virtual-network-if-needed) - Required for deploys using an existing virtual network and creating blob storage
+1. [Storage service endpoint (if needed)](avere-vfxt-prereqs.md#create-a-storage-service-endpoint-in-your-virtual-network-if-needed) - Required for deployments that use an existing virtual network and create blob storage
 
 For more information about cluster deployment steps and planning, read [Plan your Avere vFXT system](avere-vfxt-deploy-plan.md) and [Deployment overview](avere-vfxt-deploy-overview.md).
 
@@ -36,7 +36,7 @@ Access the creation template in the Azure portal by searching for Avere and sele
 
 ![Browser window showing the Azure portal with bread crumbs "New > Marketplace > Everything". In the Everything page, the search field has the term "avere" and the second result, "Avere vFXT for Azure ARM Template" is outlined in red to highlight it.](media/avere-vfxt-template-choose.png)
 
-After reading the details on the Avere vFXT for Azure ARM Template page, click **Create** to begin.
+After reading the details on the Avere vFXT for Azure ARM Template page, click its **Create** button to begin.
 
 ![Azure marketplace with the first page of the deployment template showing](media/avere-vfxt-deploy-first.png)
 

articles/avere-vfxt/avere-vfxt-manage-cluster.md

@@ -4,7 +4,7 @@ description: How to manage Avere cluster - add or remove nodes, reboot, stop, or
 author: ekpgh
 ms.service: avere-vfxt
 ms.topic: conceptual
-ms.date: 12/19/2019
+ms.date: 01/13/2020
 ms.author: rohogue
 ---
 
@@ -47,7 +47,7 @@ The Avere Control Panel can be used for these tasks:
 * Remove a node from the cluster
 * Stop or reboot the entire cluster
 
-Avere Control Panel prioritizes data integrity, so it attempts to write any changed data to backend storage before a possibly destructive operation. This makes it a safer option than the Azure portal.
+Avere Control Panel prioritizes data integrity, so it attempts to write any changed data to back-end storage before a possibly destructive operation. This makes it a safer option than the Azure portal.
 
 Access Avere Control Panel from a web browser. Follow the instructions in [Access the vFXT cluster](avere-vfxt-cluster-gui.md) if you need help.