add storage target manage actions article

Author: ekpgh

articles/hpc-cache/cache-usage-models.md

@@ -7,6 +7,7 @@ ms.topic: how-to
 ms.date: 06/17/2021
 ms.author: v-erkel
 ---
+<!-- filename is referenced from GUI in aka.ms/hpc-cache-usagemodel -->
 
 # Understand cache usage models
 

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

@@ -4,7 +4,7 @@ description: How to define storage targets so that your Azure HPC Cache can use
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: how-to
-ms.date: 06/23/2021
+ms.date: 06/24/2021
 ms.custom: subject-rbac-steps
 ms.author: v-erkel
 ---
@@ -91,7 +91,7 @@ Azure HPC Cache uses [Azure role-based access control (Azure RBAC)](../role-base
 
 The storage account owner must explicitly add the roles [Storage Account Contributor](../role-based-access-control/built-in-roles.md#storage-account-contributor) and [Storage Blob Data Contributor](../role-based-access-control/built-in-roles.md#storage-blob-data-contributor) for the user "HPC Cache Resource Provider".
 
-You can do this ahead of time, or by clicking a link on the page where you add a Blob storage target. Keep in mind that it can take up to five minutes for the role settings to propagate through the Azure environment, so you should wait a few minutes after adding the roles before creating a storage target.
+You can do this ahead of time, or by clicking a link on the portal page where you add a Blob storage target. Keep in mind that it can take up to five minutes for the role settings to propagate through the Azure environment, so you should wait a few minutes after adding the roles before creating a storage target.
 
 1. Open **Access control (IAM)** for your storage account.
 
@@ -107,7 +107,7 @@ You can do this ahead of time, or by clicking a link on the page where you add a
     ![Add role assignment page](../../includes/role-based-access-control/media/add-role-assignment-page.png)
 
    > [!NOTE]
-   > If you can't find the HPC Cache Resource Provider, try a search for the string "storagecache" instead. Users who participated in HPC Cache previews (before GA) might need to use the older name for the service principal.
+   > If you can't find the HPC Cache Resource Provider, try a search for the string "storagecache" instead. This was a pre-GA name for the service principal.
 
 <!-- 
 Steps to add the Azure roles:
@@ -184,25 +184,23 @@ az hpc-cache blob-storage-target add --resource-group "hpc-cache-group" \
 
 ## Add a new NFS storage target
 
-An NFS storage target has different settings from a Blob storage target. The usage model setting helps the cache to efficiently cache data from this storage system.
+An NFS storage target has different settings from a Blob storage target, including a usage model setting, which tells the cache how to store data from this storage system.
 
 ![Screenshot of add storage target page with NFS target defined](media/add-nfs-target.png)
 
 > [!NOTE]
 > Before you create an NFS storage target, make sure your storage system is accessible from the Azure HPC Cache and meets permission requirements. Storage target creation will fail if the cache can't access the storage system. Read [NFS storage requirements](hpc-cache-prerequisites.md#nfs-storage-requirements) and [Troubleshoot NAS configuration and NFS storage target issues](troubleshoot-nas.md) for details.
 
 ### Choose a usage model
-<!-- referenced from GUI by aka.ms link -->
 
 When you create a storage target that uses NFS to reach its storage system, you need to choose a usage model for that target. This model determines how your data is cached.
 
 Read [Understand usage models](cache-usage-models.md) for more details about all of these settings.
 
 The built-in usage models let you choose how to balance fast response with the risk of getting stale data. If you want to optimize speed for reading files, you might not care whether the files in the cache are checked against the back-end files. On the other hand, if you want to make sure your files are always up to date with the remote storage, choose a model that checks frequently.
 
-<!-- asc12 add restriction on L series: -->
 > [!NOTE]
-> L Series storage caches support read caching only so you can't choose those write models (write this better)
+> [High-throughput style caches](hpc-cache-create.md#choose-the-cache-type-for-your-needs) support read caching only.
 
 These three options cover most situations:
 
@@ -251,7 +249,7 @@ Provide this information for an NFS-backed storage target:
 
 * **Target type** - Choose **NFS**.
 
-* **Hostname** - Enter the IP address or fully qualified domain name for your NFS storage system. (Use a domain name only if your cache has access to a DNS server that can resolve the name.)
+* **Hostname** - Enter the IP address or fully qualified domain name for your NFS storage system. (Use a domain name only if your cache has access to a DNS server that can resolve the name.) You can enter multiple IP addresses if your storage system is referenced by multiple IPs.
 
 * **Usage model** - Choose one of the data caching profiles based on your workflow, described in [Choose a usage model](#choose-a-usage-model) above.
 
@@ -342,7 +340,9 @@ ADLS-NFS storage targets have some similarities with Blob storage targets and so
 
 * Like a Blob storage target, you need to give Azure HPC Cache permission to [access your storage account](#add-the-access-control-roles-to-your-account).
 * Like an NFS storage target, you need to set a cache [usage model](#choose-a-usage-model).
-* Because NFS-enabled blob containers have an NFS-compatible hierarchical structure, you do not need to use the cache to ingest data, and the containers are readable by other NFS systems. You can pre-load data in an ADLS-NFS container, then add it to an HPC Cache as a storage target, and then access the data later from outside of an HPC Cache. When you use a standard blob container as an HPC Cache storage target, the data is written in a proprietary format and can only be accessed from other Azure HPC Cache-compatible products.
+* Because NFS-enabled blob containers have an NFS-compatible hierarchical structure, you do not need to use the cache to ingest data, and the containers are readable by other NFS systems.
+
+  You can pre-load data in an ADLS-NFS container, then add it to an HPC Cache as a storage target, and then access the data later from outside of an HPC Cache. When you use a standard blob container as an HPC Cache storage target, the data is written in a proprietary format and can only be accessed from other Azure HPC Cache-compatible products.
 
 Before you can create an ADLS-NFS storage target, you must create an NFS-enabled storage account. Follow the tips in [Prerequisites for Azure HPC Cache](hpc-cache-prerequisites.md#nfs-mounted-blob-adls-nfs-storage-requirements-preview) and the instructions in [Mount Blob storage by using NFS](../storage/blobs/network-file-system-protocol-support-how-to.md). After your storage account is set up you can create a new container when you create the storage target.
 

articles/hpc-cache/hpc-cache-edit-storage.md

@@ -4,15 +4,15 @@ description: How to edit Azure HPC Cache storage targets
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: how-to
-ms.date: 03/29/2021
+ms.date: 06/24/2021
 ms.author: v-erkel
 ---
 
 # Edit storage targets
 
-You can modify, manage, or remove storage targets with the Azure portal or by using the Azure CLI.
+You can modify storage targets with the Azure portal or by using the Azure CLI. For example, you can change access policies, usage models, and namespace paths for an existing storage target.
 
-The xxx 
+Storage target *management* tasks, like suspending or deleting a storage target, are described in [Manage storage targets](manage-storage-targets.md).
 
 Depending on the type of storage, you can modify these storage target values:
 
@@ -27,40 +27,11 @@ Depending on the type of storage, you can modify these storage target values:
 
 * For ADLS-NFS storage targets, you can change the namespace path, access policy, and the usage model.
 
-You can't edit a storage target's name, type, or back-end storage system (Blob container or NFS hostname/IP address). If you need to change these properties, delete the storage target and create a replacement with the new value.
+You can't edit a storage target's name, type, or back-end storage system. If you need to change these properties, delete the storage target and create a replacement with the new value.
 
 > [!TIP]
 > The [Managing Azure HPC Cache video](https://azure.microsoft.com/resources/videos/managing-hpc-cache/) shows how to edit a storage target in the Azure portal.
 
-## Remove a storage target
-
-### [Portal](#tab/azure-portal)
-
-To remove a storage target, open the **Storage targets** page. Click the '...' next to the storage target and choose **Delete** from the menu. The other options on this menu are explained in [Manage storage targets](#manage-storage-targets).
-
-### [Azure CLI](#tab/azure-cli)
-
-[Set up Azure CLI for Azure HPC Cache](./az-cli-prerequisites.md).
-
-Use [az hpc-cache storage-target remove](/cli/azure/hpc-cache/storage-target#az_hpc_cache_storage_target_remove) to delete a storage target from the cache.
-
-```azurecli
-$ az hpc-cache storage-target remove --resource-group cache-rg --cache-name doc-cache0629 --name blob1
-
-{- Finished ..
-  "endTime": "2020-07-09T21:45:06.1631571+00:00",
-  "name": "2f95eac1-aded-4860-b19c-3f089531a7ec",
-  "startTime": "2020-07-09T21:43:38.5461495+00:00",
-  "status": "Succeeded"
-}
-```
-
----
-
-Deleting a storage target removes the storage system's association with this Azure HPC Cache system, but it does not change the back-end storage system. For example, if you used an Azure Blob storage container, the container and its contents still exist after you delete it from the cache. You can add the container to a different Azure HPC Cache, re-add it to this cache, or delete it with the Azure portal.
-
-Any file changes stored in the cache are written to the back-end storage system before the storage target is removed. This process can take an hour or more if a lot of changed data is in the cache.
-
 ## Change a blob storage target's namespace path
 
 Namespace paths are the paths that clients use to mount this storage target. (To learn more, read [Plan the aggregated namespace](hpc-cache-namespace.md) and [Set up the aggregated namespace](add-namespace-paths.md)).
@@ -211,34 +182,8 @@ Use the **Namespace** page for your Azure HPC Cache to update namespace values.
 
 The configuration for ADLS-NFS usage models is identical to the NFS usage model selection. Read the portal instructions in [Change the usage model](#change-the-usage-model) in the NFS section above. Additional tools for updating ADLS-NFS storage targets are in development.
 
-
-## Manage storage targets
-
-You can also perform management actions on individual storage targets. These actions supplement the cache-level management options discussed in [Manage your cache](hpc-cache-manage.md).
-
-Sometimes an individual storage target can get into a bad state and need to be temporarily removed, or permanently deleted. You also can flush cached data for a specific target.
-
-![Screenshot of the storage targets page in the Azure portal, with the cursor over the menu exposed by clicking on the three dots (...) symbol to the far right of the storage target's row in the list.](media/storage-target-manage-options.png)
-
-* Flush
-* Suspend
-* Force remove
-* Resume
-* Delete
-
-### Flush cached files to the storage target
-
-### Suspend a storage target
-
-The suspend feature disables client access to a storage target, but doesn't permanently remove the storage target from your cache. You can use this option if you need to disable a back-end storage system for maintenance, repair, or replacement.  <!-- https://msazure.visualstudio.com/One/_workitems/edit/5301521 -->
-
-### Force remove a storage target
-<!-- https://msazure.visualstudio.com/One/_workitems/edit/8267141 -->
-
-Delete 
-
-
 ## Next steps
 
-* Read [Add storage targets](hpc-cache-add-storage.md) to learn more about these options.
+* Read [Manage storage targets](manage-storage-targets.md) for information about stopping, deleting, and flushing individual storage targets.
+* Read [Add storage targets](hpc-cache-add-storage.md) to learn more about storage target options.
 * Read [Plan the aggregated namespace](hpc-cache-namespace.md) for more tips about using virtual paths.

articles/hpc-cache/hpc-cache-manage.md

@@ -29,6 +29,9 @@ The buttons at the top of the page can help you manage the cache:
 
 Read more about these options below.
 
+> [!TIP]
+> You can also manage individual storage targets - read [Manage storage targets](manage-storage-targets.md) for details.
+
 Click the image below to watch a [video](https://azure.microsoft.com/resources/videos/managing-hpc-cache/) that demonstrates cache management tasks.
 
 [![video thumbnail: Azure HPC Cache: Manage (click to visit the video page)](media/video-5-manage.png)](https://azure.microsoft.com/resources/videos/managing-hpc-cache/)

articles/hpc-cache/manage-storage-targets.md

@@ -0,0 +1,101 @@
+---
+title: Manage Azure HPC Cache storage targets
+description: How to suspend, remove, force delete, and flush Azure HPC Cache storage targets
+author: ekpgh
+ms.service: hpc-cache
+ms.topic: how-to
+ms.date: 06/24/2021
+ms.author: v-erkel
+---
+
+# Manage storage targets
+
+You can perform management actions on individual storage targets. These actions supplement the cache-level options discussed in [Manage your cache](hpc-cache-manage.md).
+
+Sometimes an individual storage target can get into a bad state and need to be temporarily removed, or permanently deleted. You also can save cached data for a specific target.
+
+Open the **Storage targets** page in the Azure portal. Click the **...** text on the far right of the storage target list to open the list of tasks.
+
+![Screenshot of the storage targets page in the Azure portal, with the cursor over the menu exposed by clicking on the three dots (...) symbol to the far right of the storage target's row in the list.](media/storage-target-manage-options.png)
+
+These options are available:
+
+* **Flush** - Write all cached changes to the back-end storage
+* **Suspend** - Temporarily stop the storage target from serving requests
+* **Resume** - Put a suspended storage target back into service
+* **Force remove** - Delete a storage target, skipping some usual steps
+* **Delete** - Permanently remove a storage target
+
+Read the rest of this article for more detail about these options.
+
+## Write cached files to the storage target
+
+The **Flush** option tells the cache immediately copy any changed files stored in the cache to the back-end storage system. For example, if your client machines are updating a particular file repeatedly, it is held in the cache for quicker access and not written to the long-term storage system for a period ranging from several minutes to more than an hour.
+
+The **Flush** action tells the cache to write all files to the storage system.
+
+The cache won't accept requests from clients for files on this storage target until after the flush is complete.
+
+You could use this option to make sure that the back-end storage is populated before doing a backup, or for any situation where you want to make sure the back-end storage has recent updates.
+
+This option mainly applies to usage models that include write caching. Read [Understand cache usage models](cache-usage-models.md) to learn more about read and write caching.
+
+## Suspend a storage target
+
+The suspend feature disables client access to a storage target, but doesn't permanently remove the storage target from your cache. You can use this option if you need to disable a back-end storage system for maintenance, repair, or replacement.
+
+## Put a suspended storage target back in service
+
+Use **Resume** to un-suspend a storage target.
+
+## Force remove a storage target
+
+> [!NOTE]
+> This option can cause data loss for the affected storage target.
+
+If a storage target can't be removed with a normal delete action, you can use the **Force remove** option to delete it from the Azure HPC Cache.
+
+This action skips the step that synchronizes files in the cache with the files in the back-end storage system. There is no guarantee that any changes written to the HPC Cache will be written to the back-end storage system, so changes can be lost if you use this option.
+
+There also is no guarantee that the back-end storage system will be accessible after it is removed from the cache.
+
+Usually, force remove is used only when a storage target has become unresponsive or otherwise is in a bad state. This option lets you remove the bad storage target instead of having to take more drastic action.
+<!-- https://msazure.visualstudio.com/One/_workitems/edit/8267141 -->
+
+## Delete a storage target
+
+You can use the Azure portal or the AZ CLI to delete a storage target. 
+
+The regular delete option permanently removes the storage target from the HPC Cache, but first it synchronizes the cache contents with the back-end storage system. It's different from the force delete option, which does not synchronize data.
+
+Deleting a storage target removes the storage system's association with this Azure HPC Cache, but it does not change the back-end storage system. For example, if you used an Azure Blob storage container, the container and its contents still exist after you delete it from the cache. You can add the container to a different Azure HPC Cache, re-add it to this cache, or delete it with the Azure portal.
+
+If there is a large amount of changed data stored in the cache, deleting a storage target can take several minutes to complete. Wait for the action to finish to be sure that the data is safely stored in your long-term storage system.
+
+### [Portal](#tab/azure-portal)
+
+To remove a storage target, open the **Storage targets** page. Click the '...' next to the storage target and choose **Delete** from the menu.
+
+### [Azure CLI](#tab/azure-cli)
+
+[Set up Azure CLI for Azure HPC Cache](./az-cli-prerequisites.md).
+
+Use [az hpc-cache storage-target remove](/cli/azure/hpc-cache/storage-target#az_hpc_cache_storage_target_remove) to delete a storage target from the cache.
+
+```azurecli
+$ az hpc-cache storage-target remove --resource-group cache-rg --cache-name doc-cache0629 --name blob1
+
+{- Finished ..
+  "endTime": "2020-07-09T21:45:06.1631571+00:00",
+  "name": "2f95eac1-aded-4860-b19c-3f089531a7ec",
+  "startTime": "2020-07-09T21:43:38.5461495+00:00",
+  "status": "Succeeded"
+}
+```
+
+---
+
+## Next steps
+
+* Learn about [cache-level management actions](hpc-cache-manage.md)
+* [Edit a storage target](hpc-cache-edit-storage.md)