Triggering the Rolling Software Upgrade
AMF utilizes the SMI Cluster Manager to perform a rolling software upgrade.
To upgrade AMF using SMI Cluster Manager, use the following configuration procedures:
Important | Before you begin, ensure that the AMF is up and running with the current version of the software. |
-
Log on to the SMI Cluster Manager Ops Center
-
Download the latest tarball from the URL, as the following:
software-packages download url
NOTES:
-
software-packages download url —Specify the software packages to be downloaded through HTTP/HTTPS.
Example:
SMI Cluster Manager# software-packages download <url>
-
-
Verify whether the tarball is loaded.
software-packages list
NOTES:
-
software-packages list —Specify the list of available software packages.
Example:
SMI Cluster Manager# software-packages list [ amf-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.
config cluster cluster_name ops-centers app_name instance_name repository url exit exit
NOTES:
-
cluster cluster_name —Specify the K8s cluster name.
-
ops-centers app_name instance_name—Specify the product Ops Center and instance.
app_name is the application name.
instance_name is the name of the AMF instance.
-
repository url —Specify the local registry URL for downloading the charts.
Example:
SMI Cluster Manager# config SMI Cluster Manager(config)# clusters test2 SMI Cluster Manager(config-clusters-test2)# ops-centers amf data SMI Cluster Manager(config-ops-centers-amf/data)# repository <url> SMI Cluster Manager(config-ops-centers-amf/data)# exit SMI Cluster Manager(config-clusters-test2)# exit
-
-
Update the latest version of the product chart using the following command:
clusters cluster_name actions sync run
NOTES:
-
actions —Specify the actions performed on the cluster.
-
sync run—Triggers the cluster synchronization.
Example:
SMI Cluster Manager# clusters test2 actions sync run
Important-
The cluster synchronization updates the AMF Ops Center, which in turn updates the application pods (through the helm sync command) one at a time automatically.
-
When you trigger rolling upgrade on a specific pod, the AMF avoids routing new calls to that pod.
-
The AMF honors in-progress calls by waiting for 30 seconds before restarting the pod where rolling upgrade is initiated. Also, the AMF establishes all the in-progress calls completely within 30 seconds during the upgrade period. The maximum call-setup time is 10 seconds.
-