Merge pull request #93074 from ronhogue/ronh1023

add manage cache article

Author: v-shils

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

@@ -0,0 +1,75 @@
+---
+title: Manage and update Azure HPC Cache (Preview)
+description: How to manage and update Azure HPC Cache using the Azure portal 
+author: ekpgh
+ms.service: hpc-cache
+ms.topic: conceptual
+ms.date: 10/25/2019
+ms.author: rohogue
+---
+
+# Manage your cache from the Azure portal
+
+The cache overview page in the Azure portal shows project details, cache status, and basic statistics for your cache. It also has controls to delete the cache, flush data to long-term storage, or update software.
+
+To open the overview page, select your cache resource in the Azure portal. For example, load the **All resources** page and click the cache name.
+
+![screenshot of an Azure HPC Cache instance's Overview page](media/hpc-cache-overview.png) <!-- placeholder is identical to hpc-cache-new-overview.png; replace with better image (showing graphs, full sidebar) when available -->
+
+The buttons at the top of the page can help you manage the cache:
+
+* [**Flush**](#flush-cached-data) - Writes all cached data to storage targets
+* [**Upgrade**](#upgrade-cache-software) - Updates the cache software
+* **Refresh** - Reloads the overview page
+* [**Delete**](#delete-the-cache) - Permanently destroys the cache
+
+Read more about these options below.
+
+## Flush cached data
+
+The **Flush** button on the overview page tells the cache to immediately write all changed data that is stored in the cache to the back-end storage targets. The cache routinely saves data to the storage targets, so it's not necessary to do this manually unless you want to make sure the back-end storage system is up to date. For example, you might use **Flush** before taking a storage snapshot or checking the data set size.
+
+> [!NOTE]
+> During the flush process, the cache can't serve client requests. Cache access is suspended and resumes after the operation finishes.
+
+When you start the cache flush operation, the cache stops accepting client requests, and the cache status on the overview page changes to **Flushing**.
+
+Data in the cache is saved to the appropriate storage targets. The process can take a few minutes or it can take an hour or more, depending on how much data has been written to the cache recently.
+
+After all the data is saved to storage targets, the cache automatically starts taking client requests again. The cache status returns to **Healthy**.
+
+## Upgrade cache software
+
+If a new software version is available, the **Upgrade** button becomes active. You also might see a message at the top of the page about updating software.
+
+![screenshot of the top row of buttons with the Upgrade button enabled](media/hpc-cache-upgrade-button.png)
+
+Client access is not interrupted during a software upgrade, but cache performance slows. Plan to upgrade software during non-peak usage hours or in a planned maintenance period.
+
+The software update can take several hours. Caches configured with higher throughput take longer to upgrade than caches with smaller peak throughput values.
+
+When a software upgrade is available, you have several days to apply it manually. The end date is listed in the upgrade message. If you don't upgrade during that time, Azure automatically applies the update to your cache. The timing of the automatic upgrade is not configurable. If you are concerned about impacting cache performance, you should upgrade the software yourself before the time period expires.
+
+Click the **Upgrade** button to begin the software update. The cache status changes to **Upgrading** until the operation completes.
+
+## Delete the cache
+
+The **Delete** button destroys the cache. When you delete a cache, all of its resources are destroyed and no longer incur account charges.
+
+Storage targets are unaffected when you delete the cache. You can add them to a future cache later, or decommission them separately.
+
+The cache automatically flushes any unsaved data to storage targets as part of its final shutdown.
+
+## Cache metrics and monitoring
+
+The overview page shows graphs for some basic cache statistics - cache throughput, operations per second, and latency.
+
+![screenshot of three line graphs showing the statistics mentioned above for a sample cache](media/hpc-cache-overview-stats.png)
+
+These charts are part of Azure's built-in monitoring and analytics tools. Additional tools and alerts are available from the pages under the **Monitoring** heading in the portal sidebar. Learn more in the portal section of the [Azure Monitoring documentation](../azure-monitor/insights/monitor-azure-resource.md#monitoring-in-the-azure-portal).
+
+## Next steps
+
+<!-- * Learn more about metrics and statistics for hpc cache -->
+* Learn more about [Azure metrics and statistics tools](../azure-monitor/index.yml)
+* Get [help with your Azure HPC Cache](hpc-cache-support-ticket.md)

articles/hpc-cache/index.yml

@@ -11,7 +11,7 @@ metadata:
   ms.collection: collection
   author: ekpgh
   ms.author: rohogue
-  ms.date: 09/24/2019
+  ms.date: 10/21/2019
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 
@@ -39,6 +39,8 @@ landingContent:
             url: hpc-cache-add-storage.md
           - text: Mount clients
             url: hpc-cache-mount.md
+          - text: Manage and monitor the cache
+            url: hpc-cache-manage.md
       - linkListType: concept
         links:
           - text: Plan the aggregated namespace

articles/hpc-cache/media/hpc-cache-overview-stats.png

@@ -33,9 +33,10 @@
           href: hpc-cache-ingest-msrsync.md
         - name: Populate the cache by manual file copy 
           href: hpc-cache-ingest-manual.md
-  
   - name: Connect to the cache
     href: hpc-cache-mount.md
+  - name: Manage the cache 
+    href: hpc-cache-manage.md
 
 - name: Resources
   items: