Skip to content

Commit 300bd71

Browse files
committedDec 22, 2020
new screenshots for access policies
1 parent 8cec225 commit 300bd71

File tree

5 files changed

+6
-8
lines changed

5 files changed

+6
-8
lines changed
 

‎articles/hpc-cache/access-policies.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: How to create and apply custom access policies to limit client acce
44
author: ekpgh
55
ms.service: hpc-cache
66
ms.topic: how-to
7-
ms.date: 12/17/2020
7+
ms.date: 12/22/2020
88
ms.author: v-erkel
99
---
1010

@@ -24,14 +24,14 @@ If you don't need fine-grained control over storage target access, you can use t
2424

2525
Use the **Client access policies** page in the Azure portal to create and manage policies. <!-- is there AZ CLI for this? -->
2626

27-
<!-- ![screenshot of client access policies page. Several policies are defined, and some are expanded to show their rules](media/policies-overview-draft.png) -->
28-
29-
[ ![screenshot of client access policies page. Several policies are defined, and some are expanded to show their rules](media/policies-overview-draft.png)](media/policies-overview-draft.png#lightbox)
27+
[![screenshot of client access policies page. Several policies are defined, and some are expanded to show their rules](media/policies-overview.png)](media/policies-overview.png#lightbox)
3028

3129
Each policy is made up of rules. The rules are applied to hosts in order from the smallest scope (host) to the largest (default). The first rule that matches is applied and later rules are ignored.
3230

3331
To create a new access policy, click the **+ Add access policy** button at the top of the list. Give the new access policy a name, and enter at least one rule.
3432

33+
![screenshot of access policies edit blade with multiple rules filled in. Click ok to save the rule.](media/add-policy.png)
34+
3535
The rest of this section explains the values you can use in rules.
3636

3737
### Scope
@@ -60,11 +60,11 @@ Specify the IP address or range of addresses for this rule. Use CIDR notation (e
6060

6161
Set what privileges to grant the clients that match the scope and filter.
6262

63-
Options are read/write, read-only, or none.
63+
Options are **read/write**, **read-only**, or **no access**.
6464

6565
### SUID
6666

67-
Check the SUID box to allow files in storage to set user IDs upon access.
67+
Check the **SUID** box to allow files in storage to set user IDs upon access.
6868

6969
SUID typically is used to increase a user’s privileges temporarily so that the user can accomplish a task related to that file.
7070

@@ -86,8 +86,6 @@ If you turn on root squash, you must also set the anonymous ID user value to one
8686
* **65535** (no access)
8787
* **0** (unprivileged root)
8888

89-
![screenshot of access policies edit blade with multiple rules filled in. Click ok to save the rule.](media/add-policy-draft.png)
90-
9189
## Next steps
9290

9391
* Apply access policies in the namespace paths for your storage targets. Read [Set up the aggregated namespace](add-namespace-paths.md) to learn how.
-149 KB
Binary file not shown.
171 KB
Loading
Binary file not shown.
225 KB
Loading

0 commit comments

Comments
 (0)
Please sign in to comment.