1. Cloud Native Core Console Network Impact Report
  2. Introduction

1 Introduction

Purpose and Scope

The purpose of this document is to highlight the changes made in CNC Console from Release 22.2.x to Release 22.3.x. These changes may have an impact on the customer network operations and should be considered by the customer while planning the deployment.

CNC Console Compatibility Matrix

The following table provides the list of network functions that are compatible with CNC Console 22.3.x:

Release 22.3.2

Table 1-1 Compatibility Matrix

Network Functions Compatible Versions
BSF 22.3.x
NRF 22.3.x
NSSF 22.3.x
Policy 22.3.x
SCP 22.3.x
SEPP 22.3.x
UDR 22.3.x

Table 1-2 Compatibility Matrix

Components Compatible Versions
CNE 22.1.x, 22.2.x, 22.3.x
cnDBTier 22.1.x, 22.2.x, 22.3.x
CDCS 22.3.x
OSO 1.6.2, 1.10.x, 22.3.x
ASM 1.4.6-am9, 1.6.14-am4, 1.9.8-am1

Common Services Load Lineup

The following table provides the list of added or updated common services load lineup that is compatible with CNC Console 22.3.x:

Release 22.3.2

Table 1-3 Common Services Load Lineup

Common Service Version
Debug-tool 22.3.2
Helm Test 22.3.3
Ingress Gateway 22.3.13
Release 22.3.1

Table 1-4 Common Services Load Lineup

Common Service Version
Debug-tool 22.3.1
Helm Test 22.3.2
Ingress Gateway 22.3.10
Release 22.3.0

Table 1-5 Common Services Load Lineup

Common Service Version
Debug-tool 22.3.0
Helm Test 22.3.1
Ingress Gateway 22.3.4

Software Requirements

This section lists the minimum software requirements to install Oracle Communications CNC Console.

Table 1-6 Software Requirements

Software Version
Kubernetes 1.22.5
HELM 3.8.0
Podman 3.3.1
Prometheus 1.22.5

Orchestration

This section provides information about orchestration changes for CNC Console from release 22.2.x to 22.3.x.

Table 1-7 Orchestration

Orchestration Changes Status Notes
Support for in-service upgrade Yes For information about upgrade and roll back, see Supported Upgrade and Rollback Paths section.

Note: The console microservices are single pod. For information about upgrade and roll back,

see Upgrading CNC Console section in Cloud Native Core Console Installation and Upgrade Guide .
Changes in the custom_values.yaml file Yes For information about changes in the custom_values.yaml file, see Helm section.
Changes in the resource information for custom_values.yaml file Yes For information about changes in the resource requirements, see Resource Requirement section.
Changes in the CSAR package Yes Following changes are made in CSAR package:
  • With this release, two CSAR packages are available:
    • Generic CSAR package
    • Customer-specific CSAR and TGZ package.
  • The uniform naming convention has been followed for the following items across the packages:
    • package name
    • custom_value file name
    • dashboard name
    • alert file name

Note: For more information on specific CSAR changes, contact My Oracle Support.

Changes in Role-Based Access Control (RBAC) policy No No new RBAC policies are added.
Changes in Life Cycle Management (LCM) Operations No No new LCM operations are added.
Helm Test Support Yes Helm Test is supported.

For more information, see Performing Helm Test section in Oracle Communications Cloud Native Core Console Installation and Upgrade Guide.

CNC Console Resource Requirement

This section includes information about CNC Console Resource Requirement.

CNC Console Deployment Resource Usage

Resource usage for CNC Console Single Cluster and Multi Cluster deployment is listed in the following tables.

CNC Console Single Cluster Deployment Resource Usage

Single Cluster Deployment will include M-CNCC IAM, M-CNCC Core and A-CNCC Core components.

CNC Console Common Resource is a common resource needed for manager or agent deployment.

Table 1-8 CNC Console Single Cluster Deployment Resource Usage

Component Limits Requests
CPU Memory (Gi) CPU Memory (Gi)
M-CNCC IAM 7.5 7.5 3.8 3.8
M-CNCC Core 7 7 3.5 3.5
A-CNCC Core 7 7 3.5 3.5
CNCC Common Resource 3 4 1.5 2
Total 24.5 25.5 12.3 12.8

Formula

Total Resource = M-CNCC IAM Resource + M-CNCC Core Resource + A-CNCC Core Resource + CNCC Common Resource

CNC Console Multi Cluster Deployment Resource Usage

Multi Cluster Deployment will include M-CNCC IAM and M-CNCC Core components in Manager cluster. A-CNCC Core component shall be deployed in Manager cluster if there is a local NF.

A-CNCC Core is needed in each Agent cluster for managing local NF. CNCC Common Resource is a common resource needed for manager or agent deployment.

Table 1-9 CNC Console Multi Cluster Deployment Resource Usage

Component Limits Requests
CPU Memory (Gi) CPU Memory (Gi)
M-CNCC IAM 7.5 7.5 3.8 3.8
M-CNCC Core 7 7 3.5 3.5
A-CNCC Core 7 7 3.5 3.5
CNCC Common Resource 3 4 1.5 2
*No Of Agents In Other Clusters 2
Total 37.5 40.5 18.8 20.3

* Assumed number of Agents (A-CNCC Core deployments) for the calculation

Formula

Total Resource = M-CNCC IAM Resource + M-CNCC Core Resource + Common Resources + (No Of Agents In Other Clusters * (CNCC Common Resource + A-CNCC Core Resource))

CNC Console Manager Only Deployment

The following table shows resource requirement for manager only deployment. In this case, agent will be deployed in separate cluster.

Component Limits Requests
CPU Memory (Gi) CPU Memory (Gi)
M-CNCC IAM 7.5 7.5 3.8 3.8
M-CNCC Core 7 7 3.5 3.5
A-CNCC Core 0 0 0 0
CNCC Common Resource 3 4 1.5 2
Total 17.5 18.5 8.8 9.3
CNC Console Agent Only Deployment

The following table shows resource requirement for agent only deployment, in this case manager will be deployed in separate cluster.

Table 1-10 CNC Console Agent Only Deployment

Component Limits Requests
CPU Memory (Gi) CPU Memory (Gi)
M-CNCC IAM 0 0 0 0
M-CNCC Core 0 0 0 0
A-CNCC Core 7 7 3.5 3.5
CNCC Common Resource 3 4 1.5 2
Total 10 11 5 5.5
CNC Console Manager with Agent Deployment

The following table shows resource requirement for manager with agent deployment, in this case agent will be deployed along with manager to manage local NF.

This manager can manage agents deployed in other clusters.

Table 1-11 CNC Console Manager with Agent Deployment

Component Limits Requests
CPU Memory (Gi) CPU Memory (Gi)
M-CNCC IAM 7.5 7.5 3.8 3.8
M-CNCC Core 7 7 3.5 3.5
A-CNCC Core 7 7 3.5 3.5
CNCC Common Resource 3 4 1.5 2
Total 24.5 25.5 12.3 12.8
CNC Console Component wise Resource Usage

Table 1-12 CNCC Common Resource Usage

Microservice Name Containers Limits Requests Comments
CPU Memory CPU Memory
debug_tools tools 1 2 0.5 1 Applicable when debug_tool is enabled
hookJobResources   2 2 1 1 Common Hook Resource
helm test cncc-test         Uses hookJobResources
Total   3 4 1.5 2  

Table 1-13 M-CNCC IAM Resource Usage

Microservice Name Containers Limits Requests Comments
CPU Memory CPU Memory
cncc-iam-ingress-gateway ingress-gateway 2 2 1 1  
  init-service 1 1 0.5 0.5 Applicable when HTTPS is enabled
  update-service 1 1 0.5 0.5 Applicable when HTTPS is enabled
  common_config_hook         common_config_hook not used in IAM
cncc-iam-kc-http kc 2 2 1 1
  init-service 1 1 0.5 0.5 Optional, used for enabling LDAPS
  healthcheck 0.5 0.5 0.3 0.3  
  cnnc-iam--pre-install         Uses hookJobResources
  cnnc-iam-pre-upgrade         Uses hookJobResources
  cnnc-iam-post-install         Uses hookJobResources
  cnnc-iam-post-upgrade         Uses hookJobResources
Total   7.5 7.5 3.8 3.8  

Table 1-14 M-CNCC Core Resource Usage

Microservice Name Containers Limits Requests Comments
CPU Memory CPU Memory
cncc-mcore-ingress-gateway ingress-gateway 2 2 1 1  
  init-service 1 1 0.5 0.5 Applicable when HTTPS is enabled
  update-service 1 1 0.5 0.5 Applicable when HTTPS is enabled
  common_config_hook 1 1 0.5 0.5 Common Configuration Hook container creates databases which are used by Common Configuration Client
cncc-mcore-cmservice cmservice 2 2 1 1  
  validation-hook         Uses common hookJobResources
Total   7 7 3.5 3.5  

Table 1-15 A-CNCC Core Resource Usage

Microservice Name Containers Limits Requests Comments
CPU Memory CPU Memory
cncc-acore-ingress-gateway ingress-gateway 2 2 1 1  
  init-service 1 1 0.5 0.5 Applicable when HTTPS is enabled
  update-service 1 1 0.5 0.5 Applicable when HTTPS is enabled
  common_config_hook 1 1 0.5 0.5 Common Configuration Hook container creates databases which are used by Common Configuration Client
cncc-acore-cmservice cmservice 2 2 1 1  
  validation-hook         Uses common hookJobResources
Total   7 7 3.5 3.5  
CNC Console Microservices Resource Requirement

Table 1-16 CNC Console Microservices Resource Requirement

Microservice Name CPU Per Pod Memory Per Pod (GB) Pod count CPU All Pods - Maximum Memory All Pods - Maximum (GB)
Maximum Maximum Maximum
#cncc-iam-kc-http &$!2.5 &$!2.5 1 2.5 2.5
#cncc-iam-ingress-gateway ^$2 ^$2 1 2 2
#cncc-core-cmservice $2 $2 1 2 2
#cncc-core-ingress-gateway ^$2 ^$2 1 2 2
Total       8.5 8.5
  • #: <helm release name>→ will be prefixed in each Microservice name. Example: if helm release name is "cncc-iam", then ingress-gateway Microservice name will be "cncc-iam-ingress-gateway"

  • ^: CPU Limit/Request Per Pod and Memory Limit/Request Per Pod needs to added as additional resources for init-service and update-service container if TLS needs to be enabled.

    Init-service container's and Common Configuration Client Hook's resources are not counted because the container gets terminated after initialization completes.

    Container Name CPU Request and Limit Per Container Memory Request and Limit Per Container Kubernetes Init Container (Job)
    init-service 1 cpu 1 gb Yes
    update-service 1 cpu 1 gb No
    common_config_hook 1 cpu 1 gb No
    • Update Container service
    Ingress Gateway: For periodically refreshing CNCC Private Key/ Certificate and CA Root Certificate for TLS
    • Init Container service

      Ingress Gateway: To get CNCC Private Key or Certificate and CA Root Certificate for TLS during start up
    • Common Configuration Hook

      CNCC Core Common configuration hook container creates databases which are used by Common Configuration Client

  • &: Helm Hooks Jobs - These jobs are pre and post jobs which are invoked during installation, upgrade, rollback, and uninstallation of the deployment. These are short-lived jobs which get terminated after the work is done. So, they are not part of Active deployment Resource but need to be considered only during installation, upgrade, rollback, and uninstallation procedures.

Container Type CPU Request and Limit Per Container Memory Request and Limit Per Container
Helm Hooks Request - 1 cpu, Limit - 2 cpu Request - 1 gb, Limit - 2 gb

! : Healthcheck Container Service- For monitoring health of the db, extra container is added to the kc pod. This is part of active deployment so additional resource of 0.5 is considered as part of kc pod.

Container Type CPU Request and Limit Per Container Memory Request and Limit Per Container
Health Check Request - 0.3 cpu, Limit - 0.5 cpu Request - 0.3 gb, Limit - 0.5 gb
  • Helm Test Job - This job is run on demand when helm test command is executed. It executes the helm test and stops after completion. These are short-lived jobs which gets terminated after the work is done. So, they are not part of active deployment Resource, but needs to be considered only during helm test procedures.
Container Type CPU Request and Limit Per Container Memory Request and Limit Per Container
Helm Test Request - 1 cpu, Limit - 2 cpu Request - 1 gb, Limit - 2 gb

$ - Troubleshooting Tool Container - If Troubleshooting Tool Container Injection is enabled during CNCC deployment/upgrade, this container will be injected to each CNCC pod (or selected pod, depends on option chosen during deployment/upgrade). These containers will stay till pod/deployment exists.

Container Name CPU Request and Limit Per Container Memory Request and Limit Per Container ephemeral-storage Request and Limit Per Container
ocdebug-tools Request - 0.5 cpu, Limit - 1 cpu Request - 1 gb, Limit - 2 gb Request - 2 gb, Limit - 4 gb