Squashed commit of the following:

8.6.4 Release

Author: adriankjohnson

articles/cyclecloud/cluster-references/node-nodearray-reference.md

@@ -104,6 +104,7 @@ EncryptionAtHost (8.4.0+) | Boolean | If true, the virtual machine will have [En
 SecurityType (8.5.0+) | String | Sets the [security type](../how-to/vm-security.md); either undefined, `TrustedLaunch` or `ConfidentialVM`
 | EnableSecureBoot (8.5.0+) | Boolean | Enables [Secure Boot](../how-to/vm-security.md), if using Trusted Launch VMs or Confidential VMs.
 | EnableVTPM (8.5.0+) | Boolean | Enables [Virtual Trusted Platform Module](../how-to/vm-security.md), if using Trusted Launch VMs or Confidential VMs.
+| ScaleSetUpgradePolicyMode (8.6.2+) | String | Specifies the scale set upgrade policy, which controls what happens to existing VMs in a scale set when the scale set template is modified outside CycleCloud. This should generally be enabled if using an automated tool to modify existing scale sets, such as Azure Policy. Note: this does *not* automatically upgrade the OS image. One of `Automatic`, `Rolling`, or `Manual` (the default).
 
 > [!NOTE]
 > A Proximity Placement Group is a general Azure feature, and one must be created before it can be referenced on a node. 

articles/cyclecloud/concepts/usage-tracking.md

@@ -30,10 +30,11 @@ Current spend with overage:
 
 ## Notifications
 
-If you wish to receive email or Slack notifications when your cluster exceeds the budget, enter one of the following:
+If you wish to receive email, Microsoft Teams, or Slack™ notifications when your cluster exceeds the budget, enter one of the following:
 
 * **User Name**: Emails the address associated with the user account.
 * **Email Address**: Enter an email address for the alert.
+* **Teams**: If you are using [Microsoft Teams](https://www.microsoft.com/microsoft-teams/group-chat-software), you can set up a [webhook](/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook). Note: this method is deprecated and will be discontinued. There is currently no support in CycleCloud for the new Workflows method.
 * **Slack**: If you are using [Slack](https://slack.com/), you can set up a [webhook](https://api.slack.com/incoming-webhooks) to have notifications sent to a specific channel.
 
 Add the alert recipient's information and click **Save**. To add additional recipients, click the **+**, or **-** to delete.

articles/cyclecloud/cycleserver-configuration-reference.md

@@ -27,7 +27,6 @@ CycleCloud uses the _cycle_server.properties_ file to pass configuration paramet
 | webServerEnableHttp | Boolean | Enable HTTP listen port. | `true` |
 | webServerEnableHttps | Boolean | Enable HTTPS listen port. | `false` |
 | webServerRedirectHttp | Boolean | If both HTTPS and HTTP is enabled, controls whether HTTP redirects to HTTPS. | `true` |
-| webServerUseNativeHttps | Boolean | Improves HTTPS performance on Linux platforms by using Tomcat's native HTTPS implementation. `webServerEnableHttps` must also be `true`. | `false` |
 | sslEnabledProtocols | String | List of `+` separated TLS protocols to allow. e.g. `TLSv1.2+TLSv1.3` | `TLSv1.3` |
 | brokerMaxHeapSize | String | This is a JVM maximum heap size setting for the message queue broker. | Linux: `1024M`; Windows: `512M` |
 | brokerJvmOptions | String | This setting is provided for any user configurable JVM settings for the message queue broker. CycleServer only appends the message broker heap size, and port, options. | None |

articles/cyclecloud/how-to/running-in-locked-down-network.md

@@ -98,38 +98,52 @@ access is not possible then the necessary files can be downloaded
 from another machine and copied to CycleCloud. 
 
 First determine which project and
-version your cluster will need, e.g. Slurm 2.5.0. It's normally the highest version
+version your cluster will need, e.g. Slurm 3.0.8. It's normally the highest version
 number in the database for a given project.
+You can determine the latest version either by visiting the github project page or by
+querying CycleCloud for the latest version.
+
+To query CycleCloud (note that there will often be multiple versions listed):
 
 ```shell
-/opt/cycle_server/cycle_server execute 'select * from cloud.project where name == "slurm"'
+/opt/cycle_server/cycle_server execute 'select Name, Version, Url from cloud.project where name == "slurm" order by Version'
 
-AdType = "Cloud.Project"
-Version = "2.5.0"
-ProjectType = "scheduler"
-Url = "https://github.com/Azure/cyclecloud-slurm/releases/2.5.0"
-AutoUpgrade = false
 Name = "slurm"
+Version = "3.0.8"
+Url = "https://github.com/Azure/cyclecloud-slurm/releases/3.0.8"
 ```
 
 This project version and all dependencies are found in the [release tag]
-(https://github.com/Azure/cyclecloud-slurm/releases/tag/2.5.0).
-All artifacts for a release must be downloaded. First download the code artifact
-and create a blobs directory for the additional dependencies.
+(https://github.com/Azure/cyclecloud-slurm/releases/tag/3.0.8).
+
+You can download all release artifacts manually, but the CycleCloud CLI provides
+a helper for this operation.
+
+First, use the CycleCloud CLI to fetch and prepare the repository from github 
+(this is the same operation CycleCloud performs during the "Staging Resources" phase):
 
 ```bash
-wget https://github.com/Azure/cyclecloud-slurm/archive/refs/tags/2.5.0.tar.gz
-tar -xf 2.5.0.tar.gz 
-cd cyclecloud-slurm-2.5.0 && mkdir blobs 
-#... download all other release artifacts to the /blobs directory with wget ...
-wget -P "blobs/" https://github.com/Azure/cyclecloud-slurm/releases/download/2.6.1/cyclecloud_api-8.1.0-py2.py3-none-any.whl
-#... copy all the files to the Cyclecloud server
-#... then on the Cyclecloud server:
+RELEASE_URL="https://github.com/Azure/cyclecloud-slurm/releases/3.0.8"
+RELEASE_VERSION="3.0.8"
+mkdir "${RELEASE_VERSION}"
+cd "${RELEASE_VERSION}"
+# Download release artifacts from githug (on a machine with github access)
+cyclecloud project fetch "${RELEASE_URL}" .
+
+# Create a tarbal with the project files pre-staged
 cyclecloud project build
-mkdir -p /opt/cycle_server/work/staging/projects/slurm/2.5.0
-mkdir -p /opt/cycle_server/work/staging/projects/slurm/blobs
-cp build/slurm/* /opt/cycle_server/work/staging/projects/slurm/2.5.0/
-cp blobs/* /opt/cycle_server/work/staging/projects/slurm/blobs/
+mv ./build/slurm "./${RELEASE_VERSION}"
+tar czf "slurm-${RELEASE_VERSION}.tgz" ./blobs "./${RELEASE_VERSION}"
+```
+
+Next, copy the packaged project tarball to the CycleCloud server and extract:
+
+```bash
+#... copy the "slurm-${RELEASE_VERSION}.tgz" file to the Cyclecloud server in /tmp
+sudo -i
+mkdir -p /opt/cycle_server/work/staging/projects/slurm
+cd /opt/cycle_server/work/staging/projects/slurm
+tar xzf "/tmp/slurm-${RELEASE_VERSION}.tgz"
 chown -R cycle_server:cycle_server /opt/cycle_server/work/staging
 ```
 

articles/cyclecloud/how-to/ssl-configuration.md

@@ -92,28 +92,10 @@ Finally, if you make changes to the keystore outside of these commands, you can
 ./cycle_server keystore reconfig
 ```
 
-## Configuring CycleCloud to use Native HTTPS
-
-By default, Azure CycleCloud is configured to use the standard Java IO HTTPS
-implementation. This default works well on all supported platforms.
-
-To improve performance when running on Linux platforms, CycleCloud may
-optionally be configured to use the Tomcat Native HTTPS implementation.
-
-To enable Native HTTPS on Linux, add the `webServerEnableHttps` and `webServerUseNativeHttps` attributes to your _cycle_server.properties_ file. Open _cycle_server.properties_ with a text editor and set the following values:
-
-``` properties
-# Turn on HTTPS
-webServerEnableHttps = true
-
-# Use Native HTTPS connector
-webServerUseNativeHttps = true
-```
-
 ::: moniker range="=cyclecloud-7"
 ## Backwards compatibility for TLS 1.0 and 1.1
 
-By default, the Java and Native HTTPS connectors will be configured to use only the
+By default, CycleServer will be configured to use only the
 TLS 1.2 protocol. If you need to offer TLS 1.0 or 1.1 protocols for older web clients, you may
 opt-in for backwards compatibility.
 

articles/cyclecloud/index.yml

@@ -41,7 +41,7 @@ landingContent:
     linkLists:            
       - linkListType: whats-new
         links:
-          - text: CycleCloud 8.6.3 is now available
+          - text: CycleCloud 8.6.4 is now available
             url: release-notes.md
           - text: Node Health Checks are now supported
             url: how-to/healthcheck.md

articles/cyclecloud/release-notes.md

@@ -8,7 +8,7 @@ ms.author: adjohnso
 
 # Azure CycleCloud 8.x
 
-The current release is 8.6.3.
+The current release is 8.6.4.
 
 ## Azure CycleCloud 8.x Release Highlights
 
@@ -29,6 +29,7 @@ CycleCloud 8.6 is the sixth GA release of the CycleCloud 8.x platform and contin
 ## Release Notes
 
 Comprehensive release notes for the individual 8.x releases are listed below:
+* [**8.6.4 Release Notes**](release-notes/8-6-4.md) - released on 08/30/24
 * [**8.6.3 Release Notes**](release-notes/8-6-3.md) - released on 07/18/24
 * [**8.6.2 Release Notes**](release-notes/8-6-2.md) - released on 05/31/24
 * [**8.6.1 Release Notes**](release-notes/8-6-1.md) - released on 04/04/24

articles/cyclecloud/release-notes/8-6-0.md

@@ -1,6 +1,6 @@
 ---
 title: Release Notes v8.6.0
-description: Product release notes for Azure CycleCloud public preview v8.6.0
+description: Product release notes for Azure CycleCloud v8.6.0
 author: adriankjohnson
 ms.date: 02/22/2024
 ms.author: adjohnso

articles/cyclecloud/release-notes/8-6-1.md

@@ -1,6 +1,6 @@
 ---
 title: Release Notes v8.6.1
-description: Product release notes for Azure CycleCloud public preview v8.6.1
+description: Product release notes for Azure CycleCloud v8.6.1
 author: adriankjohnson
 ms.date: 04/04/2024
 ms.author: adjohnso

articles/cyclecloud/release-notes/8-6-2.md

@@ -1,6 +1,6 @@
 ---
 title: Release Notes v8.6.2
-description: Product release notes for Azure CycleCloud public preview v8.6.2
+description: Product release notes for Azure CycleCloud v8.6.2
 author: adriankjohnson
 ms.date: 05/31/2024
 ms.author: adjohnso