You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/hpc-cache/hpc-cache-add-storage.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: How to define storage targets so that your Azure HPC Cache can use
4
4
author: ekpgh
5
5
ms.service: hpc-cache
6
6
ms.topic: conceptual
7
-
ms.date: 11/11/2019
7
+
ms.date: 11/18/2019
8
8
ms.author: rohogue
9
9
---
10
10
@@ -53,7 +53,7 @@ When finished, click **OK** to add the storage target.
53
53
54
54
### Add the access control roles to your account
55
55
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.
57
57
58
58
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".
59
59
@@ -74,7 +74,7 @@ Steps to add the RBAC roles:
74
74
> [!NOTE]
75
75
> 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.
76
76
77
-
1. Click the **Save** button to add the role assignment to the storage account.
77
+
1. Click the **Save** button at the bottom.
78
78
79
79
1. Repeat this process to assign the role "Storage Blob Data Contributor".
80
80
@@ -94,7 +94,7 @@ Provide this information for an NFS-backed storage target:
94
94
95
95
***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.)
96
96
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.
98
98
99
99
### NFS namespace paths
100
100
@@ -152,4 +152,4 @@ After creating storage targets, consider one of these tasks:
152
152
*[Mount the Azure HPC Cache](hpc-cache-mount.md)
153
153
*[Move data to Azure Blob storage](hpc-cache-ingest.md)
154
154
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).
Copy file name to clipboardExpand all lines: articles/hpc-cache/hpc-cache-blob-firewall-fix.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.author: rohogue
10
10
11
11
# Work around Blob storage account firewall settings
12
12
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.
14
14
15
15
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.
Copy file name to clipboardExpand all lines: articles/hpc-cache/hpc-cache-manage.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: How to manage and update Azure HPC Cache using the Azure portal
4
4
author: ekpgh
5
5
ms.service: hpc-cache
6
6
ms.topic: conceptual
7
-
ms.date: 11/12/2019
7
+
ms.date: 11/18/2019
8
8
ms.author: rohogue
9
9
---
10
10
@@ -14,7 +14,7 @@ The cache overview page in the Azure portal shows project details, cache status,
14
14
15
15
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.
16
16
17
-

17
+

18
18
19
19
The buttons at the top of the page can help you manage the cache:
20
20
@@ -36,7 +36,7 @@ The **Flush** button on the overview page tells the cache to immediately write a
36
36
37
37
When you start the cache flush operation, the cache stops accepting client requests, and the cache status on the overview page changes to **Flushing**.
38
38
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.
40
40
41
41
After all the data is saved to storage targets, the cache automatically starts taking client requests again. The cache status returns to **Healthy**.
0 commit comments