VAST Cluster 5.4.5 Release Notes

This release is only available for VAST on Cloud clusters.

New Features

VAST Cluster 5.4.5 introduces support for Polaris-based VAST on Cloud deployments on Amazon AWS.

To deploy a VoC cluster on AWS:

Ensure that your AWS account is configured with sufficient privileges.
Ensure that your local host has networking set up with the required ports open.
Sign in to the VAST Polaris for AWS portal.
Use VAST Polaris UI and VAST on Cloud CLI (vastcloud) to create a new AWS deployment.

For complete guidance and configuration details, see VAST Polaris Administrator's Guide.

Added user controls to manage allocation of virtual IP pools and DNS in VoC environments:
- In VAST CLI, the vippool allocate, vippool reallocate, dns allocate commands
- In VAST REST API, the /vippools/allocate/, /vippools/<pool ID>/reallocate/, /dns/allocate/ endpoints.

ORION-405554: Introduced an internal change to ensure that VAST on AWS clusters get AWS permissions required to take advantage of one of the upcoming features.

ORION-409117: Made updates to ensure that users with the read-only administrative role cannot perform folder management actions via the respective VAST REST API endpoints.

VAST Cloud (Polaris) UI does not provide an option to run a cluster upgrade. Cluster upgrades are to be performed using the VAST Web UI.
VAST on Cloud clusters do not support OS upgrade.
In the event of downtime, data is rebuilt while the cluster comes back online. In case of a subsequent failure during the rebuild, data integrity is not guaranteed.
ORION-327048: For VoC on GCP, it is recommended to have a multiple of 8 non-VMS VMs per cluster, since GCP has 8 failure domains and imbalance may result in failed stripe allocations.
ORION-145141: Creating a tenant with EKM encryption is not supported on VoC clusters.
ORION-113036: After you reregister the same VoC cluster in Uplink, information about the previously registered instance of this cluster is no longer available in Uplink.