add upgrade schedule and priming changes

Author: ekpgh

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

@@ -1,11 +1,11 @@
 ---
 title: Manage and update Azure HPC Cache
 description: How to manage and update Azure HPC Cache using the Azure portal or Azure CLI
-author: ronhogue
+author: ekpgh
 ms.service: hpc-cache
 ms.topic: how-to
-ms.date: 01/19/2022
-ms.author: rohogue
+ms.date: 05/27/2022
+ms.author: v-erinkelly
 ---
 
 # Manage your cache
@@ -147,15 +147,37 @@ If a new software version is available, the **Upgrade** button becomes active. Y
 
 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.
+The software update can take several hours. Caches configured with higher throughput take longer to upgrade than caches with smaller peak throughput values. The cache status changes to **Upgrading** until the operation completes.
 
-When a software upgrade is available, you will have a week or so 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 the cache performance impact, you should upgrade the software yourself before the time period expires.
+When a software upgrade is available, you will have a week or so 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. 
+
+You can use the Azure Portal to schedule a more convenient time for the update. Follow the instructions in the **Portal** tab below.
 
 If your cache is stopped when the end date passes, the cache will automatically upgrade software the next time it is started. (The update might not start immediately, but it will start in the first hour.)
 
 ### [Portal](#tab/azure-portal)
 
-Click the **Upgrade** button to begin the software update. The cache status changes to **Upgrading** until the operation completes.
+Click the **Upgrade** button to configure your software update. You have the option to update the software immediately, or to schedule the update for a specific date and time.
+
+![Screenshot of the Schedule software upgrade blade showing radio buttons with "Schedule later" selected and fields to select a new date and time.](media/upgrade-schedule.png)
+
+To upgrade immediately, select **Upgrade now** and click the **Save** button.
+
+To schedule a different update time, select **Schedule later** and select a new date and time.
+
+* The date and time are shown in the browser's local time zone.
+* You can't choose a later time than the deadline in the original message.
+
+When you save the custom date, the update message will change to show the date you chose.
+
+If you want to revise your scheduled upgrade date, click the **Update** button again. Click the **Reset date** link. This immediately removes your scheduled date.
+
+> [!NOTE]
+> You must choose a new date before you exit the **Schedule software upgrade** blade. The calendar selector might reset to a date and time one hour from the current time; be careful to choose the date and time you prefer.
+
+![Screenshot of the Schedule software upgrade blade with a custom date selected. A text link appears at the left of the date labeled "Reset date".](media/upgrade-reset-date.png)
+
+You can't change the schedule if there are fewer than 15 minutes remaining before the upgrade.
 
 ### [Azure CLI](#tab/azure-cli)
 

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

@@ -159,7 +159,7 @@ The **State** value affects which management options you can use. Here's a short
 
 ## Allocate cache storage
 
-xxx to come xxx
+<!-- xxx to come xxx -->
 
 ![Screenshot of the storage targets page in the Azure portal.](media/storage-target-allocation.png)
 

articles/hpc-cache/media/hpc-cache-upgrade-button.png

@@ -4,7 +4,7 @@ description: Use the cache priming feature to populate or preload cache contents
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: how-to
-ms.date: 05/26/2022
+ms.date: 05/27/2022
 ms.author: v-erinkelly
 ---
 
@@ -211,19 +211,19 @@ To delete a priming job, select it in the list and use the delete control at the
 
 ## Azure REST APIs
 
-You can use these REST API endpoints to create an HPC Cache priming job. These are part of the `2021-10-01-preview` version of the REST API, so make sure you use that string in the *api_version* term.
+You can use these REST API endpoints to create and manage HPC Cache priming jobs. These are part of the `2022-05-01` version of the REST API, so make sure you use that string in the *api_version* term.
 
-***xxx update api version throughout xxx***
+Read the [Azure REST API reference](/rest/api/azure/) to learn how to use these tools.
 
-Read the [Azure REST API reference](/rest/api/azure/) to learn how to use this interface.
+### Add a new priming job
 
-### Add a priming job
+The `startPrimingJob` interface creates and queues a priming job. The job starts automatically when resources are available.
 
 ```rest
 
 URL: POST
 
-     https://MY-ARM-HOST/subscriptions/MY-SUBSCRIPTION-ID/resourceGroups/MY-RESOURCE-GROUP-NAME/providers/Microsoft.StorageCache/caches/MY-CACHE-NAME/addPrimingJob?api-version=2021-10-01-preview
+     https://MY-ARM-HOST/subscriptions/MY-SUBSCRIPTION-ID/resourceGroups/MY-RESOURCE-GROUP-NAME/providers/Microsoft.StorageCache/caches/MY-CACHE-NAME/startPrimingJob?api-version=2022-05-01
 
      BODY:
      {
@@ -235,14 +235,20 @@ URL: POST
 
 For the `primingManifestUrl` value, pass the file’s SAS URL or other HTTPS URL that is accessible to the cache. Read [Upload the priming manifest file](#upload-the-priming-manifest-file) to learn more.
 
-### Remove a priming job
+### Stop a priming job
+
+The `stopPrimingJob` interface cancels a job (if it is running) and removes it from the job list.
 
 ```rest
 
 URL: POST 
-     https://MY-ARM-HOST/subscriptions/MY-SUBSCRIPTION-ID/resourceGroups/MY-RESOURCE-GROUP-NAME/providers/Microsoft.StorageCache/caches/MY-CACHE-NAME/removePrimingJob/MY-JOB-ID-TO-REMOVE?api-version=2021-10-01-preview
+     https://MY-ARM-HOST/subscriptions/MY-SUBSCRIPTION-ID/resourceGroups/MY-RESOURCE-GROUP-NAME/providers/Microsoft.StorageCache/caches/MY-CACHE-NAME/stopPrimingJob?api-version=2022-05-01
 
 BODY:
+     {
+         "primingJobId": "MY-JOB-ID-TO-REMOVE"
+     }
+
 ```
 
 ### Get priming jobs
@@ -254,12 +260,14 @@ Priming job names and IDs are returned, along with other information.
 ```rest
 
 URL: GET 
-     https://MY-ARM-HOST/subscriptions/MY-SUBSCRIPTION-ID/resourceGroups/MY-RESOURCE-GROUP-NAME/providers/Microsoft.StorageCache/caches/MY-CACHE-NAME?api-version=2021-10-01-preview
+     https://MY-ARM-HOST/subscriptions/MY-SUBSCRIPTION-ID/resourceGroups/MY-RESOURCE-GROUP-NAME/providers/Microsoft.StorageCache/caches/MY-CACHE-NAME?api-version=2022-05-01
 
 BODY:
 
 ```
 
+***[ ?? should we add pause/resume APIs here too? ??]***
+
 ## Frequently asked questions
 
 * Can I reuse a priming job?