Upgrade Tungsten Fabric to 2011¶
This section describes how to upgrade Tungsten Fabric from version 5.1 to 2011.
Tungsten Fabric 5.1 is considered deprecated and will be declared unsupported in one of the upcoming releases.
The update of the Tungsten Fabric control plane is performed automatically while the data plane requires manual restart of the vRouter pods for the changes to be applied.
Verify that your OpenStack cloud is running on the latest MOSK release. See Release Compatibility Matrix for the release matrix and supported upgrade paths.
Verify that your OpenStack cloud is running OpenStack Victoria. If upgrade is required, proceed with Upgrade OpenStack.
Verify that running vRouter pods are up-to-date with the MOSK release.
Calculate the maintenance window for the Tungsten Fabric upgrade considering the following:
Upgrade requires pulling of new images. The amount of time required for this phase depends on quality of network connection to the Mirantis image registry, amount of workloads, and specification of the cluster nodes.
Upgrade includes the Tungsten Fabric control plane and data plane (vRouters) upgrade:
The control plane pods upgrade usually takes about 20 minutes.
The data plane may require workloads migration before the vRouter upgrade that causes network service interruption on the affected nodes. The pure vRouter upgrade takes 5-7 minutes in average.
Back up the databases as described in Back up TF databases.
Perform the upgrade¶
TFOperatorcustom resource for editing.
spec: settings: tfVersion: "2011"
Verify that all
tf-control-*pods are updated. This may take some time.
kubectl -n tf get ds
AVAILABLEfields must have the same values.
Manually restart the vRouter pods:
Since MOSK 22.4, the post-update restart of the TF vRouter pods has been implemented. Therefore, if the target update version of your deployment is MOSK 22.4 or newer, skip this step.
Remove the vRouter pods one by one manually.
Manual removal is required because vRouter pods use the
OnDeleteupdate strategy. vRouter pod restart causes networking downtime for workloads on the affected node. If it is not applicable for some workloads, migrate them before restarting the vRouter pods.
kubectl -n tf delete pod <VROUTER-POD-NAME>
Verify that all
tf-vrouter-*pods have been updated:
kubectl -n tf get ds | grep tf-vrouter
CURRENTfields must have the same values.
Verify the upgrade¶
Verify the consistency of the cloud after Tungsten Fabric upgrade through sanity tests using the Tempest service as described in Run Tempest tests.
Roll back the upgrade¶
If any failures occur after the upgrade, you can roll back your Tungsten Fabric cluster to version 5.1:
tfVersionparameter of the
TFOperatorcustom resource, specify
spec: settings: tfVersion: "5.1"
The Tungsten Fabric control plane services will be rolled back to version 5.1.
Roll back the vRouter pods manually as described in Perform the upgrade. The rollback procedure for the vRouter pods is the same as the upgrade one.