As part of Frame’s transition from Nutanix systems, Frame needed to change our Content Delivery Network (CDN) for our Frame platform hosted on console.nutanix.com. While the plan was to transition CDN providers during a scheduled maintenance window in the future, Nutanix made the change without advanced notice to Dizzion.
Two issues occurred with this CDN change:
1. Dizzion's CDN was configured to prioritize HTTP/2 over HTTP/1.1 and 1.2 for all twenty (20) Frame control plane FQDNs, including cch.console.nutanix.com, which handles communication from Cloud Connector Appliances (CCAs). This configuration prevented a small subset of our AHV customers from starting sessions when the session required a new VM to be started or an existing VM to be restarted. Sessions to VMs already powered on and in a ready state, as well as existing sessions were not impacted.
2. The SSL/TLS certificate for Frame FQDN api.console.nutanix.com was not configured properly. This prevented customers successfully calling Frame Admin API endpoints. This issue was identified and resolved by 9:30 AM PST.
Once it was identified that the change in CDN was the likely culprit of issue #1, Dizzion worked with Nutanix to revert the CDN provider for cch.console.nutanix.com. In an abundance of caution, Dizzion also requested Nutanix revert the CDN provider for api.console.nutanix.com. All other Frame FQDN endpoints remain on the Dizzion CDN provider.