4 Upgrading OCCM

Note:

It is advisable to back up the OCCM configmap before performing an upgrade or rollback. During an upgrade, the existing configurations or certificates are preserved.

However, in the event of a rollback, any configurations or certificates created during the upgrade will be lost. Therefore, having a backup allows you to reapply these configurations or certificates in future upgrades.

To back up the OCCM configuration, see OCCM Configuration Backup. For restoring the configuration from a backup, see OCCM Configuration Restore.

This chapter provides information about upgrading the OCCM deployment to the latest release. It is recommended to perform OCCM upgrade in a specific order. For more information about the upgrade order, see Oracle Communications Cloud Native Core, Solution Upgrade Guide

Following are the steps to perform upgrade:

  1. Take OCCM configuration backup by taking backup OCCM configmap.
  2. Upgrade OCCM.

Note:

Before proceeding with OCCM helm upgrade, you must backup the latest OCCM configmap and store the backup file in a location from where it can be easily restored.

Overview

You can use the Helm upgrade feature to upgrade OCCM from its current version to the latest version.

You can upgrade or Rollback OCCM from a source release to a target release using CLI procedures as outlined in the following table:

Upgrade/Rollback Task References Supported for CLI
OCCM Configuration Backup NA Yes
OCCM Upgrade See Oracle Communications Cloud Native Core, CD Control Server User Guide Yes

4.1 Supported Upgrade Paths

The following table lists the supported upgrade paths for OCCM:

Table 4-1 Supported Upgrade Paths

Source Release Target Release Upgrade Sequence Comments
24.2.x or 24.1.x 24.3.x
  • CNC Console
  • OCCM
  • NF
  • cnDBTier

  • CNC Console should be upgraded before OCCM.

  • Helm upgrade OCCM using existing release name.

4.2 Preupgrade Tasks

This section provides information about preupgrade tasks to be performed before upgrading OCCM.

Caution:

  • No configuration should be performed during upgrade.
  • Do not exit from helm upgrade command manually. After running the helm upgrade command, it takes some amount of time (depending upon number of PODs to upgrade) to upgrade all of the services. In the meantime, you must not press "ctrl+c" to come out from helm upgrade command. It may lead to anomalous behavior.

Note:

  1. Keep current occm_custom_values_<version>.yaml file as backup, that is occm_custom_values_<version to be upgraded>.yaml.
  2. Update the new custom_values.yaml defined for target OCCM release. See OCCM Parameters section in Configuration Options for more details about helm configurable parameters.
  3. OCCM certificate configuration from version 24.1.0 onwards supports ecCurve SECP256k1 as it is a few bits weaker than SECP256r1. If there are any certificate configurations with ecCurve SECP256k1, the certificate has to be deleted before performing upgrade.
  4. OCCM 24.1.0 onwards issuer configuration supports only unique server URLs. If there are any issuer configurations with same server URLs, then those issuer and corresponding certificates should be deleted before upgrade.

Preupgrade steps:

  1. Keep current occm_custom_values_<version>.yaml file as backup, that is occm_custom_values_24.2.0.yaml.
  2. Update the new custom_values.yaml defined for target OCCM release. For more details about Helm configurable parameters, see Configuration Options.

4.2.1 OCCM Configuration Backup

OCCM configurations are stored in configmap. You must take a backup before performing upgrade. These backups can be used to restore the OCCM configuration data.

To perform the backup, run the following command to create a temporary directory and save the json file containing configmap data. This can be used if there is any issue with the configmap data.
  1. Log in to the deployment cluster and run the following command to take the data backup of the configmap:
    kubectl get cm <configmap name> -n <namespace> -o json > <backup_filen_name>_backup.json
  2. Run the following command to verify the OCCM configmap name:
    $ kubectl get cm <configmap name> -n <namespace>
    For example:
    $ kubectl get cm occm-occm -n occm
  3. Run the following command to backup OCCM configmap:
    $ kubectl get cm <configmap name> -o json -n <namespace>  > occm-config-map_<version>_backup.json
    For example:
    $ kubectl get cm occm-occm -o json -n occm > occm-config-map_24.2.0_backup.json

Note:

You are recommended to take a periodic backup of configmap.

4.3 Upgrade Tasks

This section describes the procedure to upgrade OCCM to the latest release.

  1. Prepare occm_custom_values_<version>.yaml file for upgrade.
  2. Run the following command to upgrade OCCM using existing release release name:
    $ helm upgrade <occm_release_name> <helm_chart> -f <occm_custom_values_<version>.yaml> -n <namespace>
    For example:
    $ helm upgrade occm ocspf-helm-repo/occm -f occm_custom_values_<version>.yaml -n occm
  3. Run the following command to check the status of upgrade:
    $ helm status <occm_release_name> -n <namespace>
    For example:
    $ helm status occm -n occm

Note:

You must use the existing release name for upgrade or rollback.

4.4 Post Upgrade Tasks

This section provides the steps to be performed after upgrading OCCM.

For information on verifying OCCM Installation, see Verifying Installation

4.4.1 Parameters and Definitions During OCCM Upgrade

Table 4-2 OCCM Upgrade Parameters and Definitions

Parameters Definitions
<release_name> OCCM Helm release deployed. It could be found in the output of 'helm list' command
<namespace> OCCM namespace in which release deployed
<helm_chart> OCCM helm chart
<chart_version> OCCM helm chart version in case helm charts are referred from helm repo
<helm_repo> OCCM helm repo
<occm_custom_values_<version>.yaml> OCCM customized values.yaml for target release