Upgrading CNC Console

5 Upgrading CNC Console

This section provides details of CNC Console upgrade procedure to upgrade the following CNC Console components:

M-CNCC IAM
M-CNCC Core
A-CNCC Core

Note:

For OCI

The CNC Console IAM DB Backup is not applicable.

The M-CNCC IAM component is not applicable in OCI deployment.

Note:

Before proceeding with CNC Console helm upgrade to latest, CNC Console database backup must be taken and stored in a location which can be easily restored. For more information, see CNC Console IAM DB Backup.

The following steps must be followed while performing the upgrade:

This section explains about the CNC Console upgrade procedures for single cluster and multicluster deployments. M-CNCC IAM, M-CNCC Core, and A-CNCC Core can be upgraded from current version to the latest version using helm upgrade feature.

User can upgrade and rollback CNC Console from a source release to a target release using CDCS or CLI procedures as outlined in the following table:

		Non OCI Environment		OCI Environment
Upgrade	References	Applicable for CDCS	Applicable for CLI	Applicable for CNC Console deployment using OCI
M- CNCC IAM DB Backup	CNCC IAM DB Backup	Yes	Yes	No
CNC Console Upgrade	CNCC Upgrade	See Oracle Communications CD Control Server Installation and Upgrade Guide	Yes	Yes

Caution:

It is recommended to verify the copy pasted content especially when the hyphens or any special characters are part of copied content.

5.1 Supported Upgrade Paths

This section describes the supported upgrade paths for CNC Console

For more information about supported upgrade paths, see CNC Console Deployment Modes section.

The following table lists the supported upgrade paths for Console:

Table 5-1 CNC Console Upgrade Sequence

Deployment Mode	Source Version	Target Version	Upgrade Sequence
Single Cluster	23.3.x or 23.4.x	24.1.x	Console Upgrade Upgrade CNC Console NF Upgrade Upgrade Instances (NF or CNE/OSO Common Services) cnDbtier Upgrade
Multi Cluster	23.3.x or 23.4.x	24.1.x	Console Manager Upgrade Upgrade CNC Console Console Agent Upgrade Upgrade A-CNCC Core NF Upgrade Upgrade Instances (NF or CNE/OSO Common Services) cnDbtier Upgrade

Deployment Mode

Source Version

Target Version

Upgrade Sequence

Single Cluster

23.3.x or 23.4.x

24.1.x

Console Upgrade

Upgrade CNC Console

NF Upgrade

Upgrade Instances (NF or CNE/OSO Common Services)

cnDbtier Upgrade

Multi Cluster

23.3.x or 23.4.x

24.1.x

Console Manager Upgrade

Upgrade CNC Console

Console Agent Upgrade

Upgrade A-CNCC Core

NF Upgrade

Upgrade Instances (NF or CNE/OSO Common Services)

cnDbtier Upgrade

Note:

For OCI

Starting from version 24.1.0, CNC Console now supports deployment on OCI.
CNC Console multicluser feature is not supported.

Note:

Console should be upgraded first followed by NF for all the supported NFs.
cnDBTier only supports APIs from 23.3.x onwards. Users with a combination of cnDBTier 23.3.x or older, and NF version 23.4.x or newer won't have access to the data in cnDBTier configuration items.

Note:

CNC Console supports N-2 NF versions during upgrade window. For example, CNC Console 24.1.x supports SCP 24.1.x, 23.4.x, and 23.3.x. Any newly added features in Console which have NF dependency in latest release may not be available in previous release.

5.2 Preupgrade Tasks

While upgrading an existing CNC Console deployment, the running set of containers and pods are replaced with the new set of containers and pods. However, if there is no change in the pod configuration, the running set of containers and pods are not replaced.

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 time (depending upon number of Pods to upgrade) to upgrade all the services. In the meantime, you must not press "ctrl+c" to come out from helm upgrade command. It may lead to anomalous behavior.

Preupgrade Steps

Keep current occncc_custom_values_<version>.yaml file as backup, that is
```
occncc_custom_values_<version to be upgraded>.yaml 
```
Update the new custom_values.yaml defined for target CNC Console release. See CNC Console IAM Configuration Parameters section and CNC Console Core Configuration Parameters section for more details about helm configurable parameters.
Install or upgrade the network policies, if applicable. For more information, see Configuring Network Policies.

5.3 CNC Console IAM DB Backup

This section describes the procedure to do the DB backup of CNC Console IAM.

Note:

Not applicable for OCI deployment.

Prerequisites

The prerequisites for the backup process are:

MySQL NDB cluster should be in a healthy state.
Every database node of the MySQL NDB cluster should be in running state.
In case of cnDBTier to verify the prerequisites, check mysql pod is up and running.
In case of VM based DB Tier to verify the prerequisites, log in to MCM client on one of the SQL node of the cluster. Run the following command to check the node status:
```
mcm> show status -r occnendbclustera;
```

Log in to the SQL node and run the following command to take the dump (backup) of the database. The user is required to enter the password.

kubectl exec -i -n <namespace> <sql-node> -- mysqldump --single-transaction --no-tablespaces --no-create-info -h 127.0.0.1 -u <username> -p <database-name> | gzip > <backup_filename>.sql.gz

For example:

kubectl exec -i -n occne-ndb ndbappmysqld-0 -- mysqldump --single-transaction --no-tablespaces --no-create-info
      -h 127.0.0.1 -u cnccusr -p cnccdb | gzip > cnccdbBackup.sql.gz

Note:

The operator must ensure there is enough space on the current directory in order to save the backup file.

5.4 CNC Console Upgrade

This section describes the procedure to upgrade CNC Console.

Note:

Existing release name must be used for upgrade.
mCnccIams port is assumed as 80. The mCnccIams port configuration must be added only if port is other than 80.

Prepare occncc_custom_values_<version>.yaml file for upgrade.

Upgrade CNC Console using existing release release name (cncc-iam or cncc) by running the following command:

$ helm upgrade <cncc_iam_release_name> <helm_chart> -f <occncc_custom_values_<version>.yaml> -n <namespace>

Foe example:

$ helm upgrade cncc ocspf-helm-repo/cncc -f occncc_custom_values_<version>.yaml -n cncc

Check the status of upgrade by running the following command:
```
$ helm status <cncc_iam_release_name> -n <namespace>
```
For example:
```
$ helm status cncc -n cncc
```

5.5 Post Upgrade Tasks

This section describes the tasks to be performed after an upgrade.

5.6 Parameters and Definitions During CNC Console Upgrade

Parameters and Definitions during CNC Console Upgrade

Table 5-2 Parameters and Definitions during CNC Console Upgrade

Parameters	Definitions
<release_name>	CNC Console Helm release deployed. It could be found in the output of 'helm list' command
<namespacename>	CNC Console namespace in which release deployed
<helm_chart>	CNC Console helm chart
<chart_version>	CNC Console helm chart version in case helm charts are referred from helm repo
<helm_repo>	CNC Console helm repo
<occncc_custom_values_<version>.yaml>	CNC Console customized values.yaml for target release.
<occncc_rollback_iam_schema_<version>.sql>	CNC Console DB schema file used for rollback