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: how-to
7
-
ms.date: 08/19/2020
7
+
ms.date: 09/30/2020
8
8
ms.author: v-erkel
9
9
---
10
10
@@ -71,13 +71,13 @@ When finished, click **OK** to add the storage target.
71
71
72
72
### Add the access control roles to your account
73
73
74
-
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.
74
+
Azure HPC Cache uses [Azure role-based access control (Azure 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.
75
75
76
76
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".
77
77
78
78
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.
79
79
80
-
Steps to add the RBAC roles:
80
+
Steps to add the Azure roles:
81
81
82
82
1. Open the **Access control (IAM)** page for the storage account. (The link in the **Add storage target** page automatically opens this page for the selected account.)
83
83
@@ -106,7 +106,7 @@ Steps to add the RBAC roles:
106
106
107
107
Before you add a blob storage target, check that the cache has the correct roles to access the storage account, and that firewall settings will allow the storage target creation.
108
108
109
-
Azure HPC Cache uses [role-based access control (RBAC)](../role-based-access-control/index.yml) to authorize the cache service to access your storage account for Azure Blob storage targets.
109
+
Azure HPC Cache uses [Azure role-based access control (Azure RBAC)](../role-based-access-control/index.yml) to authorize the cache service to access your storage account for Azure Blob storage targets.
110
110
111
111
The storage account owner must explicitly add the roles [Storage Account Contributor](../role-based-access-control/built-in-roles.md#storage-account-contributor) and [Storage Blob Data Contributor](../role-based-access-control/built-in-roles.md#storage-blob-data-contributor) for the user "HPC Cache Resource Provider".
112
112
@@ -303,7 +303,7 @@ Output:
303
303
304
304
## View storage targets
305
305
306
-
You can use the Azure portal or the Azure CLI to show the storage targets already defined for your cache.
306
+
You can use the Azure portal or the Azure CLI to show the storage targets already defined for your cache.
Copy file name to clipboardExpand all lines: articles/hpc-cache/hpc-cache-create.md
+2-2Lines changed: 2 additions & 2 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 create an Azure HPC Cache instance
4
4
author: ekpgh
5
5
ms.service: hpc-cache
6
6
ms.topic: how-to
7
-
ms.date: 07/10/2020
7
+
ms.date: 09/30/2020
8
8
ms.author: v-erkel
9
9
---
10
10
@@ -24,7 +24,7 @@ Click the image below to watch a [video demonstration](https://azure.microsoft.c
24
24
25
25

26
26
27
-
In **Project Details**, select the subscription and resource group that will host the cache. Make sure the subscription is on the [access](hpc-cache-prerequisites.md#azure-subscription) list.
27
+
In **Project Details**, select the subscription and resource group that will host the cache.
28
28
29
29
In **Service Details**, set the cache name and these other attributes:
Copy file name to clipboardExpand all lines: articles/hpc-cache/hpc-cache-overview.md
-6Lines changed: 0 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,12 +60,6 @@ The [customer-managed keys feature](customer-keys.md) is supported only in these
60
60
* US Gov Arizona
61
61
* US Gov Virginia
62
62
63
-
<!-- ## Service availability
64
-
65
-
You must request access for each subscription you will use with Azure HPC Cache. This restriction helps ensure service quality.
66
-
67
-
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 caches. -->
68
-
69
63
## Next steps
70
64
71
65
* Read the [Azure HPC Cache product page](https://azure.microsoft.com/services/hpc-cache) to learn more about its capabilities
Copy file name to clipboardExpand all lines: articles/hpc-cache/hpc-cache-prerequisites.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,9 +31,6 @@ Read the rest of this article for specific recommendations.
31
31
## Azure subscription
32
32
33
33
A paid subscription is recommended.
34
-
<!--
35
-
> [!NOTE]
36
-
> The Azure HPC Cache team must add your subscription to the access list before it can be used to create a cache instance. This procedure helps ensure that each customer gets high-quality responsiveness from their caches. Fill out [this form](https://aka.ms/onboard-hpc-cache) to request access. -->
0 commit comments