2 Upgrade of Oracle CNC Solution deployed on Oracle CNE

This chapter provides information about Oracle Cloud Native Core (CNC) Solution upgrade when deployed on Oracle Communications Cloud Native Environment (CNE).

2.1 Overview

This section provides an overview of upgrade procedures of CNC components. You must complete the preupgrade procedures described in each subsection to ensure that the system is ready for an upgrade.

You can upgrade each Cloud Native Core (CNC) Network Functions (NFs) and Companion components from the specified source release to the target release. Once the required network function is up and running, upgrade infrastructure, followed by CNE upgrade.

Note:

The upgrade procedure for the infrastructure is not covered in this document. For more information about infrastructure upgrades, see the relevant infrastructure document.

If you are using CNC Solution on Oracle CNE, perform the upgrade procedure in the following sequence:

Figure 2-1 CNC Solution Upgrade Order on Oracle CNE


Oracle CNC Solution CNC Upgrade Order on CNE

2.2 Planning Upgrade

The following flow diagram gives a high-level overview of the sequence to be followed for upgrading CNC Solution deployed on CNE.

Figure 2-2 Planning Upgrade of CNC Solution


Planning Upgrade of CNC Solution

The following table lists the supported upgrade sequence:

Table 2-1 Upgrade Sequence

Deployment Mode Source Version Target Version Upgrade Sequence
Single Cluster or Multicluster 24.2.x, 24.3.x 25.1.100
  1. Oracle CNC NFs and Companion components:
    1. CNC Console Upgrade
    2. OCCM Upgrade
    3. CNC NF Upgrade
    4. cnDBTier Upgrade
  2. Infrastructure (if needed)
  3. CNE

2.2.1 General Guidelines

Oracle recommends the following guidelines for upgrading CNC Solution deployed on CNE:

  • Perform upgrade testing in sandbox or lab deployment before testing in production sites.
  • Follow the upgrade sequence outlined in the Figure 1-1 and CNE Upgrade sections.
  • Upgrade all components to their target release, as per the compatibility matrix provided in Oracle Communications Cloud Native Core Release Notes.
  • In a multisite deployment model, perform the upgrade of one site at a time. Follow the sequence mentioned in upgrade sequence to upgrade all the components in the specific site and then proceed to the next site.

    Refer to cnDBTier and NF-specific installation, upgrade, and fault recovery guide for post upgrade steps to verify the health of cnDBTier services and NF components.

  • It is recommended to perform an upgrade of CNC Console, OCCM, NF, and cnDBTier in a single maintenance window. If upgrade takes longer than a single maintenance window, individual components can be upgraded in multiple maintenance windows. Ensure that the upgrade order is followed as per the sequence mentioned in upgrade sequence.
  • Ensure that Console and NF versions are compatible with OCCM before upgrade.
  • Perform infrastucture upgrade, if needed.
  • You can perform a CNE upgrade in multiple maintenance windows. For more information about upgrading CNE, see Oracle Communications Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.
  • If CNE is a shared cluster, upgrade all the instances of CNC Console, OCCM, NF, and cnDBTier before upgrading CNE.
  • If multiple NFs share a cnDBTier, upgrade all the instances of CNC Console, OCCM, and NFs sharing that cnDBTier of the specific site, before upgrading the cnDBTier of the site.
  • Rollback is the reverse order of upgrade.

2.2.2 Preupgrade Checklist

Go through the following checklist before performing an upgrade.

2.2.2.1 Resource Requirement

This section details about the resources required to upgrade CNE, CNC NFs and Companion components.

2.2.2.1.1 Cloud Native Environment

CNE automatically drains its worker nodes while performing the upgrade. When a worker node is drained, Kubernetes safely evicts all of the pods that were hosted on that worker node.

Note:

NF, cnDBTier, and CNC Console support Pod Distribution Budget (PDB) to gracefully handle worker node draining. Thus, based on available resources, a CNE worker node upgrade will happen. Operator needs to ensure that enough resources are available after draining the worker node. For more information on CNE resource requirements, see Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.

2.2.2.1.2 CNC NFs and Companion Components

For CNC NFs and Companion components upgrade, reevaluate resource requirement before performing the upgrade. It is possible that CNC NFs and Companion components require additional resources due to changes in architecture or service model.

For more information on NF resource requirements, see NF-specific installation, upgrade, and fault recovery guides.

2.2.2.2 Prerequisites

Ensure that the following prerequisites are met before performing an upgrade:

  • Verify that all required worker nodes are available for scheduling pods during upgrade. For example, taints applied on worker nodes (for any maintenance activity etc.). Make sure required number of worker nodes are available as per dimensioning before upgrade.
  • Ensure that at least two worker nodes (that is, resource for largest worker node in cluster x 2) worth of total resources are free and available in CNE cluster.
  • Monitor infrastructure related issue (for example, storage or hardware alarms from infrastructure) manually before CNE or Operating System upgrade.
  • Take a backup of the following artifacts after installation of each of the CNC components:
    • custom values.yaml file
    • servicemesh-config-custom-values.yaml file
    • Updated helm charts
    • Secrets
    • Certificates
    • Keys used
  • See CNC Console, OCCM, NF, cnDBTier, and CNE installation and upgrade guides for preupgrade task details before upgrading respective components.

2.2.3 Upgrade Workflow

The section provides details about the upgrade sequence.

See CNC NFs, Companion components, and CNE installation, upgrade, and fault recovery guides for details on upgrading the respective components. The infrastructure upgrade is performed (if needed) after CNC components upgrade and before CNE upgrade.

2.2.3.1 CNC NFs and Companion Components Upgrade

This section describes the upgrade workflow for CNC Components deployed on CNE.

Figure 2-3 CNC Components Upgrade deployed on CNE


CNC Components Upgrade deployed on CNE

The following procedure explains the upgrade work flow for CNC Components:

  1. Check the supported upgrade path for each NF. To know the upgrade path, see Oracle Communications Cloud Native Core Release Notes. Check the upgrade sequence mentioned in the Supported Upgrade Paths for CNC Components except CNE section.

    Note:

    For multisite deployment model, follow the procedure on each site.
  2. Check if all the CNC components support incremental upgrades. If it is not supported, perform one of the following procedure:
    1. perform multiple hop upgrades.
    2. perform a fresh installation after site isolation.
    3. contact My Oracle Support.
  3. Upgrade the CNC components based on the upgrade sequence mentioned in the Planning Upgrade section.
  4. Run the Helm test command to check the upgrade status.
  5. Once the Helm test is successful, then the upgrade is complete.
  6. Perform the above upgrade steps in the production environment.
2.2.3.2 CNE Upgrade

Supported CNE Upgrade Paths

To ensure a smooth and supported upgrade process, follow the upgrade sequence outlined in Figure 2-4 outlines the supported upgrade paths for CNE. It is not recommend to skip intermediate versions, unless explicitly mentioned.

Figure 2-4 Supported CNE Upgrade Paths


Supported CNE Upgrade Paths

CNE Upgrade Workflow

The following flow diagram explains the process for upgrading CNE:

Figure 2-5 CNE Upgrade Procedure


CNE Upgrade Procedure

The following procedure explains the upgrade workflow for Oracle Communications Cloud Native Core, Cloud Native Environment (CNE):

  1. Check the supported upgrade path for CNE. To know the upgrade path, see Oracle Communications Cloud Native Core Release Notes.
  2. Check if CNE supports incremental upgrades. If it is not supported, contact My Oracle Support.
  3. Upgrade the components based on the upgrade sequence mentioned in the Planning Upgrade section.
  4. Check and perform an application pod restart, if required.

    For example: After upgrading the service mesh, restart the application pods of CNC Console, OCCM, NF, and cnDBTier even if they are running on the latest versions.

  5. Run the Helm test command to check the upgrade status.
  6. Once the Helm test is successful, the upgrade is complete.

2.3 Performing the Upgrade

See the following documents for detailed procedures to upgrade the respective components:

Table 2-2 CNC Network Functions Document Reference

CNC Network Functions Document Reference
Oracle Communications Cloud Native Core, Binding Support Function (BSF) Oracle Communications Cloud Native Core, Binding Support Function Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Network Exposure Function (NEF) Oracle Communications Cloud Native Core, Network Exposure Function Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Network Repository Function (NRF) Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Network Slice Selection Function (NSSF) Oracle Communications Cloud Native Core, Network Slice Selection Function Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Converged Policy (Policy) Oracle Communications Cloud Native Core, Converged Policy Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Security Edge Protection Proxy (SEPP) Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Service Communication Proxy (SCP) Oracle Communications Cloud Native Core, Service Communication Proxy Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Unified Data Repository (UDR) Oracle Communications Cloud Native Core, Unified Data Repository Installation, Upgrade, and Fault Recovery Guide

Table 2-3 CNC Companion Components Document Reference

CNC Companion Components Document Reference
Oracle Communications Cloud Native Configuration Console (CNC Console) Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, cnDBTier (cnDBTier) Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Certification Management (OCCM) Oracle Communications Cloud Native Core, Certification Management, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) Oracle Communications Cloud Native Core, Operations Services Overlay Installation and Upgrade Guide

2.4 Performing the Postupgrade Tasks

This section explains the postupgrade tasks.

2.4.1 NF Postupgrade

  • Verify postupgrade of all the CNC NFs and Companion components by running the "helm test" to verify the deployment health and status.
  • See CNC NFs and Companion components installation, upgrade, and fault recovery guides for postupgrade task details after upgrading the respective components.

2.4.2 CNE Postupgrade

For information on CNE postupgrade tasks, see Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.

2.5 Performing the Rollback

Note:

Before rollback contact My Oracle Support to analyze the cause of failure and any possible workarounds.

This section helps you to decide the order of the rollback of the components that were upgraded successfully. For example, a rollback is triggered if the cnDBTier upgrade fails (or validation after an upgrade fails) for any reason, and this guide provides the information to perform the rollback of CNC Components in a given order.

The following diagram details the rollback sequence:

Figure 2-6 Rollback Sequence


Rollback Sequence

The following table lists the supported rollback sequence:

Table 2-4 Rollback Sequence

Deployment Mode Source Version Target Version Rollback Sequence
Single Cluster or Multicluster 25.1.100 24.2.x, 24.3.x
  1. CNE roll back
  2. Infrastructure roll back
  3. CNC NFs and Companion components
    1. cnDBTier roll back
    2. NF roll back
    3. OCCM roll back
    4. CNC Console roll back

See the following documents for detailed procedures to roll back the respective components:

Table 2-5 CNC Network Functions Document Reference

CNC Network Functions Document Reference
Oracle Communications Cloud Native Core, Binding Support Function (BSF) Oracle Communications Cloud Native Core, Binding Support Function Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Network Exposure Function (NEF) Oracle Communications Cloud Native Core, Network Exposure Function Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Network Repository Function (NRF) Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Network Slice Selection Function (NSSF) Oracle Communications Cloud Native Core, Network Slice Selection Function Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Converged Policy (Policy) Oracle Communications Cloud Native Core, Converged Policy Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Security Edge Protection Proxy (SEPP) Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Service Communication Proxy (SCP) Oracle Communications Cloud Native Core, Service Communication Proxy Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Unified Data Repository (UDR) Oracle Communications Cloud Native Core, Unified Data Repository Installation, Upgrade, and Fault Recovery Guide

Table 2-6 CNC Companion Components Document Reference

CNC Companion Components Document Reference
Oracle Communications Cloud Native Configuration Console (CNC Console) Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, cnDBTier (cnDBTier) Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Certification Management (OCCM) Oracle Communications Cloud Native Core, Certification Management, Upgrade, and Fault Recovery Guide
Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) Oracle Communications Cloud Native Core, Operations Services Overlay Installation and Upgrade Guide

2.6 Performing the Postrollback Tasks

Perform the following postrollback tasks:

  • Verify the rollback of all the CNC NFs and Companion components by running the "helm test" to verify the deployment health and status.

  • See CNC NFs and Companion components installation, upgrade, and fault recovery guides for postrollback task details after rolling back respective components.