The steps below describe how to upgrade the nodes that make up your deployment. Select the steps that are appropriate for your VM host: OpenStack or VMware vSphere.
The supported versions for the platforms are listed below:
| Platform | Supported versions |
|---|---|
OpenStack |
Newton to Wallaby |
VMware vSphere |
6.7 and 7.0 |
Live migration of a node to a new VMware vSphere host or a new OpenStack compute node is not supported. To move such a node to a new host, remove it from the old host and add it again to the new host.
Notes on parallel vs sequential upgrade
If your custom VM type supports parallel upgrade, SIMPL VM can upgrade multiple VMs simultaneously. This can save a lot of time when you upgrade large deployments.
The node-parameters.yaml that was used to build the VM specifies whether parallel upgrade is supported.
It specifies a proportion ("factor") of the deployment size that can be upgraded simultaneously
and a maximum for that proportion.
You can calculate the number of nodes that are upgraded at once
by multiplying the deployment size by the factor, rounding down to a whole number,
then taking the smaller of the result and the configured maximum number of nodes.
For example, node-parameters.yaml might specify a factor of 0.25 and maximum of 10 nodes.
In a deployment with 26 nodes that were built with those settings,
SIMPL VM upgrades the first six nodes simultaneously,
then six more, then six more, then six more and finally the last two.
Preparing for an upgrade
| Task | More information |
|---|---|
Set up and/or verify your OpenStack or VMware vSphere deployment |
The installation procedures assume that you are upgrading VMs on an existing OpenStack or VMware vSphere host(s). Ensure the host(s) have sufficient vCPU, RAM and disk space capacity for the VMs. Note that for upgrades, you will temporarily need approximately one more VM’s worth of vCPU and RAM, and potentially more than double the disk space, than your existing deployment currently uses. You can later clean up older images to save disk space once you are happy that the upgrade was successful. Perform health checks on your host(s), such as checking for active alarms, to ensure they are in a suitable state to perform VM lifecycle operations. Ensure the VM host credentials that you will use in your SDF are valid and have sufficient permission to create/destroy VMs, power them on and off, change their properties, and access a VM’s terminal via the console. |
Prepare service configuration |
VM configuration information can be found at VM Configuration. |
Upgrades and patching
The following table sets out the steps you need to execute a rolling upgrade of an existing VM deployment. These steps also cover how to apply a patch to the VM deployment.
| Step | Task | Link |
|---|---|---|
Rolling upgrade |
Rolling upgrade of TSN nodes |
|
Rolling upgrade of MCP nodes |
||
Post-acceptance tasks |
