Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit d719a54

Browse files
committedApr 14, 2020
update screenshots
1 parent 0c404f1 commit d719a54

File tree

6 files changed

+14
-4
lines changed

6 files changed

+14
-4
lines changed
 

‎articles/hpc-cache/hpc-cache-mount.md

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ description: How to connect clients to an Azure HPC Cache service
44
author: ekpgh
55
ms.service: hpc-cache
66
ms.topic: conceptual
7-
ms.date: 04/09/2020
8-
ms.author: rohogue
7+
ms.date: 04/14/2020
8+
ms.author: v-erkel
99
---
1010

1111
# Mount the Azure HPC Cache
@@ -58,16 +58,24 @@ Before using the command on a client, make sure the client meets the prerequisit
5858

5959
Follow this procedure to create the mount command.
6060

61-
1. Customize the **Client path** field. This field gives an example command that you can use to create a local path on the client. This is the path that the client will use to access the content from the Azure HPC Cache.
61+
1. Customize the **Client path** field. This field gives an example command that you can use to create a local path on the client. The client accesses the content from the Azure HPC Cache locally in this directory.
6262

63-
Edit the command to contain the directory name you want. The name appears at the end of the string after `sudo mkdir -p`
63+
Click the field and edit the command to contain the directory name you want. The name appears at the end of the string after `sudo mkdir -p`
64+
65+
![screenshot of the client path field with cursor positioned at the end](media/mount-edit-client.png)
66+
67+
After you finish editing the field, the mount command at the bottom of the page updates with the new client path.
6468

6569
1. Choose the **Cache mount address** from the list. This menu lists all of the cache's [client mount points](#find-mount-command-components).
6670

6771
Balance client load across all of the available mount addresses for better cache performance.
6872

73+
![screenshot of the cache mount address field, with selector showing three IP addresses to choose from](media/mount-select-ip.png)
74+
6975
1. Choose the **Virtual namespace path** to use for the client. These paths link to exports on the back-end storage system.
7076

77+
![screenshot of the namespace paths field, with selector open](media/mount-select-target.png)
78+
7179
You can view and change virtual namespace paths on the Storage targets portal page. Read [Add storage targets](hpc-cache-add-storage.md) to see how.
7280

7381
To learn more about Azure HPC Cache's aggregated namespace feature, read [Plan the aggregated namespace](hpc-cache-namespace.md).
@@ -76,6 +84,8 @@ Follow this procedure to create the mount command.
7684

7785
Click the copy symbol at the right side of the field to automatically copy it to your clipboard.
7886

87+
![screenshot of the namespace paths field, with selector open](media/mount-command-copy.png)
88+
7989
1. Use the copied mount command on the client machine to connect it to the Azure HPC Cache. You can issue the command directly from the client command line, or include the mount command in a client setup script or template.
8090

8191
## Understand mount command syntax
47.5 KB
Loading
12.4 KB
Loading
27.9 KB
Loading
38.1 KB
Loading
47.7 KB
Loading

0 commit comments

Comments
 (0)
Please sign in to comment.