Nutanix Clusters delivers a hybrid multi cloud platform addressing the pressing need for a single platform that can span private, distributed, and public clouds so that you can manage your traditional and modern applications using a consistent cloud platform.

Nutanix Clusters has features such as operational simplicity, seamless application mobility, and cost efficiency needed to run applications in private or multiple public clouds and reduce the operational complexity of migrating, extending, or bursting your applications and data between clouds.

Nutanix Clusters extends the simplicity and ease of use of Nutanix hyperconverged infrastructure (HCI) software as well as the full Nutanix stack to public clouds such as AWS.

You can modify, update, display, hibernate, resume, and delete Nutanix clusters running on AWS by using the Nutanix Clusters console.

Nutanix Clusters console Updates

The service that is responsible for provisioning, maintaining underlying infrastructure and making configuration updates to the Nutanix Clusters console is called Clusters orchestration engine that is part of the Nutanix Clusters console. This service is maintained and managed by Nutanix. With continuous delivery, the service gets new updates frequently and keeps getting better with new capabilities and bug fixes.

The Orchestration Engine is a combination of the hosted service and a collection of orchestration agents, which are installed on the bare metal hosts of Nutanix Clusters. Even though the agents (Clusters agent, Host agent, Infra Gateway agent, and Cloud Net) are deployed in your environments, they are an integral part of the service and need to be in sync and up-to-date with the Orchestration engine.

There are two kinds of updates that take place with respect to the Orchestrator Engine:

• Regular updates: Typically every Thursday morning, Central European time(CET). These include planned feature releases, bug fixes, and system updates.

• Ad-Hoc updates: No fixed time. These are smaller updates such as a hot-fix for a P0 issue or a fix for a bug that is preventing optimal operations of the service. Decision on when to deploy an update is made based on a combination of factors, such as severity of the issue that is being addressed, risk of the deployment, and risk of postponing the deployment.

• All updates are expected to be non-disruptive and provide uninterrupted access to the Clusters Orchestration Engine. When the updates are completed, this Release Notes document is updated with the changes and critical updates.