3 Upgrade of Oracle CNC Solution deployed on Non-Oracle CNE

This chapter provides information about Oracle Cloud Native Core (CNC) Solution upgrade when deployed on Non-Oracle cloud native environment.

3.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 non-Oracle cloud native environment or infrastructure.

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 Oracle CNC Solution on non-Oracle CNE, perform the upgrade procedure in the following sequence:

Figure 3-1 Oracle CNC Solution Upgrade Order on Non-Oracle CNE


Oracle CNC Solution Upgrade Order on Non-Oracle CNE

See CNC NFs and Companion components installation, upgrade, and fault recovery guides for details on upgrading the respective components.

3.2 Planning Upgrade

This section explains the planning for upgrading CNC NFs and Companion components deployed on non-Oracle cloud native environment.

3.2.1 General Guidelines

Oracle recommends the following guidelines:

  • Perform upgrade testing in sandbox or lab deployment before testing in production sites.
  • Follow the upgrade sequence outlined in the Figure 1-1 section.
  • Upgrade all components to their target release, as per the compatibility matrix provided in the CNC release notes.
  • In a multisite deployment model, perform the upgrade of one site at a time. Follow the sequence mentioned in Figure 3-1 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.

  • 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 Figure 3-1.
  • Ensure that CNC Console and NF versions are compatible with OCCM before upgrade.
  • 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.

3.2.2 Preupgrade Checklist

Go through the following checklist before performing an upgrade.

3.2.2.1 Resource Requirement

This section details about the resources required to upgrade a non-Oracle cloud native environment, CNC NFs, and Companion components.

3.2.2.1.1 Cloud Native Environment

Ensure that the number of planned resources required for NF, CNC Console, and cnDBTier are available during the non-Oracle cloud native environment upgrade.

For more information on non-Oracle cloud native environment resource requirements, see the installation and upgrade guide provided by the non-Oracle cloud native environment vendor.

3.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 or Companion components requires additional resources due to changes in architecture or service model.

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

3.2.2.2 Prerequisites

Ensure that you have the following prerequisites before performing an upgrade:

  • Keep the backup of the following artifacts from your recent successful installation handy:
    • custom values.yaml file
    • servicemesh-config-custom-values.yaml file, if any
    • Updated helm charts
    • Secrets
    • Certificates
    • Keys used
  • See CNC Console, OCCM, NF, cnDBTier, and OSO guides for preupgrade task details before upgrading respective components.
  • Refer to customer-specific non-Oracle cloud native environment Upgrade document for preupgrade tasks.

3.2.3 Upgrade Workflow

The following diagram details the upgrade sequence if you are using a non-Oracle CNE.

3.2.3.1 CNC NFs and Companion Components Upgrade

This section explains the upgrade workflow of CNC NFs and Companion Components deployed on Non-Oracle cloud native environment.

Figure 3-2 CNC NFs and Companion components Upgrade on Non-Oracle cloud native environment


CNC Console, OCCM, NF, and cnDBTier Upgrade with Non-Oracle cloud native environment

The following procedure explains the upgrade workflow for CNC NFs and Companion Components:

  1. Check the supported upgrade path for each CNC NFs and Companion Components. To know the upgrade path, see Oracle Communications Cloud Native Core Release Notes.

    Note:

    It is recommended to upgrade in the similar supported upgrade path of the Upgrade Workflow.
  2. Check for the compatibility of the target CNC component. See Compatibility check of target NF component with installed CNE section for the procedure.
  3. If the CNC components are not compatible, upgrade non-Oracle cloud native environment.
  4. If all CNC components are compatible, upgrade the components based on the upgrade sequence mentioned in Upgrade Workflow section.
  5. Run the Helm test command to check the upgrade status. In case of any failure, contact My Oracle Support.
  6. Once the Helm test is successful, then the upgrade is complete.
  7. Perform the above upgrade steps in the production environment.
3.2.3.2 Compatibility Check of Target NF Component with Installed Non-Oracle cloud native environment

Follow the procedure to check the compatibility of target NF component with installed Non-Oracle cloud native environment:

  1. Run the following command to get the list of resource versions for the installed non-Oracle cloud native environment release:
    kubectl api-resources --sort-by='name’ (or kubectl api-versions)

    Sample output:

    
serviceaccounts                   sa           v1                                     true         ServiceAccount
serviceentries                    se           networking.istio.io/v1beta1            true         ServiceEntry
servicemonitors                                monitoring.coreos.com/v1               true         ServiceMonitor
services                          svc          v1                                     true         Service
sidecars                                       networking.istio.io/v1beta1            true         Sidecar ...
...
...
...
  2. Run the following command to get the list of target CNC Console, OCCM, NF, cnDBTier, and OSO resources and their versions:
    helm upgrade <helm release> <chart tarball> -f <ASM Custom File> -n <helm release> --dry-run | egrep -i "^apiVersion:|^kind:" |sed 's/\r$//' | awk '{ ORS = (NR%2 ? ", " : RS) } 1' | sort | uniq

    For example:

    helm upgrade ocpcf-lp  occnp-23.2.0-od-20230210.tgz -f occnp-23.2.0-nb-20230127-custom-values-pcf-ASM.yaml -n ocpcf-lp --dry-run | egrep -i "^apiVersion:|^kind:" |sed 's/\r$//' | awk '{ ORS = (NR%2 ? ", " : RS) } 1' | sort | uniq
    Sample output:
     
apiVersion: apps/v1, kind: Deployment
apiVersion: apps/v1, kind: StatefulSet
apiVersion: autoscaling/v1, kind: HorizontalPodAutoscaler
apiVersion: autoscaling/v2beta1, kind: HorizontalPodAutoscaler
apiVersion: autoscaling/v2beta2, kind: HorizontalPodAutoscaler
apiVersion: batch/v1, kind: Job
apiVersion: policy/v1beta1, kind: PodDisruptionBudget
apiVersion: rbac.authorization.k8s.io/v1beta1, kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1, kind: Role
apiVersion: rbac.authorization.k8s.io/v1, kind: RoleBinding
apiVersion: v1, kind: ConfigMap
apiVersion: v1, kind: Service
apiVersion: v1, kind: ServiceAccount
  3. Verify that installed non-Oracle cloud native environment has all Kubernetes resources and their versions required by CNC Console, OCCM, NF, cnDBTier, and OSO.

3.3 Performing the NF Upgrade

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

Table 3-1 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 3-2 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

3.3.1 Non-Oracle Cloud Native Environment Upgrade

Figure 3-3 Non-Oracle CNE Upgrade


Non-Oracle CNE Upgrade

The following procedure explains the upgrade workflow for non-Oracle cloud native environment:

  1. Check for the compatibility of the target NF component. Refer to Compatibility check of target NF component with installed CNE section for compatibility check procedure.
  2. Check for resource requirements detail for worker nodes upgrade in vendor-specific cloud native core documentation.
  3. Upgrade cloud native core and restart the applications, if required.
  4. Run the Helm test command to check the upgrade status.
  5. Once the Helm test is successful, the upgrade is complete.
  6. Perform the above steps in the production environment.

3.3.2 Compatibility Check of NF Component with Target Cloud Native Environment

Perform the following compatibility checks:

  1. Run the following commands to get the list of deployed resources and their versions from a given CNC Console, OCCM, NF, cnDBTier and OSO release:
    helm get manifest <helm release>  -n <namespace> | egrep -i "^apiVersion:|^kind:" |sed 's/\r$//' | awk '{ ORS = (NR%2 ? ", " : RS) } 1' | sort | uniq
    Sample Output:
    
apiVersion: apps/v1, kind: Deployment
apiVersion: apps/v1, kind: StatefulSet
apiVersion: autoscaling/v1, kind: HorizontalPodAutoscaler
apiVersion: autoscaling/v2beta1, kind: HorizontalPodAutoscaler
apiVersion: autoscaling/v2beta2, kind: HorizontalPodAutoscaler
apiVersion: policy/v1beta1, kind: PodDisruptionBudget
apiVersion: rbac.authorization.k8s.io/v1beta1, kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1, kind: Role
apiVersion: rbac.authorization.k8s.io/v1, kind: RoleBinding
apiVersion: v1, kind: ConfigMap
apiVersion: v1, kind: Service
apiVersion: v1, kind: ServiceAccount
  2. Run the following command to get the list of resource versions for the target cloud native environment release:

    Note:

    • See Kubernetes release documentation for supported resources and versions.
    • Alternate approach: From any installed target cloud native environment release, run the following command to get a list of all supported api-versions:
    kubectl api-resources --sort-by='name’ (or kubectl api-versions)
    Sample output:
    
serviceaccounts                   sa           v1                                     true         ServiceAccount
serviceentries                    se           networking.istio.io/v1beta1            true         ServiceEntry
servicemonitors                                monitoring.coreos.com/v1               true         ServiceMonitor
services                          svc          v1                                     true         Service
sidecars                                       networking.istio.io/v1beta1            true         Sidecar ...
...
...
...
  3. Manually ensure that all installed CNC Console, OCCM, NF, cnDBTier, and OSO resources and their versions are available in the target cloud native environment.

3.4 Performing the Postupgrade Tasks

This section explains the postupgrade tasks.

3.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 respective components.

3.4.2 Cloud Native Environment Postupgrade

  • Re-validate the stability of all the components by running "helm test" provided by CNC Console, OCCM, NF, and cnDBTier to verify the deployment health and status.
  • For procedures to perform any restart required by CNC Console, OCCM, NF, cnDBTier, or any other external component, see the component-specific guides or documents.

3.5 Performing the Rollback

Once a rollback is triggered for a component, this section of the guide helps you to decide the order of the rollback for other 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 NFs and CNC Console in a given order.

The following diagram details the rollback sequence:

Figure 3-4 Rollback Sequence with Non-Oracle CNE


Rollback Sequence with Non-Oracle CNE

Table 3-3 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 3-4 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

3.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 and upgrade guides for postrollback task details after rolling back respective components.