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-mount.md
+13-9Lines changed: 13 additions & 9 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 connect clients to an Azure HPC Cache service
4
4
author: ekpgh
5
5
ms.service: hpc-cache
6
6
ms.topic: conceptual
7
-
ms.date: 03/30/2020
7
+
ms.date: 04/01/2020
8
8
ms.author: rohogue
9
9
---
10
10
@@ -19,15 +19,15 @@ The mount command is made up of these elements:
19
19
* The local path to use on the client
20
20
* Command parameters that optimize the success of this kind of NFS mount
21
21
22
-
The **Mount instructions** page for your cache collects the information and the recommended options for you, and creates a proptype mount command that you can copy. Read [Use the mount instructions](#use-the-mount-instructions-utility), below, for details.
22
+
The **Mount instructions** page for your cache collects the information and the recommended options for you, and creates a prototype mount command that you can copy. Read [Use the mount instructions utility](#use-the-mount-instructions-utility), below, for details.
23
23
24
24
## Prepare clients
25
25
26
26
Make sure your clients are able to mount the Azure HPC Cache by following the guidelines in this section.
27
27
28
28
### Provide network access
29
29
30
-
The client machines must have SSL access to the cache's virtual network and private subnet.
30
+
The client machines must have network access to the cache's virtual network and private subnet.
31
31
32
32
For example, create client VMs within the same virtual network, or use an endpoint, gateway, or other solution in the virtual network for access from outside. (Remember that nothing other than the cache itself can be hosted inside the cache's subnet.)
33
33
@@ -42,7 +42,7 @@ Install the appropriate Linux utility software to support the NFS mount command:
42
42
43
43
Create a local directory path on each client to connect to the cache. Create a path for each storage target that you want to mount.
44
44
45
-
Example: `sudo mkdir hpc-cache-1\target3`
45
+
Example: `sudo mkdir /mnt/hpc-cache-1/target3`
46
46
47
47
## Use the mount instructions utility
48
48
@@ -54,19 +54,23 @@ The mount command page includes information about the client mount process and p
54
54
55
55
To use this page, follow this procedure:
56
56
57
-
1.The first section reviews the steps required for client systems before they can mount the cache. Check the network access prerequisites and install the utilities needed to use the NFS `mount` command as described above in [Prepare clients](#prepare-clients).
57
+
1.Review the client prerequisites and install the utilities needed to use the NFS `mount` command as described above in [Prepare clients](#prepare-clients).
58
58
59
-
1. In step one of **Mounting your file system**<!-- label will change -->, enter the path that the client will use to access the Azure HPC Cache storage target.
59
+
<!--1. In step one of **Mounting your file system**, enter the path that the client will use to access the Azure HPC Cache storage target.
60
60
61
61
* This path is local to the client.
62
-
* After you provide the directory name, the field populates with a command you can copy. Use this command on the client directly or in a setup script to create the directory path on the client VM.
62
+
* After you provide the directory name, the field populates with a command you can copy. Use this command on the client directly or in a setup script to create the directory path on the client VM. -->
63
+
64
+
1. Step one of **Mounting your file system**<!-- label will change --> gives an example command for creating the local path on the client. This is the path that the client will use to access the content from the Azure HPC Cache.
65
+
66
+
Note the path name so that you can modify it in the command if needed.
63
67
64
68
1. In step two, select one of the available IP addresses. All of the cache's [client mount points](#find-mount-command-components) are listed here.
65
69
66
70
1. The field in step three automatically populates with a prototype mount command. Click the copy symbol at the right side of the field to automatically copy it to your clipboard.
67
71
68
72
> [!NOTE]
69
-
> Check the copy command before using it. You might need to customize the storage target path, which is not yet selectable in this interface. You also should update the mount command options to reflect the [recommended options](#mount-command-options) below. Read [Understand mount command syntax](#understand-mount-command-syntax) for help.
73
+
> Check the copy command before using it. You might need to customize the client mount path and the storage target virtual namespace path, which are not yet selectable in this interface. You also should update the mount command options to reflect the [recommended options](#mount-command-options) below. Read [Understand mount command syntax](#understand-mount-command-syntax) for help.
70
74
71
75
1. Use the copied mount command (with edits, if needed) on the client machine to connect it to the storage target on 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.
72
76
@@ -80,7 +84,7 @@ Example:
80
84
81
85
```bash
82
86
root@test-client:/tmp# mkdir hpccache
83
-
root@test-client:/tmp# sudo mount 10.0.0.28:/blob-demo-0722 ./hpccache/ -orw,tcp,mountproto=tcp,vers3,hard
87
+
root@test-client:/tmp# sudo mount 10.0.0.28:/blob-demo-0722 ./hpccache/ -o hard,proto=tcp,mountproto=tcp,retry=30
0 commit comments