From OneFS 8.0.0, the entire NDU process can be described by a PowerScale cluster upgrade state machine as demonstrated in Figure 2. This means a PowerScale OneFS cluster is in exactly one of the following upgrade states at any given time:
- Committed
- Upgrading
- Upgraded
- Rollback
Figure 2. PowerScale cluster upgrade state and transition paths
The state will change as it moves through the NDU cycle based on a set of allowed transitions. In Figure 2, transitions are the blue arrows between two upgrade states:
- Upgrade
- Upgrade complete
- Rollback
- Rollback complete
- Commit
Table 1 lists all the details of each OneFS upgrade states and how they can switch from one to another through transitions.
Table 1. PowerScale cluster upgrade states and transition paths details
Committed | - A previous upgrade operation has been completed and committed.
- All nodes are running the same version of OneFS and all features of that version are available. Rollback to the previously installed version is not available.
- The cluster is ready to start another OneFS upgrade when required.
- A cluster remains in this state until another upgrade is initiated.
- This is considered the steady state of a cluster, and it is expected that a cluster over its life cycle will spend most of its operational time in this state.
|
Upgrading | - At least one PowerScale node has started upgrading to the target release version.
- The required information to roll back to the source release is maintained while the cluster is in Upgrading state.
- A cluster remains in Upgrading state until either all nodes are upgraded to the target release, or a rollback is initiated.
- In Upgrading state, the cluster is running in mixed mode, as there are now two versions of OneFS present in the cluster.
- Nodes which have already upgraded may be able to access some of the functionality of the new release.
- Nodes which have not been upgraded cannot access any new release functionality.
|
Upgraded | - All nodes are now running the target release version; however, the upgrade has not been Committed.
- The required configuration to roll back to the source release is maintained while the cluster is in an Upgraded state.
- A cluster in the Upgraded state can run any new functionality of the target release.
|
Rollback | - The cluster is in the process of rolling back a OneFS upgrade.
- Rollback can be initiated by the administrator on a cluster in either the Upgrading or Upgraded state.
- Once the upgrade is committed, rollback is no longer available.
- In the Rollback state, the cluster restores the saved information associated with the source release and prepares the nodes to reboot to the original source release version. Once the nodes have rebooted, the cluster transitions automatically to the Committed state.
- Rollback is available for both rolling and simultaneous upgrades. A cluster can be rolled back only to the previously installed release.
- This state should be considered a transition state. Clusters should not be run in this state for extended periods of time.
|
To check out the current cluster upgrade state and activity, use the following CLI command:
isi upgrade cluster view
or
isi upgrade view
An example of the output from the command above is as below, which indicates the PowerScale cluster is in the committed state:
Upgrade Status:
Cluster Upgrade State: committed
Current Upgrade Activity: -
Upgrade Start Time: 2018-08-09T07:22:15
Upgrade Finished Time: 2018-08-14T06:09:35
Current OS Version: 8.1.0.4_build(57)style(5)
Upgrade OS Version: N/A
Percent Complete: 0%
Nodes Progress:
Total Cluster Nodes: 3
Nodes On Older OS: 3
Nodes Upgraded: 0
Nodes Transitioning/Down: 0
LNN Progress Version Status
- - - - - - - - - - - - - - - - - - - - - - -
1 0% 8.1.0.4 committed
2 0% 8.1.0.4 committed
3 0% 8.1.0.4 committed