Triggering the Rolling Software Upgrade
The SMF utilizes the SMI Cluster Manager to perform a rolling software update. To update SMF using SMI Cluster Manager, use the following configurations:
Important | Before you begin, ensure that SMF is up and running with the current version of the software. |
-
Log in to SMI Cluster Manager Ops Center.
-
Download the latest TAR ball from the URL.
software-packages download url
Example:
SMI Cluster Manager# software-packages download <url>
-
Verify whether the TAR balls are loaded.
software-packages list
Example:
SMI Cluster Manager# software-packages list [ smf-2019-08-21 ] [ sample ]
-
Update the product repository URL with the latest version of the product chart.
NoteIf the repository URL contains multiple versions, the Ops Center automatically selects the latest version.
configure cluster cluster_name ops-centers app_name smf_instance_name repository url exit exit
Example:
SMI Cluster Manager# config SMI Cluster Manager(config)# clusters test2 SMI Cluster Manager(config-clusters-test2)# ops-centers smf data SMI Cluster Manager(config-ops-centers-smf/data)# repository <url> SMI Cluster Manager(config-ops-centers-smf/data)# exit SMI Cluster Manager(config-clusters-test2)# exit
-
Run the cluster sync command to update to the latest version of the product chart.
clusters cluster_name actions sync run
Example:
SMI Cluster Manager# clusters test2 actions sync run
Important-
The cluster synchronization updates the SMF Ops Center, which in turn updates the application pods (through helm sync command) one at a time automatically.
-
When you trigger rolling upgrade on a specific pod, the SMF avoids routing new calls to that pod.
-
The SMF honors in-progress call by waiting for 30 seconds before restarting the pod where rolling upgrade is initiated. Also, the SMF establishes all the in-progress calls completely within 30 seconds during the upgrade period (maximum call-setup time is 10 seconds).
-
Note |
|