avere-vfxt: rework prereqs, new screenshots

Author: ekpgh

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

@@ -4,9 +4,10 @@ description: Overview of deploying Avere vFXT for Azure
 author: ekpgh
 ms.service: avere-vfxt
 ms.topic: conceptual
-ms.date: 12/20/2019
+ms.date: 01/09/2020
 ms.author: rohogue
 ---
+<!-- filename is linked to in the marketplace template, make sure it gets a redirect if we rename it -->
 
 # Avere vFXT for Azure - deployment overview
 
@@ -20,7 +21,7 @@ After [planning your system](avere-vfxt-deploy-plan.md), you can begin to create
 
 An Azure Resource Manager template in the Azure Marketplace collects the necessary information and automatically deploys the entire cluster.
 
-After the vFXT cluster is up and running, you will want to know how to connect clients to it and (optionally) how to move your data to the new Blob storage container. If you use a NAS storage system, you need to add it after the cluster is created.
+After the vFXT cluster is up and running, there are still some configuration steps to take before using it. If you created a new Blob storage container, you'll want to move your data to it. If you use a NAS storage system, you need to add it after the cluster is created. You will want to connect clients to the cluster.
 
 Here is an overview of all of the steps.
 
@@ -62,7 +63,7 @@ Here is an overview of all of the steps.
 1. Add data (if needed)
 
    Because the Avere vFXT is a scalable multi-client cache, the best way to move data to a new back-end storage container is with a multi-client, multi-threaded file copy strategy.
-   
+
    If you need to move working set data to a new Blob container or other back-end storage system, follow the instructions in [Moving data to the vFXT cluster](avere-vfxt-data-ingest.md).
 
 ## Next steps

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

@@ -12,7 +12,12 @@ ms.author: rohogue
 
 This article explains how to plan a new Avere vFXT for Azure cluster that is positioned and sized appropriately for your needs.
 
-Before going to the Azure Marketplace or creating any VMs, consider how the cluster will interact with other elements in Azure. Plan where cluster resources will be located in your private network and subnets, and decide where your back-end storage will be. Make sure that the cluster nodes you create are powerful enough to support your workflow.
+Before going to the Azure Marketplace or creating any VMs, consider these details:
+
+* How will the cluster interact with other Azure resources?
+* Where should cluster elements be located in private networks and subnets?
+* What type of back-end storage will you use, and how will the cluster access it?
+* How powerful do your cluster nodes need to be to support your workflow?
 
 Read on to learn more.
 
@@ -38,10 +43,12 @@ Consider where the elements of your Avere vFXT for Azure deployment will be. The
 
 Follow these guidelines when planning your Avere vFXT system's network infrastructure:
 
-* Create a new subscription for each Avere vFXT for Azure deployment and manage all components in this subscription. Benefits include:
+* Create a new subscription for each Avere vFXT for Azure deployment and 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.
   * Easier cleanup - You can remove the entire subscription when finished with the project.
-  * Convenient partitioning of resource quotas - Protect other critical workloads from possible resource throttling by isolating the Avere vFXT clients and cluster in a single subscription. This avoids conflict when bringing up a large number of clients for a high-performance computing workflow.
+  * Convenient partitioning of resource quotas - Isolate the Avere vFXT clients and cluster in a single subscription to protect other critical workloads from possible resource throttling. This separation prevents conflict when bringing up a large number of clients for a high-performance computing workflow.
 
 * Locate your client compute systems close to the vFXT cluster. Back-end storage can be more remote.  
 
@@ -51,7 +58,7 @@ Follow these guidelines when planning your Avere vFXT system's network infrastru
   * In the same resource group
   * In the same storage account
 
-  The automated cluster creation template handles this for most situations.
+  The cluster creation template handles this configuration for most situations.
 
 * The cluster must be located in its own subnet to avoid IP address conflicts with clients or other compute resources.
 

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

@@ -144,11 +144,11 @@ To find the information:
 
 1. On left side, click **Deployments**, and then **microsoft-avere.vfxt-template**.
 
-   ![Resource group portal page with Deployments selected on the left and microsoft-avere.vfxt-template showing in a table under Deployment name](media/avere-vfxt-outputs-deployments.png) <!-- update image for new portal GUI -->
+   ![Resource group portal page with Deployments selected on the left and microsoft-avere.vfxt-template showing in a table under Deployment name](media/avere-vfxt-outputs-deployments.png)
 
 1. On left side, click **Outputs**. Copy the values in each of the fields.
 
-   ![outputs page showing SSHSTRING, RESOURCE_GROUP, LOCATION, NETWORK_RESOURCE_GROUP, NETWORK, SUBNET, SUBNET_ID, VSERVER_IPs, and MGMT_IP values in fields to the right of the labels](media/avere-vfxt-outputs-values.png)<!-- update image for new portal GUI -->
+   ![outputs page showing SSHSTRING, RESOURCE_GROUP, LOCATION, NETWORK_RESOURCE_GROUP, NETWORK, SUBNET, SUBNET_ID, VSERVER_IPs, and MGMT_IP values in fields to the right of the labels](media/avere-vfxt-outputs-values.png)
 
 ## Next steps
 

articles/avere-vfxt/avere-vfxt-open-ticket.md

@@ -4,7 +4,7 @@ description: Explanation of opening support tickets about Avere vFXT for Azure
 author: ekpgh
 ms.service: avere-vfxt
 ms.topic: conceptual
-ms.date: 12/19/2019
+ms.date: 01/09/2020
 ms.author: rohogue
 ---
 
@@ -22,25 +22,31 @@ If you encounter issues while deploying or using Avere vFXT, request help throug
 
 Follow these steps to make sure that your support ticket is tagged with a resource from your cluster. Tagging the ticket helps us route it to the correct support resource.
 
-1. From [https://portal.azure.com](https://portal.azure.com), select **Resource Groups**.
-
-1. Browse to the resource group that contains the vFXT cluster where the issue occurred, and click on one of the Avere virtual machines.
+1. From [https://portal.azure.com](https://portal.azure.com), select **Resource Groups**. Browse to the resource group that contains the vFXT cluster where the issue occurred, and click on one of the Avere virtual machines.
 
     ![screenshot of Azure portal resource group "overview" panel with a particular VM circled](media/avere-vfxt-ticket-vm.png)
 
 1. In the VM page, scroll down to the bottom of the left panel and click **New support request**.
 
-    ![Screenshot of the Azure portal VM page for the VM from the previous screenshot. The left menu is scrolled to the bottom and "New support request" is circled.](media/avere-vfxt-ticket-request.png)
+    ![Screenshot of the Azure portal VM page for the VM from the previous screenshot. The left menu is scrolled to the bottom and 'New support request' is circled.](media/avere-vfxt-ticket-request.png)
+
+1. On the first page of the support request, choose the issue type and make sure the correct subscription is selected.
+
+   Under **Service**, click **All Services** and look under **Storage** to choose **Avere vFXT**.
+
+   Add a short summary, and select the problem type.
+
+    ![screenshot of a new support request screen in the Azure portal. The Basics tab is selected. Screen items include Issue type, Subscription, Service, Summary, and Problem type.](media/ticket-basics.png)
 
-1. On page one of the support request, click **All Services** and look under **Storage** to choose **Avere vFXT**.
+1. The second page of the support form contains suggestions for fixing the problem based on your summary description. Click the **Next** button at the bottom if you still need to create a support ticket.
 
-    ![screenshot of the new support request screen in the Azure portal with the header "Basics" and a circle around the "Service" item. The button "All services" is selected and the drop-down menu field has the value "Avere vFXT"](media/avere-vfxt-ticket-service.png)
+   ![screenshot of the new support request screen with the Solutions tab selected. A text field in the middle has the title 'Recommended solution' and explains possible remedies.](media/ticket-solutions.png)
 
-1. Choose the problem type and category that most closely match your issue. Add a short summary and a description that includes the time the issue occurred.
+1. In the third page, provide details - this includes information about your cluster, the time the problem occurred, the severity, and how to contact you.
 
-   ![screenshot of the new support request screen with the header "Problem", which contains many fields that need to be completed](media/avere-vfxt-ticket-problem.png)
+   ![screenshot of the new support request screen with the Details tab selected. Information fields are organized into the categories 'Problem details', 'Support method', and "Contact info'.](media/ticket-details.png)
 
-1. Fill in your contact information when requested and click **Create**. A confirmation and ticket number will be sent to your email address, and a support staff member will contact you.
+1. Review the information on the final page and click **Create**. A confirmation and ticket number will be sent to your email address, and a support staff member will contact you.
 
 ## Request a quota increase
 

articles/avere-vfxt/avere-vfxt-prereqs.md

@@ -4,17 +4,17 @@ description: Prerequisites for Avere vFXT for Azure
 author: ekpgh
 ms.service: avere-vfxt
 ms.topic: conceptual
-ms.date: 02/20/2019
+ms.date: 01/09/2020
 ms.author: rohogue
 ---
 
 # Prepare to create the Avere vFXT
 
-This article explains the prerequisite tasks for creating an Avere vFXT cluster.
+This article explains prerequisite tasks for creating an Avere vFXT cluster.
 
 ## Create a new subscription
 
-Start by creating a new Azure subscription. Use a separate subscription for each Avere vFXT project to let you easily track all project resources and expenses, protect other projects from possible resource throttling during provisioning, and simplify cleanup.
+Start by creating a new Azure subscription. Use a separate subscription for each Avere vFXT project to simplify expense tracking and cleanup, and to make sure other projects aren't affected by quotas or resource throttling when provisioning the cluster workflow.
 
 To create a new Azure subscription in the Azure portal:
 
@@ -25,46 +25,49 @@ To create a new Azure subscription in the Azure portal:
 
 ## Configure subscription owner permissions
 
-A user with owner permissions for the subscription should create the vFXT cluster. Subscription owner permissions are needed to accept the software terms of service and perform other actions.
+A user with owner permissions for the subscription should create the vFXT cluster. Cluster creation requires an owner to accept the software terms of service and to authorize changes to network and storage resources.
 
-There are some workaround scenarios that allow a non-owner to create an Avere vFTX for Azure cluster. These scenarios involve restricting resources and assigning additional roles to the creator. In both of these cases, a subscription owner also must [accept the Avere vFXT software terms](#accept-software-terms) ahead of time.
+There are some workarounds to allow a non-owner to create an Avere vFTX for Azure cluster. These scenarios involve restricting resources and assigning additional role-based access control (RBAC) roles to the creator. In all of these cases, a subscription owner also must [accept the Avere vFXT software terms](#accept-software-terms) ahead of time.
 
 | Scenario | Restrictions | Access roles required to create the Avere vFXT cluster |
 |----------|--------|-------|
-| Resource group administrator | The virtual network, cluster controller, and cluster nodes must be created within the resource group | [User Access Administrator](../role-based-access-control/built-in-roles.md#user-access-administrator) and [Contributor](../role-based-access-control/built-in-roles.md#contributor) roles, both scoped to the target resource group |
-| External virtual network | The cluster controller and cluster nodes are created within the resource group but an existing virtual network in a different resource group is used | (1) [User Access Administrator](../role-based-access-control/built-in-roles.md#user-access-administrator) and [Contributor](../role-based-access-control/built-in-roles.md#contributor) roles scoped to the vFXT resource group; and (2) [Virtual Machine Contributor](../role-based-access-control/built-in-roles.md#virtual-machine-contributor), [User Access Administrator](../role-based-access-control/built-in-roles.md#user-access-administrator), and [Avere Contributor](../role-based-access-control/built-in-roles.md#avere-contributor) roles scoped to the virtual network's resource group. |
-
-An alternative is to create a custom role-based access control (RBAC) role ahead of time and assign privileges to the user, as explained in [this article](avere-vfxt-non-owner.md). This method gives significant permissions to these users.
+| Resource group administrator creates the vFXT | The virtual network, cluster controller, and cluster nodes must be created within the resource group. | [User Access Administrator](../role-based-access-control/built-in-roles.md#user-access-administrator) and [Contributor](../role-based-access-control/built-in-roles.md#contributor) roles, both scoped to the target resource group |
+| Use an existing, external virtual network | The cluster controller and cluster nodes are created within the vFXT's resource group but use an existing virtual network in a different resource group. | (1) [User Access Administrator](../role-based-access-control/built-in-roles.md#user-access-administrator) and [Contributor](../role-based-access-control/built-in-roles.md#contributor) roles scoped to the vFXT resource group; and (2) [Virtual Machine Contributor](../role-based-access-control/built-in-roles.md#virtual-machine-contributor), [User Access Administrator](../role-based-access-control/built-in-roles.md#user-access-administrator), and [Avere Contributor](../role-based-access-control/built-in-roles.md#avere-contributor) roles scoped to the virtual network's resource group. |
+| Custom role for cluster creators | No resource placement restrictions. This method gives non-owners significant privileges. | Subscription owner creates a custom RBAC role as explained in [this article](avere-vfxt-non-owner.md). |
 
 ## Quota for the vFXT cluster
 
-You must have sufficient quota for the following Azure components. If needed, [request a quota increase](https://docs.microsoft.com/azure/azure-portal/supportability/resource-manager-core-quotas-request).
+Check that you have sufficient quota for the following Azure components. If needed, [request a quota increase](https://docs.microsoft.com/azure/azure-supportability/resource-manager-core-quotas-request).
 
 > [!NOTE]
-> The virtual machines and SSD components listed here are for the vFXT cluster itself. You will need additional quota for the VMs and SSD you intend to use for your compute farm.  Make sure the quota is enabled for the region where you intend to run the workflow.
+> The virtual machines and SSD components listed here are for the vFXT cluster itself. Remember that you also need quota for the VMs and SSDs you will use for your compute farm.
+>
+> Make sure the quota is enabled for the region where you intend to run the workflow.
 
 |Azure component|Quota|
 |----------|-----------|
-|Virtual machines|3 or more E32s_v3|
+|Virtual machines|3 or more E32s_v3 (one per cluster node) |
 |Premium SSD storage|200 GB OS space plus 1 TB to 4 TB cache space per node |
 |Storage account (optional) |v2|
 |Data backend storage (optional) |One new LRS Blob container |
 <!-- this table also appears in the overview - update it there if updating here -->
 
 ## Accept software terms
 
-> [!NOTE]
-> This step is not required if a subscription owner creates the Avere vFXT cluster.
+> [!TIP]
+> Skip this step if a subscription owner will create the Avere vFXT cluster.
+
+During cluster creation, you must accept the terms of service for the Avere vFXT software. If you are not a subscription owner, have a subscription owner accept the terms ahead of time.
 
-During cluster creation, you must accept the terms of service for the Avere vFXT software. If you are not a subscription owner, have a subscription owner accept the terms ahead of time. This step only needs to be done once per subscription.
+This step only needs to be done once per subscription.
 
 To accept the software terms in advance:
 
 1. Open a cloud shell in the Azure portal or by browsing to <https://shell.azure.com>. Sign in with your subscription ID.
 
    ```azurecli
     az login​
-    az account set --subscription abc123de-f456-abc7-89de-f01234567890​
+    az account set --subscription <subscription ID>
    ```
 
 1. Issue this command to accept service terms and enable programmatic access for the Avere vFXT for Azure software image:
@@ -77,14 +80,12 @@ To accept the software terms in advance:
 
 A [service endpoint](../virtual-network/virtual-network-service-endpoints-overview.md) keeps Azure Blob traffic local instead of routing it outside the virtual network. It is recommended for any Avere vFXT for Azure cluster that uses Azure Blob for back-end data storage.
 
-If you are providing an existing virtual network and creating a new Azure Blob container for your back-end storage as part of the cluster creation, you must have a service endpoint in the network for Microsoft storage. This endpoint must exist before creating the cluster, or the creation will fail.
-
-A storage service endpoint is recommended for any Avere vFXT for Azure cluster that uses Azure Blob storage, even if you add the storage later.
+If you create a new virtual network while creating the cluster, an endpoint is created automatically. If you provide an existing virtual network, it must have a Microsoft storage service endpoint if you want to create a new Blob storage container during cluster creation.<!-- if there is no endpoint in that situation, the cluster creation will fail -->
 
 > [!TIP]
 >
 >* Skip this step if you are creating a new virtual network as part of cluster creation.
->* This step is optional if you are not creating Blob storage during cluster creation. In that case, you can create the service endpoint later if you decide to use Azure Blob.
+>* An endpoint is optional if you are not creating Blob storage during cluster creation. In that case, you can create the service endpoint later if you decide to use Azure Blob.
 
 Create the storage service endpoint from the Azure portal.
 
@@ -100,4 +101,4 @@ Create the storage service endpoint from the Azure portal.
 
 ## Next step: Create the vFXT cluster
 
-After completing these prerequisites, you can jump into creating the cluster itself. Read [Deploy the vFXT cluster](avere-vfxt-deploy.md) for instructions.
+After completing these prerequisites, you can create the cluster. Read [Deploy the vFXT cluster](avere-vfxt-deploy.md) for instructions.

articles/avere-vfxt/avere-vfxt-whitepapers.md

@@ -5,7 +5,7 @@ ms.service: avere-vfxt
 author: ekpgh
 ms.author: rohogue
 ms.topic: conceptual
-ms.date: 1/06/2020
+ms.date: 01/06/2020
 ---
 
 # Azure vFTX for Azure whitepapers and other resources