This section explains the difference between Qumulo Core Instant Software Upgrades and Platform Upgrades and how to perform upgrades.
- If you perform multiple upgrades back to back, you might encounter one or more platform upgrades in one of the incremental releases; you must install these upgrades before you continue. Before performing back to back upgrades, contact the Qumulo Care team for guidance.
- If you don't see a rolling reboot option for a platform upgrade, refresh the page in your browser.
- Cloud Native Qumulo doesn't differentiate between upgrade modes and all upgrades are instant software upgrades that have a downtime of less than 30 seconds and don't disrupt the operation of the cluster.
For downloads, release notes, and upgrade paths for on-premises and cloud releases of Qumulo Core, see Qumulo Nexus đź”’.
Understanding the Upgrade Phases
Every Qumulo Core upgrade has two phases, preparation and commit.
-
Preparation: Qumulo Core stages a new image in an alternate boot drive partition while the current image continues to run. This phase is responsible only for the background work (unpacking and writing the platform image and upgrade firmware, and so on). When the preparation phase is complete, we continue to the commit phase.
-
Commit: Qumulo Core does one of the following:
- Instant Software Upgrade: Stops the existing container and starts a new one.
- Platform Upgrade: Initiates a reboot and selectively upgrades the operating system image.
To view your cluster’s upgrade phase and status, run the qq upgrade_status
command.
The following is example output.
{
"install_path": "/upgrade/qinstall.qimg",
"state": "UPGRADE_PREPARING",
"details": "",
"error_message": "",
"error_state": "UPGRADE_ERROR_NO_ERROR",
"is_blocked": false,
"blocked_reason": ""
}
Upgrading Your Qumulo Cluster
- Before beginning the upgrade process, make sure that you have the correct on-premises upgrade imageđź”’. CNQ uses the Qumulo Core Product Package (which doesn't have separate versions for on-premises and cloud platforms) as a deployment artifact. For this reason, you must use the on-premises upgrade image to upgrade a CNQ cluster.
- To allow certain background processes to run, multiple sequential Qumulo Core upgrades might require a waiting period between specific releases. Before installing multiple Qumulo Core releases within an extended maintenance window, contact the Qumulo Care team.
- When the node to which you are connected reboots, the Qumulo Core Web UI might redirect you to the Cluster is booting... page. To view the reboot status, you can connect to a different node or wait until the current node goes online and then click Support > Software Upgrade.
- During rolling reboots, the system reboots one or more nodes (depending on the configured protection level) in the cluster in succession. If your cluster is under heavy load due to write or delete operations, this process can take a long time.
To Upgrade Your Qumulo Cluster by Using the Qumulo Core Web UI
-
Upload the
qumulo_core_x.x.x.qimg
upgrade file to any directory on your cluster by using a client protocol such as NFS or SMB. -
Log in to the Qumulo Core Web UI.
-
Click Support > Software Upgrade.
-
On the Software Upgrade page, enter the file system path for the upgrade file without the leading slash, for example:Â
upgrade/qumulo_core_7.1.0.1.qimg
. -
Click Upgrade…
-
Confirm the current and new versions of Qumulo Core and then click Start Upgrade.
Qumulo Core prepares the upgrade then installs Qumulo software on your cluster.
When the upgrade is complete, the message You have successfully upgraded from Qumulo Core x.x.x to y.y.y is displayed.
To Upgrade Your Qumulo Cluster by Using the qq CLI
- For two-phase upgrades, there is no client downtime during the prepare phase, only during the commit phase.
- You can disable the CLI progress bar by adding the
--no-monitor
flag to your command. If you do this, it isn't possible to cancel the upgrade process after it begins. - Qumulo Core reboots a number of nodes (depending on the protection level configured on your cluster) in succession. This requires the restriper job to finish before Qumulo Core can continue to the next node in the cluster. If your cluster is under heavy load from write or delete operations, this process can take a long time.
-
Upload the
qumulo_core_x.x.x.qimg
upgrade file to any directory on your cluster by using a client protocol such as NFS or SMB. -
Use SSH to connect to an IP address of a node in your cluster.
-
To become the root user, run the
sudo -s
command. -
Depending on the current Qumulo Core version on your cluster, do one of the following:
-
Qumulo Core 5.1.0.1 (and Higher):
-
Immediate Upgrade with Rolling Reboot: Run the
qq upgrade_cluster
command. Use the--rolling
flag to specify rolling reboot, and the--path
flag to specify the path to the upgrade file. For example:qq upgrade_cluster \ --rolling \ --path /qumulo_upgrade_x.x.x.qimg
-
Two-Phase Upgrade with Rolling Reboot: Run the
qq upgrade_cluster
command first with theprepare
subcommand and then with thecommit
subcommand. Use the--rolling
flag to specify rolling reboot, and the--path
flag to specify the path to the upgrade file. For example:qq upgrade_cluster prepare \ --rolling \ --path /qumulo_upgrade_x.x.x.qimg
qq upgrade_cluster commit
-
-
Qumulo Core 5.0.6 (and Lower):
-
Immediate Upgrade: Run the
qq upgrade_cluster
command and use the--path
flag to specify the path to the upgrade file. For example:qq upgrade_cluster \ --path /qumulo_core_x.x.x.qimg
-
Two-Phase Upgrade: Run the
qq upgrade_cluster
command first with theprepare
subcommand and then with thecommit
subcommand. Use the--path
flag to specify the path to the upgrade file. For example:qq upgrade_cluster prepare \ --path /qumulo_core_x.x.x.qimg
qq upgrade_cluster commit
-
-
-
To view your cluster’s upgrade phase and status, run the
qq upgrade_status
command.When the CLI progress bar shows that the upgrade is complete, Qumulo Core restarts your cluster.
Note
You can disable the CLI progress bar by adding the--no-monitor
flag to your command. If you do this, it isn’t possible to cancel the upgrade process after it begins.