How to upgrade OPCP
Learn how to upgrade your OVHcloud On-Prem Cloud Platform (OPCP), from downloading the artifacts with the opcp-cli to performing the post-deployment checks
Objective
This guide explains how to upgrade your OVHcloud On-Prem Cloud Platform (OPCP): downloading the new artifacts, upgrading the opcp-cli, applying the new OPCP release, and validating the platform once the upgrade is complete.
Requirements
- An operational OPCP infrastructure.
- Administrative (
root) access to the OPCP control-plane, withopcp-cli,opcp-diag,needrestart,fluxandtfctlinstalled and configured. - Access to the official S31 bucket provided for your OPCP delivery, in order to download the
opcp-cli, the new OPCP bundle, theRELEASE-NOTES, and their corresponding.minisigsignature files.
Instructions
1. Running the pre-deployment checks
On the OPCP control-plane, run opcp-diag to confirm the platform is healthy before starting the upgrade:
If any error is reported, check whether it needs to be fixed before going any further.
2. Downloading the artifacts
Get access to the official S3 bucket in order to download the latest version of:
- the
opcp-cli, - the new OPCP bundle,
- the
RELEASE-NOTESof the versions that will be deployed.
You will also find the corresponding .minisig files in the bucket. They are used to check that the downloaded files are not corrupted before upgrading your OPCP product.
If you are currently using an OPCP product in AirGap mode, you should have received a read-only user to access this bucket. Refer to Use Object Storage with S3cmd to get started with Object Storage.
Once the s3cmd command is configured, you can list the artifacts to download:
Once you have downloaded the required files, push them to one of your OPCP controllers, under the /home/opcp-admin path. In HA mode (3 controllers), the artifacts are automatically synchronized between all the controllers, so you do not need to push the files to every controller.
3. Reading the RELEASE-NOTES
Some versions require manual actions to prepare services before the upgrade.
Read the RELEASE-NOTES carefully, as some actions may be required before the upgrade starts and others after it ends.
4. Upgrading the opcp-cli
If mentioned in the RELEASE-NOTES, upload the new opcp-cli binary and its signature to the remote managed OPCP control-plane.
Then, as root, update opcp-cli:
Remove the uploaded files once the update is confirmed:
5. Upgrading the OPCP artifacts
As root on the remote managed OPCP control-plane, open the configuration file and update the versions:
Update the global version. For example:
Then apply the new release:
The following steps can take up to 30 minutes, depending on what is updated in the release:
- extracting Glance images,
- starting the deployment on the remote nodes,
- executing the deployment of the control plane, which can take up to 10 minutes.
You can follow the detailed logs in /var/log/opcp-cli/opcp-cli.log. To do this, open a new terminal window and run:
6. Performing the final checks
Checking if some services need a restart
Use needrestart to check whether some services need to be restarted:
Restarting services can have an impact on the platform. Only proceed if it is required.
If needed, restart the required services:
Waiting for reconciliation
Wait for the Flux reconciliation to complete and the Terraform runs to finish:
If needed, apply a fix. Sometimes you need to relaunch some pods, so be patient.
Post-deployment checks
On the OPCP control-plane, run opcp-diag again:
If any error is reported, check whether it needs to be fixed.
You can also try to access the UI to confirm that it works properly.
Go further
If you need training or technical assistance implementing our solutions, contact your sales representative or visit our Professional Services page to request a quote and have your project analyzed by our experts.
Join our community of users.
1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud's service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc.