The steps below describe how to install or 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.
Note that after completing an upgrade or CSAR EFIX patch of only a subset of the nodes that does not include the MAG node, you will need to re-upload the existing configuration set for the MAG nodes, but with the SDF updated to specify the correct version of the upgraded or patched nodes. This ensures that the MAG node can populate connection settings for the other nodes in REM.
Notes on parallel vs sequential upgrade
Some node types support parallel upgrade, that is, SIMPL upgrades multiple VMs simultaneously.
This can save a lot of time when you upgrade large deployments.
SIMPL VM upgrades one quarter of the nodes (rounding down any remaining fraction) simultaneously, up to a maximum of ten nodes. Once all those nodes have been upgraded, SIMPL VM upgrades the next set of nodes. For example, in a deployment of 26 nodes, SIMPL VM upgrades the first six nodes simultaneously, then six more, then six more, then six more and finally the last two.
The following node types support parallel upgrade: MAG, ShCM, and MMT GSM. All other node types are upgraded one VM at a time.
Preparing for a new installation or an upgrade
| Task | More information |
|---|---|
Set up and/or verify your OpenStack or VMware vSphere deployment |
The installation procedures assume that you are installing the VMs into, or upgrading VMs on, an existing OpenStack or VMware vSphere host(s). If you do not yet have a host system set up, then complete the setup of your host in its entirety before proceeding with installing the VMs. 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. An in-depth description of RVT YAML configuration can be found in the Rhino VoLTE TAS Configuration and Management Guide. |
Installation
The following table sets out the steps you need to take to install and commission your VM deployment.
Be sure you know the number of VMs you need in your deployment. At present it is not possible to change the size of your deployment after it has been created.
| Step | Task | Link |
|---|---|---|
Installation (on VMware vSphere) |
Prepare the SDF for the deployment |
|
Deploy SIMPL VM into VMware vSphere |
||
Prepare configuration files for the deployment |
||
Install MDM |
||
Prepare SIMPL VM for deployment |
||
Deploy the nodes on VMware vSphere |
||
Installation (on OpenStack) |
Prepare the SDF for the deployment |
|
Deploy SIMPL VM into OpenStack |
||
Prepare configuration files for the deployment |
||
Create the OpenStack flavors |
||
Install MDM |
||
Prepare SIMPL VM for deployment |
||
Deploy the nodes on OpenStack |
||
Verification |
Run some simple tests to verify that your VMs are working as expected |
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 MAG nodes |
||
Rolling upgrade of ShCM nodes |
||
Rolling upgrade of MMT GSM nodes |
||
Rolling upgrade of SMO nodes |
||
Post-acceptance tasks |
||
Major upgrade from 4.0.0 |
Major upgrade from 4.0.0 of MAG nodes |
|
Major upgrade from 4.0.0 of ShCM nodes |
||
Major upgrade from 4.0.0 of MMT GSM nodes |
||
Major upgrade from 4.0.0 of SMO nodes |
||
Major upgrade from 4.0.0 of TSN nodes |
||
Cassandra version switch procedure for TSN nodes |
||
Post-acceptance tasks |
