Merge pull request #89614 from ekpgh/hpc-cache-updatepreview-2

edit pass, remove  unused images

Author: tiburd

articles/hpc-cache/hpc-cache-add-storage.md

@@ -4,7 +4,7 @@ description: How to define storage targets so that your Azure HPC Cache can use
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: conceptual
-ms.date: 09/06/2019
+ms.date: 09/24/2019
 ms.author: v-erkell
 ---
 
@@ -16,11 +16,11 @@ You can define up to ten different storage targets for one cache. The cache pres
 
 Remember that the storage exports must be accessible from your cache's virtual network. For on-premises hardware storage, you might need to set up a DNS server that can resolve hostnames for NFS storage access. Read more in [DNS access](hpc-cache-prereqs.md#dns-access).
 
-You can add storage targets while creating your Azure HPC Cache, or afterward. The procedure is slightly different depending on whether you're adding Azure Blob storage or an NFS export. Details for each are below.
+You can add storage targets while creating your cache, or afterward. The procedure is slightly different depending on whether you're adding Azure Blob storage or an NFS export. Details for each are below.
 
 ## Add storage targets while creating the cache
 
-Use the **Storage targets** tab of the cache creation wizard to define storage at the same time you create the cache instance.
+Use the **Storage targets** tab of the Azure HPC Cache creation wizard to define storage at the same time you create the cache instance.
 
 ![screenshot of storage targets page](media/hpc-cache-storage-targets-pop.png)
 
@@ -40,6 +40,8 @@ To define an Azure Blob container, enter this information.
 
 ![screenshot of the add storage target page, populated with information for a new Azure Blob storage target](media/hpc-cache-add-blob.png)
 
+<!-- need to replace screenshot after note text is updated with both required RBAC roles -->
+
 * **Storage target name** - Set a name that identifies this storage target in the Azure HPC Cache.
 * **Target type** - Choose **Blob**.
 * **Storage account** - Select the account with the container to reference.
@@ -53,7 +55,7 @@ When finished, click **OK** to add the storage target.
 
 ### Add the access control roles to your account
 
-The Azure HPC Cache uses [role-based access control (RBAC)](https://docs.microsoft.com/azure/role-based-access-control/index) to authorize the cache application to access your storage account for Azure Blob storage targets.
+Azure HPC Cache uses [role-based access control (RBAC)](https://docs.microsoft.com/azure/role-based-access-control/index) to authorize the cache application to access your storage account for Azure Blob storage targets.
 
 The storage account owner must explicitly add the roles [Storage Account Contributor](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#storage-account-contributor) and [Storage Blob Data Contributor](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#storage-blob-data-contributor) for the user "StorageCache Resource Provider".
 
@@ -93,9 +95,14 @@ Provide this information for an NFS-backed storage target:
 
 * **Usage model** - Choose one of the data caching profiles based on your workflow, described in [Choose a usage model, below](#choose-a-usage-model).
 
-You can create multiple namespace paths to represent different exports on the same NFS storage system, but you must create them all from one storage target.
+### NFS namespace paths
+
+An NFS storage target can have multiple virtual paths, as long as each path represents a different export or subdirectory on the same storage system.
+
+Create all of the paths from one storage target.
+<!-- You can create multiple namespace paths to represent different exports on the same NFS storage system, but you must create them all from one storage target. -->
 
-For each export, fill in these values:
+Fill in these values for each namespace path: 
 
 * **Virtual namespace path** - Set the client-facing filepath for this storage target. Read [Configure aggregated namespace](hpc-cache-namespace.md) to learn more about the virtual namespace feature.
 

articles/hpc-cache/hpc-cache-create.md

@@ -4,7 +4,7 @@ description: How to create an Azure HPC Cache instance
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: tutorial
-ms.date: 09/06/2019
+ms.date: 09/24/2019
 ms.author: v-erkell
 ---
 
@@ -18,18 +18,20 @@ Use the Azure portal to create your cache.
 
 ![screenshot of project details page in Azure portal](media/hpc-cache-create-basics.png)
 
-In **Project Details**, select the subscription and resource group that will host the Azure HPC Cache. Make sure the subscription is on the [preview access](hpc-cache-prereqs.md#azure-subscription) list.
+In **Project Details**, select the subscription and resource group that will host the cache. Make sure the subscription is on the [preview access](hpc-cache-prereqs.md#azure-subscription) list.
 
 In **Service Details**, set the cache name and these other attributes:
 
 * Location - Select one of the [supported regions](hpc-cache-overview.md#region-availability).
 * Virtual network - You can select an existing one or create a new virtual network.
-* Subnet - Choose or create a subnet with at least 64 IP addresses (/24) that will be used only for the Azure HPC Cache.
+* Subnet - Choose or create a subnet with at least 64 IP addresses (/24) that will be used only for this Azure HPC Cache instance.
 
 ## Set cache capacity
 <!-- referenced from GUI - update aka.ms link if you change this header text -->
 
-On the **Cache** page, you must set the capacity of your Azure HPC Cache. This value determines how much data your cache can hold and how quickly it can service client requests. After the public preview period, capacity will also affect the cache's cost.
+On the **Cache** page, you must set the capacity of your cache. This value determines how much data your cache can hold and how quickly it can service client requests. 
+
+After the public preview period, capacity also will affect the cache's cost.
 
 Cache capacity is measured in input/output operations per second (IOPS). Choose the capacity by setting these two values:
 
@@ -38,9 +40,9 @@ Cache capacity is measured in input/output operations per second (IOPS). Choose
 
 Choose one of the available throughput values and cache storage sizes. The IOPS capacity is calculated and shown below the value selectors.
 
-Keep in mind that the actual data transfer rate depends on workload, network speeds, and the type of storage targets. If a file isn't in the cache, or it is marked as stale, the service will use some throughput to fetch it from backend storage. The value you choose sets the maximum throughput for the entire cache, and not all of it is available for client requests.
+Keep in mind that the actual data transfer rate depends on workload, network speeds, and the type of storage targets. The value you choose sets the maximum throughput for the entire cache, and not all of it is available for client requests. For example, if a client requests a file that isn't already stored in the cache, or if the file is marked as stale, your cache uses some of its throughput to fetch it from backend storage.
 
-For cache storage, Azure HPC Cache manages which files are cached and preloaded to maximize cache hit rates. The cache contents are continuously assessed and files are moved to long-term storage when they are less frequently accessed. Choose a cache storage size that can comfortably hold the active set of working files with additional space for metadata and other overhead.
+Azure HPC Cache manages which files are cached and preloaded to maximize cache hit rates. The cache contents are continuously assessed and files are moved to long-term storage when they are less frequently accessed. Choose a cache storage size that can comfortably hold the active set of working files with additional space for metadata and other overhead.
 
 ![screenshot of cache sizing page](media/hpc-cache-create-iops.png)
 
@@ -58,7 +60,7 @@ You can define up to ten different storage targets.
 
 Step-by-step instructions to add a storage target are included in [Add storage targets](hpc-cache-add-storage.md). The procedure is different for Blob storage or for NFS exports.
 
-Here are some tips: 
+Here are some tips:
 
 * For both types of storage, you must specify how to find the back-end storage system (either an NFS address or a Blob container name) and the client-facing namespace path.
 
@@ -68,7 +70,7 @@ Here are some tips:
 
 ## Add resource tags (optional)
 
-The **Tags** page lets you add [resource tags](https://go.microsoft.com/fwlink/?linkid=873112) to your Azure HPC Cache. 
+The **Tags** page lets you add [resource tags](https://go.microsoft.com/fwlink/?linkid=873112) to your Azure HPC Cache instance.
 
 ## Finish creating the cache
 

articles/hpc-cache/hpc-cache-ingest.md

@@ -4,21 +4,21 @@ description: How to populate Azure Blob storage for use with Azure HPC Cache
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: conceptual
-ms.date: 09/18/2019
+ms.date: 09/24/2019
 ms.author: v-erkell
 ---
 
-# Move data to Azure Blob storage for Azure HPC Cache (preview)
+# Move data to Azure Blob storage
 
-If your workflow includes moving data to Azure Blob storage, make sure you are using an efficient strategy to copy your data through the Azure HPC Cache.
+If your workflow includes moving data to Azure Blob storage, make sure you are using an efficient strategy. You can either preload data in a new Blob container before defining it as a storage target, or add the container and then copy your data using Azure HPC Cache.
 
 This article explains the best ways to move data to Blob storage for use with Azure HPC Cache.
 
 Keep these facts in mind:
 
 * Azure HPC Cache uses a specialized storage format to organize data in Blob storage. This is why a Blob storage target must either be a new, empty container, or a Blob container that was previously used for Azure HPC Cache data. ([Avere vFXT for Azure](https://azure.microsoft.com/services/storage/avere-vfxt/) also uses this cloud filesystem.)
 
-* Copying data through the Azure HPC Cache is best when you use multiple clients and parallel operations. A simple copy command from one client will move data slowly.
+* Copying data through the Azure HPC Cache to a back-end storage target is more efficient when you use multiple clients and parallel operations. A simple copy command from one client will move data slowly.
 
 A Python-based utility is available to load content into a Blob storage container. Read [Pre-load data in Blob storage](#pre-load-data-in-blob-storage-with-clfsload) to learn more.
 
@@ -36,7 +36,7 @@ Detailed information is included in the Avere CLFSLoad distribution, which is av
 
 A general overview of the process:
 
-1. Prepare a Linux system (VM or physical) with Python version 3.6 or later. (Python 3.7 is recommended for better performance.)
+1. Prepare a Linux system (VM or physical) with Python version 3.6 or later. Python 3.7 is recommended for better performance.
 1. Install the Avere-CLFSLoad software on the Linux system.
 1. Execute the transfer from the Linux command line.
 
@@ -45,7 +45,7 @@ The Avere CLFSLoad utility needs the following information:
 * The storage account ID that contains your Blob storage container
 * The name of the empty Blob storage container
 * A shared access signature (SAS) token that allows the utility to write to the container
-* A local path to the data source - either a local directory that contains the data to copy, or a local path to a mounted remote system with the data.
+* A local path to the data source - either a local directory that contains the data to copy, or a local path to a mounted remote system with the data
 
 <!-- The requirements are explained in detail in the [Avere CLFSLoad readme](https://aka.ms/avere-clfsload). -->
 

articles/hpc-cache/hpc-cache-mount.md

@@ -4,22 +4,26 @@ description: How to connect clients to an Azure HPC Cache service
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: conceptual
-ms.date: 09/12/2019
+ms.date: 09/24/2019
 ms.author: v-erkell
 ---
 
 # Mount the Azure HPC Cache (preview)
 
 After the cache is created, NFS clients can access it with a simple mount command.
 
-Use the mount addresses listed on the cache overview page and the virtual namespace path that you set when you created the storage target. 
+The mount command is made up of two elements:
+
+* One of the cache's mount addresses (listed on the cache overview page)
+* The virtual namespace path that you set when you created the storage target
 
 ![screenshot of Azure HPC Cache instance's Overview page, with a highlight box around the mount addresses list on the lower right](media/hpc-cache-mount-addresses.png)
 
 > [!NOTE] 
-> The cache mount addresses correspond to network interfaces inside the cache's subnet. These NICs appear in the resource group with names ending in `-cluster-nic-` and a number. Do not alter or delete these interfaces, or the cache will become unavailable.
+> The cache mount addresses correspond to network interfaces inside the cache's subnet. In a resource group, these NICs are listed with names ending in `-cluster-nic-` and a number. Do not alter or delete these interfaces, or the cache will become unavailable.
+
+The virtual namespace paths are shown in the **Storage targets** page. Click an individual storage target name to see its details, including aggregated namespace paths associated with it.
 
-The virtual namespace paths are shown in the **Storage targets** page. Click the target name to see details, including the aggregated namespace path (or paths) associated with it. 
 ![screenshot of the cache's Storage target panel, with a highlight box around an entry in the Path column of the table](media/hpc-cache-view-namespace-paths.png)
 
 ## Mount command syntax
@@ -28,15 +32,15 @@ Use a mount command like the following:
 
 > sudo mount *cache_mount_address*:/*namespace_path* *local_path* {*options*}
 
-Example: 
+Example:
 
 ```
 root@test-client:/tmp# mkdir hpccache
 root@test-client:/tmp# sudo mount 10.0.0.28:/blob-demo-0722 ./hpccache/ -orw,tcp,mountproto=tcp,vers3,hard,intr
 root@test-client:/tmp# 
 ```
 
-After this command succeeds, the contents of the storage export should be visible in the ``hpccache`` directory on the client. 
+After this command succeeds, the contents of the storage export should be visible in the ``hpccache`` directory on the client.
 
 > [!NOTE] 
 > Your clients must be able to access the virtual network and subnet that houses your cache. For example, create client VMs within the same virtual network, or use an endpoint, gateway, or other solution in the virtual network for access from outside. Remember that nothing else can be hosted inside the cache's subnet.

articles/hpc-cache/hpc-cache-namespace.md

@@ -4,19 +4,21 @@ description: How to create an Azure HPC Cache instance
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: conceptual
-ms.date: 09/06/2019
+ms.date: 09/24/2019
 ms.author: v-erkell
 ---
 
 # Plan the aggregated namespace
 
 Azure HPC Cache (preview) allows clients to access a variety of storage systems through a virtual namespace that hides the details of the back-end storage system.
 
-When you add a storage target, you set the client-facing filepath. Client machines mount this filepath. You can change the storage target associated with that path. For example, you could replace a hardware storage system with cloud storage without needing to rewrite client-facing procedures.
+When you add a storage target, you set the client-facing filepath. Client machines mount this filepath and can make file read requests to the cache instead of mounting the storage system directly.
+
+Because Azure HPC Cache manages this virtual filesystem, you can change the storage target without changing the client-facing path. For example, you could replace a hardware storage system with cloud storage without needing to rewrite client-facing procedures.
 
 ## Aggregated namespace example
 
-Plan your aggregated namespace so that client machines can conveniently reach the information they need, and administrators and workflow engineers can easily distinguish the paths.
+Plan your aggregated namespace so that client machines can conveniently reach the information they need, and so that administrators and workflow engineers can easily distinguish the paths.
 
 For example, consider a system where an Azure HPC Cache instance is being used to process data stored in Azure Blob. The analysis requires template files that are stored in an on-premises datacenter.
 
@@ -35,20 +37,22 @@ The data to be analyzed has been copied to an Azure Blob storage container named
 
 To allow easy access through the cache, consider creating storage targets with these virtual namespace paths:
 
-| Back-end NFS filepath or Blob container | Virtual namespace path |
+| Back-end storage system <br/> (NFS filepath or Blob container) | Virtual namespace path |
 |-----------------------------------------|------------------------|
 | /goldline/templates/acme2017/sku798     | /templates/sku798      |
 | /goldline/templates/acme2017/sku980     | /templates/sku980      |
 | sourcecollection                        | /source/               |
 
-Since the NFS source paths are subdirectories of the same export, you will need to define multiple namespace paths from the same storage target. 
+An NFS storage target can have multiple virtual namespace paths, as long as each one references a unique export path.
+
+Since the NFS source paths are subdirectories of the same export, you will need to define multiple namespace paths from the same storage target.
 
 | Storage target hostname  | NFS export path      | Subdirectory path | Namespace path    |
 |--------------------------|----------------------|-------------------|-------------------|
 | *IP address or hostname* | /goldline/templates  | acme2017/sku798   | /templates/sku798 |
 | *IP address or hostname* | /goldline/templates  | acme2017/sku980   | /templates/sku980 |
 
-A client application can mount the cache and easily access the aggregated namespace filepaths /source, /templates/sku798, and /templates/sku980.
+A client application can mount the cache and easily access the aggregated namespace filepaths ``/source``, ``/templates/sku798``, and ``/templates/sku980``.
 
 ## Next steps