Upgrade OpenVidu High Availability: Oracle Cloud Infrastructure#

Oracle Cloud Infrastructure

For Oracle Cloud Infrastructure environments, we recommend upgrading by redeploying the OpenVidu High Availability Oracle Cloud Infrastructure stack using the latest version. This approach ensures that all components are updated accurately and consistently, since Oracle Cloud Infrastructure Terraform files and related configurations may differ between releases. Redeploying guarantees that all necessary changes are properly applied.

If you would prefer not to redeploy, an in-place upgrade is also possible. The steps below describe how to perform an in-place upgrade of your OpenVidu High Availability deployment on Oracle Cloud Infrastructure.

Upgrading OpenVidu High Availability on Oracle Cloud Infrastructure#

SSH into one of your Master Nodes.
Execute the following command in the Master Node:
```
sh <(curl -fsSL http://get.openvidu.io/update/latest/update.sh)
```
To upgrade to a specific version instead, replace latest with the version number (e.g. 3.7.0).

This will run an update script that guides you from your currently installed version to the target one. The output will begin with the following:

Stopping OpenVidu service...
Backing up files...

    - Backing up file '/opt/openvidu/config' to '/opt/openvidu/backups/<DATE>_<VERSION>/config'
    ... More files ...

--------------------
📦 Backup directory: /opt/openvidu/backups/<DATE>_<VERSION>/
--------------------

--------------------
🚀 Updating OpenVidu from 3.x.x to 3.y.y
--------------------

? Do you want to update from 3.x.x to 3.y.y? ›
• Yes
  No

Confirm each version upgrade. You can jump straight to the latest release regardless of how far behind you are — the updater will automatically apply every intermediate upgrade in sequence.

For each intermediate version, the updater will prompt you to confirm the upgrade, display a diff of configuration file changes, ask whether to apply the diff, and ask whether to pull updated Docker images. You must confirm each step.

Warning

The updater will flag any breaking changes if they are present. Pay close attention to these, as they may require you to update firewall rules, open or close specific ports, or make other manual configuration changes.

Pulling Docker images

When upgrading across multiple intermediate versions, answer No when the updater asks whether to pull images at each intermediate step. Only answer Yes for the final version.

Any missing images will be pulled automatically when you run systemctl start openvidu.
Repeat steps 1 to 4 on each of the remaining Master Nodes of your deployment. This is important because all 4 Master Nodes need to be running the same version of OpenVidu.
After the final intermediate upgrade completes on all 4 Master Nodes, you need to terminate the Media Nodes to apply the changes. Go to the OCI Console, navigate to the Compute → Instance Pools section, open <STACK_NAME>-media-pool, and terminate the existing Media Node instances. The Instance Pool will automatically launch new Media Nodes with the updated configuration.
Once the Media Nodes are up and running, restart OpenVidu High Availability by running the following command on every Master Node:
```
systemctl start openvidu && journalctl -f -u openvidu
```
The journalctl command will show you the logs of the OpenVidu services. You can stop the logs by pressing Ctrl + C.

Backups and Rollback#

Once the upgrade is complete, a backup of the previous version will be available in the /opt/openvidu/backups directory of each Master Node. The backup contains only the configuration files that were changed during the upgrade.

To roll back to the previous version, copy the files from the backup back to the OpenVidu directory on each Master Node using the following commands:

cp -r /opt/openvidu/backups/<DATE>_<VERSION>/* /opt/openvidu
/usr/local/bin/store_secret.sh save OPENVIDU_VERSION "<VERSION>"

Where <DATE> and <VERSION> are the date and version of the backup you want to restore. For example:

cp -r /opt/openvidu/backups/2025-02-12-09-50-46_3.0.0/* /opt/openvidu
/usr/local/bin/store_secret.sh save OPENVIDU_VERSION "3.0.0"

Note the store_secret.sh command at the end. This is required to update the OPENVIDU_VERSION secret in the OCI Vault, which the Oracle Cloud Infrastructure deployment uses to determine which version of OpenVidu should be running on the Media Nodes. The store_secret.sh command only needs to be run once from any Master Node, but the cp step must be repeated on every Master Node to restore its configuration files.

Remember to terminate the Media Nodes after rolling back so that the Instance Pool can launch new Media Nodes with the restored configuration. You can do this from the OCI Console by navigating to the Compute → Instance Pools section, opening <STACK_NAME>-media-pool, and terminating the existing Media Node instances.

Recommendations#

Always upgrade all nodes in your OpenVidu High Availability deployment. Running mismatched versions across Master Nodes may cause compatibility issues.
If you encounter any problems during an upgrade, a full redeployment is always the recommended path to a clean installation.
Keep your Docker and Docker Compose versions up to date.
Remove unused images and containers to free up disk space. For example, once the upgrade is complete and OpenVidu is running, you can remove old images with the following command on each Master Node:
```
docker image prune -a
```
This command will remove all the images that are not being used by any container.