Skip to content

Commit 04f94d6

Browse files
committed
hpc-cache: update mount description
1 parent 0d88d7a commit 04f94d6

File tree

1 file changed

+13
-9
lines changed

1 file changed

+13
-9
lines changed

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

Lines changed: 13 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ 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: 03/30/2020
7+
ms.date: 04/01/2020
88
ms.author: rohogue
99
---
1010

@@ -19,15 +19,15 @@ The mount command is made up of these elements:
1919
* The local path to use on the client
2020
* Command parameters that optimize the success of this kind of NFS mount
2121

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.
2323

2424
## Prepare clients
2525

2626
Make sure your clients are able to mount the Azure HPC Cache by following the guidelines in this section.
2727

2828
### Provide network access
2929

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.
3131

3232
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.)
3333

@@ -42,7 +42,7 @@ Install the appropriate Linux utility software to support the NFS mount command:
4242

4343
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.
4444

45-
Example: `sudo mkdir hpc-cache-1\target3`
45+
Example: `sudo mkdir /mnt/hpc-cache-1/target3`
4646

4747
## Use the mount instructions utility
4848

@@ -54,19 +54,23 @@ The mount command page includes information about the client mount process and p
5454

5555
To use this page, follow this procedure:
5656

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).
5858

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.
6060
6161
* 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.
6367

6468
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.
6569

6670
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.
6771

6872
> [!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.
7074
7175
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.
7276

@@ -80,7 +84,7 @@ Example:
8084

8185
```bash
8286
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
8488
root@test-client:/tmp#
8589
```
8690

0 commit comments

Comments
 (0)