Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into freshness51

Author: dagiro

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: 10/30/2019
+ms.date: 11/18/2019
 ms.author: rohogue
 ---
 
@@ -36,7 +36,7 @@ To define an Azure Blob container, enter this information.
 
 * **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.
+* **Storage account** - Select the account with the container that you want to use.
 
   You will need to authorize the cache instance to access the storage account as described in [Add the access roles](#add-the-access-control-roles-to-your-account).
 
@@ -48,13 +48,16 @@ To define an Azure Blob container, enter this information.
 
 When finished, click **OK** to add the storage target.
 
+> [!NOTE]
+> If your storage account firewall is set to restrict access to only "selected networks," use the temporary workaround documented in [Work around Blob storage account firewall settings](hpc-cache-blob-firewall-fix.md).
+
 ### Add the access control roles to your account
 
-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 service 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 "HPC Cache Resource Provider".
 
-You can do this ahead of time, or by clicking a link on the page where you add a Blob storage target.
+You can do this ahead of time, or by clicking a link on the page where you add a Blob storage target. Keep in mind that it can take up to five minutes for the role settings to propagate through the Azure environment, so you should wait a few minutes after adding the roles before creating a storage target.
 
 Steps to add the RBAC roles:
 
@@ -71,15 +74,15 @@ Steps to add the RBAC roles:
    > [!NOTE]
    > If a search for "hpc" doesn't work, try using the string "storagecache" instead. Users who joined the previews (before GA) might need to use the older name for the service principal.
 
-1. Click the **Save** button to add the role assignment to the storage account.
+1. Click the **Save** button at the bottom.
 
 1. Repeat this process to assign the role "Storage Blob Data Contributor".  
 
 ![screenshot of add role assignment GUI](media/hpc-cache-add-role.png)
 
 ## Add a new NFS storage target
 
-An NFS storage target has some extra fields to specify how to reach the storage export and how to efficiently cache its data. Also, you can create multiple namespace paths from one NFS host if it has more than one export available.
+An NFS storage target has more fields than the Blob storage target. These fields specify how to reach the storage export and how to efficiently cache its data. Also, an NFS storage target lets you create multiple namespace paths if the NFS host has more than one export available.
 
 ![Screenshot of add storage target page with NFS target defined](media/hpc-cache-add-nfs-target.png)
 
@@ -91,14 +94,15 @@ Provide this information for an NFS-backed storage target:
 
 * **Hostname** - Enter the IP address or fully qualified domain name for your NFS storage system. (Use a domain name only if your cache has access to a DNS server that can resolve the name.)
 
-* **Usage model** - Choose one of the data caching profiles based on your workflow, described in [Choose a usage model, below](#choose-a-usage-model).
+* **Usage model** - Choose one of the data caching profiles based on your workflow, described in [Choose a usage model](#choose-a-usage-model), below.
 
 ### 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. -->
+
+You can [add and edit namespace paths](hpc-cache-edit-storage.md) on a storage target at any time.
 
 Fill in these values for each namespace path:
 
@@ -117,11 +121,29 @@ When finished, click **OK** to add the storage target.
 
 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.
 
-* Read heavy - If you mostly use the cache to speed up data read access, choose this option.
+There are three options:
+
+* **Read heavy, infrequent writes** - Use this option if you want to speed up read access to files that are static or rarely changed.
+
+  This option caches files that clients read, but passes writes through to the back-end storage immediately. Files stored in the cache are never compared to the files on the NFS storage volume.
+
+  Do not use this option if there is a risk that a file might be modified directly on the storage system without first writing it to the cache. If that happens, the cached version of the file will never be updated with changes from the back end, and the data set can become inconsistent.
+
+* **Greater than 15% writes** - This option speeds up both read and write performance. When using this option, all clients must access files through the Azure HPC Cache instead of mounting the back-end storage directly. The cached files will have recent changes that are not stored on the back end.
+
+  In this usage model, files in the cache are not checked against the files on back-end storage. The cached version of the file is assumed to be more current. A modified file in the cache is only written to the back-end storage system after it has been in the cache for an hour with no additional changes.
+
+* **Clients write to the NFS target, bypassing the cache** - Choose this option if any clients in your workflow write data directly to the storage system without first writing to the cache. Files that clients request are cached, but any changes to those files from the client are passed back to the back-end storage system immediately.
+
+  With this usage model, the files in the cache are frequently checked against the back-end versions for updates. This verification allows files to be changed outside of the cache while maintaining data consistency.
 
-* Read/write - If clients use the cache to read and write, choose this option.
+This table summarizes the usage model differences:
 
-* Clients bypass the cache - Choose this option if your clients write data directly to the storage system without first writing to the cache.
+| Usage model | Caching mode | Back-end verification | Maximum write-back delay |
+| ---- | ---- | ---- | ---- |
+| Read heavy, infrequent writes | Read | Never | None |
+| Greater than 15% writes | Read/write | Never | 1 hour |
+| Clients bypass the cache | Read | 30 seconds | None |
 
 ## Next steps
 
@@ -130,4 +152,4 @@ After creating storage targets, consider one of these tasks:
 * [Mount the Azure HPC Cache](hpc-cache-mount.md)
 * [Move data to Azure Blob storage](hpc-cache-ingest.md)
 
-If you need to change a storage target, read [Edit storage targets](hpc-cache-edit-storage.md) to learn how.
+If you need to update any settings, you can [edit a storage target](hpc-cache-edit-storage.md).

articles/hpc-cache/hpc-cache-blob-firewall-fix.md

@@ -0,0 +1,29 @@
+---
+title: Work around storage firewall settings
+description: A storage account network firewall setting can cause failure when creating an Azure Blob storage target in Azure HPC Cache. This article gives a workaround for the limitation until a software fix is in place.
+author: ekpgh
+ms.service: hpc-cache
+ms.topic: conceptual
+ms.date: 11/7/2019
+ms.author: rohogue
+---
+
+# Work around Blob storage account firewall settings
+
+A particular setting used in storage account firewalls can cause your Blob storage target creation to fail. The Azure HPC Cache team is working on a software fix for this problem, but you can work around it by following the instructions in this article.
+
+The firewall setting that allows access only from "selected networks" can prevent the cache from creating a Blob storage target. This configuration is in the storage account's **Firewalls and virtual networks** settings page.
+
+The issue is that the cache service uses a hidden service virtual network that is separate from customer environments. It isn't possible to explicitly authorize this network to access your storage account.
+
+When you create a Blob storage target, the cache service uses this network to check whether or not the container is empty. If the firewall does not allow access from the hidden network, the check fails, and the storage target creation fails.
+
+To work around the problem, temporarily change your firewall settings while creating the storage target:
+
+1. Go to the storage account **Firewalls and virtual networks** page and change the setting "Allow access from" to **All networks**.
+1. Create the Blob storage target in your Azure HPC Cache.
+1. After the storage target has been created successfully, change the account's firewall setting back to **Selected networks**.
+
+Azure HPC Cache does not use the service virtual network to access the finished storage target.
+
+For help with this workaround, [contact Microsoft Service and Support](hpc-cache-support-ticket.md).

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: 10/30/2019
+ms.date: 11/11/2019
 ms.author: rohogue
 ---
 
@@ -59,6 +59,7 @@ Cache creation takes about 10 minutes. You can track the progress in the Azure p
 ![screenshot of cache creation "deployment underway" and "notifications" pages in portal](media/hpc-cache-deploy-status.png)
 
 When creation finishes, a notification appears with a link to the new Azure HPC Cache instance, and the cache appears in your subscription's **Resources** list.
+<!-- double check on notification -->
 
 ![screenshot of Azure HPC Cache instance in Azure portal](media/hpc-cache-new-overview.png)
 

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

@@ -42,7 +42,7 @@ After making changes, click **OK** to update the storage target, or click **Canc
 
 ## Update an Azure Blob storage target
 
-The details page for a Blob storage target lets you modify the virtual namespace path. 
+The details page for a Blob storage target lets you modify the virtual namespace path.
 
 ![screenshot of the edit page for a blob storage target](media/hpc-cache-edit-storage-blob.png)
 

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

@@ -12,7 +12,7 @@ ms.author: rohogue
 
 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.
 
-To learn more about moving data to Blob storage for your Azure HPC Cache, read [Move data to Azure Blob storage for Azure HPC Cache](hpc-cache-ingest.md).
+To learn more about moving data to Blob storage for your Azure HPC Cache, read [Move data to Azure Blob storage](hpc-cache-ingest.md).
 
 ## Simple copy example
 

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

@@ -12,7 +12,7 @@ ms.author: rohogue
 
 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.
 
-To learn more about moving data to Blob storage for your Azure HPC Cache, read [Move data to Azure Blob storage for Azure HPC Cache](hpc-cache-ingest.md).
+To learn more about moving data to Blob storage for your Azure HPC Cache, read [Move data to Azure Blob storage](hpc-cache-ingest.md).
 
 The ``msrsync`` tool can be used to move data to a backend storage target for the Azure HPC Cache. 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.
 

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

@@ -12,29 +12,29 @@ ms.author: rohogue
 
 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.
 
-To learn more about moving data to Blob storage for your Azure HPC Cache, read [Move data to Azure Blob storage for Azure HPC Cache](hpc-cache-ingest.md).
+To learn more about moving data to Blob storage for your Azure HPC Cache, read [Move data to Azure Blob storage](hpc-cache-ingest.md).
 
 ## Create the parallelcp script
 
 The script below will add the executable `parallelcp`. (This script is designed for Ubuntu; if using another distribution, you must install ``parallel`` separately.)
 
 ```bash
-sudo touch /usr/bin/parallelcp && sudo chmod 755 /usr/bin/parallelcp && sudo sh -c "/bin/cat >/usr/bin/parallelcp" <<EOM 
+sudo touch /usr/bin/parallelcp && sudo chmod 755 /usr/bin/parallelcp && sudo sh -c "/bin/cat >/usr/bin/parallelcp" <<EOM
 #!/bin/bash
 
-display_usage() { 
-    echo -e "\nUsage: \$0 SOURCE_DIR DEST_DIR\n" 
-} 
+display_usage() {
+    echo -e "\nUsage: \$0 SOURCE_DIR DEST_DIR\n"
+}
 
-if [  \$# -le 1 ] ; then 
+if [  \$# -le 1 ] ; then
     display_usage
     exit 1
-fi 
- 
-if [[ ( \$# == "--help") ||  \$# == "-h" ]] ; then 
+fi
+
+if [[ ( \$# == "--help") ||  \$# == "-h" ]] ; then
     display_usage
     exit 0
-fi 
+fi
 
 SOURCE_DIR="\$1"
 DEST_DIR="\$2"

articles/hpc-cache/hpc-cache-manage.md

@@ -4,7 +4,7 @@ description: How to manage and update Azure HPC Cache using the Azure portal
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: conceptual
-ms.date: 10/30/2019
+ms.date: 11/18/2019
 ms.author: rohogue
 ---
 
@@ -14,7 +14,7 @@ The cache overview page in the Azure portal shows project details, cache status,
 
 To open the overview page, select your cache resource in the Azure portal. For example, load the **All resources** page and click the cache name.
 
-![screenshot of an Azure HPC Cache instance's Overview page](media/hpc-cache-overview.png) <!-- placeholder is identical to hpc-cache-new-overview.png; replace with better image (showing graphs, full sidebar) when available -->
+![screenshot of an Azure HPC Cache instance's Overview page](media/hpc-cache-overview.png)
 
 The buttons at the top of the page can help you manage the cache:
 
@@ -32,23 +32,25 @@ The **Flush** button on the overview page tells the cache to immediately write a
 > [!NOTE]
 > During the flush process, the cache can't serve client requests. Cache access is suspended and resumes after the operation finishes.
 
+![screenshot of the top buttons with Flush highlighted and a pop-up message describing the flush action and asking 'do you want to continue?' with Yes (default) and No buttons](media/hpc-cache-flush.png)
+
 When you start the cache flush operation, the cache stops accepting client requests, and the cache status on the overview page changes to **Flushing**.
 
-Data in the cache is saved to the appropriate storage targets. The process can take a few minutes or it can take an hour or more, depending on how much data has been written to the cache recently.
+Data in the cache is saved to the appropriate storage targets. Depending on how much data needs to be flushed, the process can take a few minutes or over an hour.
 
 After all the data is saved to storage targets, the cache automatically starts taking client requests again. The cache status returns to **Healthy**.
 
 ## Upgrade cache software
 
-If a new software version is available, the **Upgrade** button becomes active. You also might see a message at the top of the page about updating software.
+If a new software version is available, the **Upgrade** button becomes active. You also should see a message at the top of the page about updating software.
 
 ![screenshot of the top row of buttons with the Upgrade button enabled](media/hpc-cache-upgrade-button.png)
 
 Client access is not interrupted during a software upgrade, but cache performance slows. Plan to upgrade software during non-peak usage hours or in a planned maintenance period.
 
 The software update can take several hours. Caches configured with higher throughput take longer to upgrade than caches with smaller peak throughput values.
 
-When a software upgrade is available, you have several days to apply it manually. The end date is listed in the upgrade message. If you don't upgrade during that time, Azure automatically applies the update to your cache. The timing of the automatic upgrade is not configurable. If you are concerned about impacting cache performance, you should upgrade the software yourself before the time period expires.
+When a software upgrade is available, you will have a week or so to apply it manually. The end date is listed in the upgrade message. If you don't upgrade during that time, Azure automatically applies the update to your cache. The timing of the automatic upgrade is not configurable. If you are concerned about the cache performance impact, you should upgrade the software yourself before the time period expires.
 
 Click the **Upgrade** button to begin the software update. The cache status changes to **Upgrading** until the operation completes.