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 5d1eb29

Browse files
ekpghekpgh
committedSep 29, 2020
document updated GUI
1 parent 36b3a84 commit 5d1eb29

17 files changed

+355
-133
lines changed
 

‎articles/hpc-cache/add-namespace-paths.md

Lines changed: 144 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,144 @@
1+
---
2+
title: Configure the Azure HPC Cache aggregated namespace
3+
description: How to create client-facing paths for back-end storage with Azure HPC Cache
4+
author: ekpgh
5+
ms.service: hpc-cache
6+
ms.topic: how-to
7+
ms.date: 08/19/2020
8+
ms.author: v-erkel
9+
---
10+
11+
# Set up the aggregated namespace
12+
13+
After you create storage targets, you must also create namespace paths for them. Client machines use these virtual paths to access files through the cache instead of connecting to the back-end storage directly. This system lets cache administrators change back-end storage systems without having to rewrite client instructions.
14+
15+
Read [Plan the aggregated namespace](hpc-cache-namespace.md) to learn more about this feature.
16+
17+
The **Namespace** page in the Azure portal shows the paths that clients use to access your data through the cache. Use this page to create, remove, or change namespace paths. You also can configure namespace paths by using the Azure CLI.
18+
19+
All of the existing client-facing paths are listed on the **Namespace** page. If a storage target does not have any paths, it does not appear in the table.
20+
21+
You can sort the table columns by clicking the arrows and better understand your cache's aggregated namespace.
22+
23+
![screenshot of portal namespace page with two paths in a table. Column headers: Namespace path, Storage target, Export path, and Export subdirectory. The items in the first column are clickable links. Top buttons: Add namespace path, refresh, delete](media/namespace-page.png)
24+
25+
## Add or edit client-facing namespace paths
26+
27+
You must create at least one namespace path before clients can access the storage target. (Read [Mount the Azure HPC Cache](hpc-cache-mount.md) for more about client access.)
28+
29+
### Blob namespace paths
30+
31+
An Azure Blob storage target can have only one namespace path.
32+
33+
Follow the instructions below to set or change the path with the Azure Portal or Azure CLI.
34+
35+
### [Portal](#tab/azure-portal)
36+
37+
From the Azure portal, load the **Namespace** settings page. You can add, change, or delete namespace paths from this page.
38+
39+
* **Add a new path:** Click the **+ Add** button at the top and fill in information in the edit panel.
40+
41+
* Select the storage target from the drop-down list. (In this screenshot, the blob storage target can't be selected because it already has a namespace path.)
42+
43+
![Screenshot of the new namespace edit fields with the storage target selector exposed](media/namespace-select-storage-target.png)
44+
45+
* For an Azure Blob storage target, the export and subdirectory paths are automatically set to ``/``.
46+
47+
* **Change an existing path:** Click the namespace path. The edit panel opens and you can modify the path.
48+
49+
![Screenshot of the namespace page after clicking on a Blob namespace path - the edit fields appear on a pane to the right](media/edit-namespace-blob.png)
50+
51+
* **Delete a namespace path:** Select the checkbox to the left of the path and click the **Delete** button.
52+
53+
### [Azure CLI](#tab/azure-cli)
54+
55+
[!INCLUDE [cli-reminder.md](includes/cli-reminder.md)]
56+
57+
When using the Azure CLI, you must add a namespace path when you create the storage target. Read [Add a new Azure Blob storage target](hpc-cache-add-storage.md?tabs=azure-cli#add-a-new-azure-blob-storage-target) for details.
58+
59+
To update the target's namespace path, use the [az hpc-cache blob-storage-target update](/cli/azure/ext/hpc-cache/hpc-cache/blob-storage-target#ext-hpc-cache-az-hpc-cache-blob-storage-target-update) command. The arguments for the update command are similar to the arguments in the create command, except that you do not pass the container name or storage account.
60+
61+
You cannot delete a namespace path from a blob storage target with the Azure CLI, but you can overwrite the path with a different value.
62+
63+
---
64+
65+
### NFS namespace paths
66+
67+
An NFS storage target can have multiple virtual paths, as long as each path represents a different export or subdirectory on the same storage system.
68+
69+
When planning your namespace for an NFS storage target, keep in mind that each path must be unique, and can't be a subdirectory of another namespace path. For example, if you have a namespace path that is called ``/parent-a``, you can't also create namespace paths like ``/parent-a/user1`` and ``/parent-a/user2``. Those directory paths are already accessible in the namespace as subdirectories of ``/parent-a``.
70+
71+
All of the namespace paths for an NFS storage system are created on one storage target. Most cache configurations can support up to ten namespace paths per storage target, but larger configurations can support up to 20.
72+
73+
<!-- | Throughput value | Cache size | Maximum number of namespace paths per storage target |
74+
|------------------|------------|------------------------------------------------------|
75+
| Up to 2 GB/s | 3 TB | 10 |
76+
| Up to 2 GB/s | 6 TB | 10 |
77+
| Up to 2 GB/s | 12 TB | 20 |
78+
| Up to 4 GB/s | 6 TB | 10 |
79+
| Up to 4 GB/s | 12 TB | 10 |
80+
| Up to 4 GB/s | 24 TB | 20 |
81+
| Up to 8 GB/s | 12 TB | 10 |
82+
| Up to 8 GB/s | 24 TB | 10 |
83+
| Up to 8 GB/s | 48 TB | 20 | -->
84+
85+
This list shows the maximum number of namespace paths per configuration.
86+
87+
* Up to 2 GB/s throughput:
88+
89+
* 3 TB cache - 10 namespace paths
90+
* 6 TB cache - 10 namespace paths
91+
* 23 TB cache - 20 namespace paths
92+
93+
* Up to 5 GB/s throughput:
94+
95+
* 6 TB cache - 10 namespace paths
96+
* 12 TB cache - 10 namespace paths
97+
* 24 TB cache -20 namespace paths
98+
99+
* Up to 8 GB/s throughput:
100+
101+
* 12 TB cache - 10 namespace paths
102+
* 24 TB cache - 10 namespace paths
103+
* 48 TB cache - 20 namespace paths
104+
105+
For each NFS namespace path, provide the client-facing path, the storage system export, and optionally an export subdirectory.
106+
107+
### [Portal](#tab/azure-portal)
108+
109+
From the Azure portal, load the **Namespace** settings page. You can add, edit, or delete namespace paths from this page.
110+
111+
* **To add a new path:** Click the **+ Add** button at the top and fill in information in the edit panel.
112+
* **To change an existing path:** Click the namespace path. The edit panel opens and you can modify the path.
113+
* **To delete a namespace path:** Select the checkbox to the left of the path and click the **Delete** button.
114+
115+
Fill in these values for each namespace path:
116+
117+
* **Namespace path** - The client-facing file path.
118+
119+
* **Storage target** - If creating a new namespace path, select a storage target from the drop-down menu.
120+
121+
* **Export path** - Enter the path to the NFS export. Make sure to type the export name correctly - the portal validates the syntax for this field but does not check the export until you submit the change.
122+
123+
* **Export subdirectory** - If you want this path to mount a specific subdirectory of the export, enter it here. If not, leave this field blank.
124+
125+
![screenshot of the portal namespace page with the update page open at the right](media/update-namespace-nfs.png)
126+
127+
### [Azure CLI](#tab/azure-cli)
128+
129+
[!INCLUDE [cli-reminder.md](includes/cli-reminder.md)]
130+
131+
When using the Azure CLI, you must add at least one namespace path when you create the storage target. Read [Add a new NFS storage target](hpc-cache-add-storage.md?tabs=azure-cli#add-a-new-nfs-storage-target) for details.
132+
133+
To update the target's namespace path or to add additional paths, use the [az hpc-cache nfs-storage-target update](/cli/azure/ext/hpc-cache/hpc-cache/nfs-storage-target#ext-hpc-cache-az-hpc-cache-nfs-storage-target-update) command. Use the ``--junction`` option to specify all of the namespace paths you want.
134+
135+
The options used for the update command are similar to the "create" command, except that you do not pass the storage system information (IP address or hostname), and the usage model is optional. Read [Add a new NFS storage target](hpc-cache-add-storage.md?tabs=azure-cli#add-a-new-nfs-storage-target) for more details about the syntax of the ``--junction`` option.
136+
137+
---
138+
139+
## Next steps
140+
141+
After creating the aggregated namespace for your storage targets, you can mount clients on the cache. Read these articles to learn more.
142+
143+
* [Mount the Azure HPC Cache](hpc-cache-mount.md)
144+
* [Move data to Azure Blob storage](hpc-cache-ingest.md)

0 commit comments

Comments
 (0)
Please sign in to comment.