Skip to content

Commit a8cc252

Browse files
ekpghjswoodward
authored andcommitted
hpc cache: post-review updates
1 parent c30beb9 commit a8cc252

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: How to define storage targets so that your Azure HPC Cache can use
44
author: ekpgh
55
ms.service: hpc-cache
66
ms.topic: conceptual
7-
ms.date: 11/11/2019
7+
ms.date: 11/18/2019
88
ms.author: rohogue
99
---
1010

@@ -53,7 +53,7 @@ When finished, click **OK** to add the storage target.
5353
5454
### Add the access control roles to your account
5555

56-
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.
56+
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.
5757

5858
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".
5959

@@ -74,7 +74,7 @@ Steps to add the RBAC roles:
7474
> [!NOTE]
7575
> 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.
7676
77-
1. Click the **Save** button to add the role assignment to the storage account.
77+
1. Click the **Save** button at the bottom.
7878

7979
1. Repeat this process to assign the role "Storage Blob Data Contributor".
8080

@@ -94,7 +94,7 @@ Provide this information for an NFS-backed storage target:
9494

9595
* **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.)
9696

97-
* **Usage model** - Choose one of the data caching profiles based on your workflow, described in [Choose a usage model, below](#choose-a-usage-model).
97+
* **Usage model** - Choose one of the data caching profiles based on your workflow, described in [Choose a usage model](#choose-a-usage-model), below.
9898

9999
### NFS namespace paths
100100

@@ -152,4 +152,4 @@ After creating storage targets, consider one of these tasks:
152152
* [Mount the Azure HPC Cache](hpc-cache-mount.md)
153153
* [Move data to Azure Blob storage](hpc-cache-ingest.md)
154154

155-
You also can [edit a storage target](hpc-cache-edit-storage.md).
155+
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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.author: rohogue
1010

1111
# Work around Blob storage account firewall settings
1212

13-
A particular setting used in storage account firewalls can cause your Blob storage target creation to fail. The Azure HPC Cache team is reworking code to prevent this problem, but you can work around it by following the instructions in this article.
13+
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.
1414

1515
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.
1616

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: How to manage and update Azure HPC Cache using the Azure portal
44
author: ekpgh
55
ms.service: hpc-cache
66
ms.topic: conceptual
7-
ms.date: 11/12/2019
7+
ms.date: 11/18/2019
88
ms.author: rohogue
99
---
1010

@@ -14,7 +14,7 @@ The cache overview page in the Azure portal shows project details, cache status,
1414

1515
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.
1616

17-
![screenshot of an Azure HPC Cache instance's Overview page](media/hpc-cache-overview.png)
17+
![screenshot of an Azure HPC Cache instance's Overview page](media/hpc-cache-overview.png)
1818

1919
The buttons at the top of the page can help you manage the cache:
2020

@@ -36,7 +36,7 @@ The **Flush** button on the overview page tells the cache to immediately write a
3636

3737
When you start the cache flush operation, the cache stops accepting client requests, and the cache status on the overview page changes to **Flushing**.
3838

39-
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.
39+
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.
4040

4141
After all the data is saved to storage targets, the cache automatically starts taking client requests again. The cache status returns to **Healthy**.
4242

0 commit comments

Comments
 (0)