Merge pull request #89235 from ekpgh/hpc-cache-updatepreview-1

rework toc, text updates

Author: ktoliver

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

@@ -1,5 +1,5 @@
 ---
-title: Add storage to an Azure HPC Cache 
+title: Add storage to an Azure HPC Cache (preview)
 description: How to define storage targets so that your Azure HPC Cache can use your on-premises NFS system or Azure Blob containers for long-term file storage 
 author: ekpgh
 ms.service: hpc-cache
@@ -8,7 +8,7 @@ ms.date: 09/06/2019
 ms.author: v-erkell
 ---
 
-# Add storage
+# Add storage targets
 
 *Storage targets* are back-end storage for files that are accessed through an Azure HPC Cache instance. You can add NFS storage, like an on-premises hardware system, or store data in Azure Blob.
 
@@ -107,8 +107,8 @@ For each export, fill in these values:
 
 When finished, click **OK** to add the storage target.
 
-### Choose a usage model 
-<!-- link in GUI to this heading -->
+### Choose a usage model
+<!-- referenced from GUI - update aka.ms link if you change this heading -->
 
 When you create a storage target that points to an NFS storage system, you need to choose the *usage model* for that target. This model determines how your data is cached.
 

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

@@ -1,5 +1,5 @@
 ---
-title: Create an Azure HPC Cache 
+title: Create an Azure HPC Cache (preview)
 description: How to create an Azure HPC Cache instance
 author: ekpgh
 ms.service: hpc-cache
@@ -8,9 +8,9 @@ ms.date: 09/06/2019
 ms.author: v-erkell
 ---
 
-# Create an Azure HPC Cache
+# Create an Azure HPC Cache (preview)
 
-Use the Azure portal to create your cache.
+Use the Azure portal to create your cache. 
 
 ![screenshot of cache overview in Azure portal, with create button at the bottom](media/hpc-cache-home-page.png)
 
@@ -27,7 +27,7 @@ In **Service Details**, set the cache name and these other attributes:
 * Subnet - Choose or create a subnet with at least 64 IP addresses (/24) that will be used only for the Azure HPC Cache.
 
 ## Set cache capacity
-<!-- change link in GUI -->
+<!-- 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.
 
@@ -56,7 +56,7 @@ Click the **Add storage target link** to define your back-end storage systems. T
 
 You can define up to ten different storage targets.
 
-Step-by-step instructions to add a storage target are included in [Add storage](hpc-cache-add-storage.md). The procedure is different for Blob storage or for NFS exports.
+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: 
 

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

@@ -1,5 +1,5 @@
 ---
-title: Azure HPC Cache data ingest - manual copy
+title: Azure HPC Cache Preview data ingest - manual copy
 description: How to use cp commands to move data to a Blob storage target in Azure HPC Cache
 author: ekpgh
 ms.service: hpc-cache
@@ -8,7 +8,7 @@ ms.date: 08/30/2019
 ms.author: v-erkell
 ---
 
-# Azure HPC Cache data ingest - manual copy method
+# Azure HPC Cache (preview) data ingest - manual copy method
 
 This article gives detailed instructions for manually copying data to a Blob storage container for use with Azure HPC Cache. It uses multi-threaded parallel operations to optimize the copy speed.
 

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

@@ -1,5 +1,5 @@
 ---
-title: Azure HPC Cache data ingest - msrsync
+title: Azure HPC Cache Preview data ingest - msrsync
 description: How to use msrsync to move data to a Blob storage target in Azure HPC Cache
 author: ekpgh
 ms.service: hpc-cache
@@ -8,7 +8,7 @@ ms.date: 08/30/2019
 ms.author: v-erkell
 ---
 
-# Azure HPC Cache data ingest - msrsync method
+# Azure HPC Cache (preview) data ingest - msrsync method
 
 This article gives detailed instructions for using the ``msrsync`` utility to copy data to an Azure Blob storage container for use with Azure HPC Cache.
 

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

@@ -1,5 +1,5 @@
 ---
-title: Azure HPC Cache data ingest - parallel copy script
+title: Azure HPC Cache Preview data ingest - parallel copy script
 description: How to use a parallel copy script to move data to a Blob storage target in Azure HPC Cache
 author: ekpgh
 ms.service: hpc-cache
@@ -8,7 +8,7 @@ ms.date: 08/30/2019
 ms.author: v-erkell
 ---
 
-# Azure HPC Cache data ingest - parallel copy script method
+# Azure HPC Cache (preview) data ingest - parallel copy script method
 
 This article gives instructions for creating the ``parallelcp`` script and using it to move data to a Blob storage container for use with Azure HPC Cache.
 

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

@@ -1,5 +1,5 @@
 ---
-title: Move data to an Azure HPC Cache cloud container 
+title: Move data to an Azure HPC Cache (Preview) cloud container 
 description: How to populate Azure Blob storage for use with Azure HPC Cache
 author: ekpgh
 ms.service: hpc-cache
@@ -8,7 +8,7 @@ ms.date: 09/18/2019
 ms.author: v-erkell
 ---
 
-# Move data to Azure Blob storage for Azure HPC Cache
+# Move data to Azure Blob storage for Azure HPC Cache (preview)
 
 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.
 
@@ -28,7 +28,7 @@ If you don't want to use the loading utility, or if you want to add content to a
 
 You can use the <!--[Avere CLFSLoad](https://aka.ms/avere-clfsload)--> Avere CLFSLoad utility to copy data to a new Blob storage container before you add it as a storage target. This utility runs on a single Linux system and writes data in the proprietary format needed for Azure HPC Cache. CLFSLoad is the most efficient way to populate a Blob storage container for use with the cache.
 
-The Avere CLFSLoad utility is available by request from your Azure HPC Cache team. Ask your team contact, or open a support ticket to request assistance.
+The Avere CLFSLoad utility is available by request from your Azure HPC Cache team. Ask your team contact for it, or open a [support ticket](hpc-cache-support-ticket.md) to request assistance.
 
 This option works with new, empty containers only. Create the container before using Avere CLFSLoad.
 
@@ -55,7 +55,7 @@ If you don't want to use the Avere CLFSLoad utility, or if you want to add a lar
 
 ![Diagram showing multi-client, multi-threaded data movement: At the top left, an icon for on-premises hardware storage has multiple arrows coming from it. The arrows point to four client machines. From each client machine three arrows point toward the Azure HPC Cache. From the Azure HPC Cache, multiple arrows point to Blob storage.](media/hpc-cache-parallel-ingest.png) 
 
-The ``cp`` or ``copy`` commands that you typically use to transfer data from one storage system to another are single-threaded processes that copy only one file at a time. This means that the file server is ingesting only one file at a time - which is a waste of the cluster’s resources.
+The ``cp`` or ``copy`` commands that you typically use to transfer data from one storage system to another are single-threaded processes that copy only one file at a time. This means that the file server is ingesting only one file at a time - which is a waste of the cache's resources.
 
 This section explains strategies for creating a multi-client, multi-threaded file copying system to move data to Blob storage with Azure HPC Cache. It explains file transfer concepts and decision points that can be used for efficient data copying using multiple clients and simple copy commands.
 

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

@@ -1,5 +1,5 @@
 ---
-title: Mount an Azure HPC Cache 
+title: Mount an Azure HPC Cache (preview)
 description: How to connect clients to an Azure HPC Cache service
 author: ekpgh
 ms.service: hpc-cache
@@ -8,7 +8,7 @@ ms.date: 09/12/2019
 ms.author: v-erkell
 ---
 
-# Mount the Azure HPC Cache
+# Mount the Azure HPC Cache (preview)
 
 After the cache is created, NFS clients can access it with a simple mount command.
 
@@ -49,7 +49,7 @@ For a robust client mount, pass these settings and arguments in your mount comma
 
 | Recommended mount command settings | |
 --- | --- 
-``hard`` | Soft mounts to the vFXT cluster are associated with application failures and possible data loss. 
+``hard`` | Soft mounts to Azure HPC Cache are associated with application failures and possible data loss. 
 ``proto=netid`` | This option supports appropriate handling of NFS network errors.
 ``mountproto=netid`` | This option supports appropriate handling of network errors for mount operations.
 ``retry=n`` | Set ``retry=30`` to avoid transient mount failures. (A different value is recommended in foreground mounts.)

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

@@ -1,5 +1,5 @@
 ---
-title: Create an Azure HPC Cache 
+title: Create an Azure HPC Cache (preview)
 description: How to create an Azure HPC Cache instance
 author: ekpgh
 ms.service: hpc-cache
@@ -8,10 +8,9 @@ ms.date: 09/06/2019
 ms.author: v-erkell
 ---
 
-# Configure aggregated namespace
-<!-- change link in GUI -->
+# Plan the aggregated namespace
 
-Azure HPC Cache allows clients to access a variety of storage systems through a virtual namespace that hides the details of the back-end storage system.
+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.
 
@@ -26,7 +25,7 @@ The template data is stored in a datacenter, and the information needed for this
     /goldline/templates/acme2017/sku798
     /goldline/templates/acme2017/sku980 
 
-The datacenter storage system exposes these exports: 
+The datacenter storage system exposes these exports:
 
     /
     /goldline

articles/hpc-cache/hpc-cache-overview.md

@@ -1,14 +1,14 @@
 ---
-title: Azure HPC Cache overview 
+title: Azure HPC Cache Preview overview 
 description: Describes Azure HPC Cache, a file access accelerator solution for high-performance computing 
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: overview
-ms.date: 09/06/2019
+ms.date: 09/19/2019
 ms.author: v-erkell
 ---
 
-# What is Azure HPC Cache?
+# What is Azure HPC Cache? (Preview)
 
 Azure HPC Cache speeds access to your data for high-performance computing (HPC) tasks. By caching files in Azure, it makes the scalability of cloud computing available even for workflows where your data is stored across WAN links, such as in your local datacenter network-attached storage (NAS) environment.
 
@@ -53,6 +53,10 @@ Azure HPC Cache is available in these Azure regions:
 
 Check the [Azure HPC Cache product page](https://azure.microsoft.com/services/hpc-cache) for the latest availability information.
 
+## Preview availability
+
+The Azure HPC Cache public preview is restricted to ensure service quality. Request access by filling out [this form](https://aka.ms/onboard-hpc-cache). After your subscription is added to the access list you can create test caches.
+
 ## Next steps
 
 * Read the [Azure HPC Cache product page](https://azure.microsoft.com/services/hpc-cache) to learn more about its capabilities

articles/hpc-cache/hpc-cache-prereqs.md

@@ -1,5 +1,5 @@
 ---
-title: Azure HPC Cache prerequisites
+title: Azure HPC Cache (preview) prerequisites
 description: Prerequisites for using Azure HPC Cache
 author: ekpgh
 ms.service: hpc-cache
@@ -8,7 +8,7 @@ ms.date: 09/06/2019
 ms.author: v-erkell
 ---
 
-# Prerequisites for Azure HPC Cache
+# Prerequisites for Azure HPC Cache (preview)
 
 Before using the Azure portal to create a new Azure HPC Cache, make sure your environment meets these requirements.
 
@@ -54,7 +54,7 @@ Check these permission-related prerequisites before starting to create your cach
 * The Azure HPC Cache needs to be able to create virtual network interfaces (NICs). The user who creates the cache must have sufficient privileges in the subscription to create NICs.
 <!-- There are several ways to authorize this access; read [Additional prerequisites](media/preview-prereqs.md) to learn more. -->
 
-* If using Blob storage, the Azure HPC Cache instance needs authorization to access your storage account. You can use role-based access control (RBAC) to give the cache access to your Blob storage. Two roles are required: Storage Account Contributor, and Storage Blob Data Contributor. Follow the instructions in [Add storage to the cache](hpc-cache-add-storage.md#add-the-access-control-roles-to-your-account).
+* If using Blob storage, the Azure HPC Cache instance needs authorization to access your storage account. You can use role-based access control (RBAC) to give the cache access to your Blob storage. Two roles are required: Storage Account Contributor, and Storage Blob Data Contributor. Follow the instructions in [Add storage targets](hpc-cache-add-storage.md#add-the-access-control-roles-to-your-account).
 
 ## Storage infrastructure
 
@@ -81,7 +81,7 @@ To create a compatible storage account, use these settings:
 
 It's a good practice to use a storage account in the same location as your cache.
 
-You also must give the cache application access to your Azure storage account. Follow the description in [Add storage to the cache](hpc-cache-add-storage.md#add-the-access-control-roles-to-your-account) to give the cache the access roles Storage Account Contributor and Storage Blob Data Contributor. If you are not the storage account owner, have the owner do this step.
+You also must give the cache application access to your Azure storage account. Follow the description in [Add storage targets](hpc-cache-add-storage.md#add-the-access-control-roles-to-your-account) to give the cache the access roles Storage Account Contributor and Storage Blob Data Contributor. If you are not the storage account owner, have the owner do this step.
 
 ## Next steps