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 4f89a98

Browse files
committedDec 30, 2019
HPC cache: add ability to create containers from storage target UI
1 parent 12804f5 commit 4f89a98

File tree

6 files changed

+10
-6
lines changed

6 files changed

+10
-6
lines changed
 

‎articles/hpc-cache/hpc-cache-add-storage.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: How to define storage targets so that your Azure HPC Cache can use
44
author: ekpgh
55
ms.service: hpc-cache
66
ms.topic: conceptual
7-
ms.date: 11/18/2019
7+
ms.date: 12/30/2019
88
ms.author: rohogue
99
---
1010

@@ -28,6 +28,8 @@ From the Azure portal, open your cache instance and click **Storage targets** on
2828

2929
A new Blob storage target needs an empty Blob container or a container that is populated with data in the Azure HPC Cache cloud file system format. Read more about pre-loading a Blob container in [Move data to Azure Blob storage](hpc-cache-ingest.md).
3030

31+
You can create a new container from this page just before adding it.
32+
3133
To define an Azure Blob container, enter this information.
3234

3335
![screenshot of the add storage target page, populated with information for a new Azure Blob storage target](media/hpc-cache-add-blob.png)
@@ -36,13 +38,15 @@ To define an Azure Blob container, enter this information.
3638

3739
* **Storage target name** - Set a name that identifies this storage target in the Azure HPC Cache.
3840
* **Target type** - Choose **Blob**.
39-
* **Storage account** - Select the account with the container that you want to use.
41+
* **Storage account** - Select the account that you want to use.
4042

4143
You will need to authorize the cache instance to access the storage account as described in [Add the access roles](#add-the-access-control-roles-to-your-account).
4244

4345
For information about the kind of storage account you can use, read [Blob storage requirements](hpc-cache-prereqs.md#blob-storage-requirements).
4446

45-
* **Storage container** - Select the Blob container for this target.
47+
* **Storage container** - Select the Blob container for this target, or click **Create new**.
48+
49+
![screenshot of dialog to specify name and access level (private) for new container](media/add-blob-new-container.png)
4650

4751
* **Virtual namespace path** - Set the client-facing file path for this storage target. Read [Configure aggregated namespace](hpc-cache-namespace.md) to learn more about the virtual namespace feature.
4852

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ In **Service Details**, set the cache name and these other attributes:
3131

3232
On the **Cache** page, you must set the capacity of your cache. The values set here determine how much data your cache can hold and how quickly it can service client requests.
3333

34-
After the public preview period, capacity also will affect the cache's cost.
34+
Capacity also affects the cache's cost.
3535

3636
Choose the capacity by setting these two values:
3737

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This article explains the best ways to move data to Blob storage for use with Az
1616

1717
Keep these facts in mind:
1818

19-
* Azure HPC Cache uses a specialized storage format to organize data in Blob storage. This is why a Blob storage target must either be a new, empty container, or a Blob container that was previously used for Azure HPC Cache data. ([Avere vFXT for Azure](https://azure.microsoft.com/services/storage/avere-vfxt/) also uses this cloud file system.)
19+
* Azure HPC Cache uses a specialized storage format to organize data in Blob storage. This is why a Blob storage target must either be a new, empty container, or a Blob container that was previously used for Azure HPC Cache data. <!--([Avere vFXT for Azure](https://azure.microsoft.com/services/storage/avere-vfxt/) also uses this cloud file system.)-->
2020

2121
* Copying data through the Azure HPC Cache to a back-end storage target is more efficient when you use multiple clients and parallel operations. A simple copy command from one client will move data slowly.
2222

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ NFS back-end storage must be a compatible hardware/software platform. Contact th
7575

7676
If you want to use Azure Blob storage with your cache, you need a compatible storage account and either an empty Blob container or a container that is populated with Azure HPC Cache formatted data as described in [Move data to Azure Blob storage](hpc-cache-ingest.md).
7777

78-
Create the account and container before attempting to add it as a storage target.
78+
Create the account before attempting to add a storage target. You can create a new container when you add the target.
7979

8080
To create a compatible storage account, use these settings:
8181

Loading
Loading

0 commit comments

Comments
 (0)
Please sign in to comment.