The Ops Center is a system-level infrastructure that provides the following functionality:

• A user interface to trigger a deployment of micro-services with the flexibility of providing variable helm chart parameters to control the scale and properties of Kubernetes objects (deployment, pod, services, and so on) associated with the deployment.

• A user interface to push application specific configuration to one or more micro-services through Kubernetes configuration maps.

• A user interface to issue application-specific execution commands (such as, show commands and clear commands). These commands:

  • invoke some APIs in application-specific pods

  • display the information returned by the application on the user interface

NRF uses the Ops Center infrastructure to deploy its helm charts. The NRF Ops Center has its own render.yaml file (helm template file).

The SMI platform is responsible for deploying and managing the Cloud Native 5G NRF application and other network functions.

For deploying NRF Ops Center on a vCenter environment, see Deploying and Upgrading the Product section in the UCC SMI Cluster Deployer Operations Guide.

For deploying NRF Ops Center on a OpenStack environment, see UAME-based VNF Deployment section in the UAME-based 4G and 5G VNF Deployment Automation Guide, Release 6.9

You can connect to the NRF Ops Center through SSH or the web-based CLI console.

• SSH:

  ssh admin@ops_center_pod_ip -p 2024

• Web-based console:

  1. Log in to the Kubernetes master node.

  2. Run the following command:

     kubectl get ingress <namespace>

     The available ingress connections get listed.

  3. Select the appropriate ingress and access the NRF Ops Center.

  4. Access the following URL from your web browser:

     cli.<namespace>-ops-center.<ip_address>.nip.io

By default, the Day 0 configuration is loaded into the NRF.

To configure the IP address and port of the NRF rest endpoint, use the following sample configuration:

config 
   cdl datastore datastore_name 
      endpoint sbi 
         interface { auth | disc | mgmt } 
            loopbackPort port_number 
            api-root api_string 
         exit 

NOTES:

• endpoint sbi : Specifiy the service-based interface (SBI) as the endpoint.

• interface { auth | disc | mgmt } : Specify the NRF authentication, NRF discovery, or NRF management interface.

• loopbackPort port_number : Specify the internal port number of the loopback host. The NRF uses this port for NF status notification.

• api-root api_string : Specify the API prefix of the deployment-specific service that is used within { apiRoot }.

Configuration Example

The following is an example configuration.

config
 cdl datastore session
  endpoint sbi
   interface mgmt
    loopbackPort 8094
    api-root  root
    exit
   interface disc
    loopbackPort 8095
    api-root  root
    exit
 

To configure the NRF service engine, use the following sample configuration:

config 
   cdl datastore datastore_name 
      endpoint service 
         nodes nodes_number 
         replicas replicas_number 
         exit 
      exit 
   k8 nrf local datastore-endpoint datastore_ep 
   nrf-profile instance-id nrf_instance_id 
   nrf-profile plmn-ids hplmn_id 
      is-home { false | true } 
      mcc mcc_value 
      mnc mnc_value 
      exit 
   nrf-profile profile-settings { nf-heartbeat-timer-seconds heartbeat_timer | nf-discovery-validity-period validity_period | nf-heartbeat-grace-time-seconds grace_time | suspended-nf-profile-purge-time-mins suspended_time } 
   end 

NOTES:

• nodes nodes_number : Specifiy the number of nodes for the service endpoint. To deploy the pods on different worker nodes, set the nodes parameter.

• replicas replicas_number : Specify the number of instances for the service endpoint.

• k8 nrf local datastore-endpoint datastore_ep : Specify the datastore endpoint for NRF local configuration.

• nrf-profile instance-id nrf_instance_id : Specify the NRF instance ID.

• nrf-profile plmn-ids plmn_id : Specify the NRF Home PLMN ID.

• is-home { false | true } : Specify whether it is home PLMN or not. Default value: false .

• mcc mcc_value : Specify the PLMN ID Mobile Country Code (MCC) as a 3-digit integer.

• mnc mnc_value : Specify the PLMN ID Mobile Network Code (MNC) as a 2- or 3-digit integer.

• nrf-profile profile-settings { nf-heartbeat-timer-seconds heartbeat_timer | nf-discovery-validity-period time_period | nf-heartbeat-grace-time-seconds heartbeat_grace_time | suspended-nf-profile-purge-time-mins suspended_time_period } : Specify the NRF NF profile settings.

  • nf-heartbeat-timer-seconds heartbeat_timer : Specify the time in seconds after which NF should update NRF if it is alive. heartbeat_timer must be an integer in the range of 1 to 2592000. Default value: 300 seconds.

  • nf-discovery-validity-period validity_period : Specify the time in minutes after which an NF should do discovery again. validity_period must be an integer in the range of 30 to 1440. Default Value: 180 minutes.

  • nf-heartbeat-grace-time-seconds grace_time : Specify the time in seconds after which NRF would mark the NF instance SUSPENDED if NF does not update NRF. grace_time must be an integer in the range of 0 to 86400. Default value: 300 seconds.

  • suspended-nf-profile-purge-time-mins suspended_time : Specify the time in minutes after which a suspended NF profile will be removed from the NRF profile database. suspended_time must be an integer in the range of 5 to 43200. Default value: 1440 minutes.

Configuration Example

The following is an example configuration.

config
 endpoint service
  nodes    3
  replicas 2
  exit
 k8 nrf local datastore-endpoint datastore-ep-session:8882
 nrf-profile instance-id      350f9d40-7c99-412e-bea1-5db52f7c0bf4
 nrf-profile plmn-ids hplmn
  is-home true
  mcc     123
  mnc     456
  exit
 nrf-profile plmn-ids roam-plmn
  is-home false
  mcc     789
  mnc     45
  exit
 nrf-profile profile-settings nf-heartbeat-timer-seconds 300
 nrf-profile profile-settings nf-discovery-validity-period 12
 nrf-profile profile-settings nf-heartbeat-grace-time-seconds 300
 nrf-profile profile-settings suspended-nf-profile-purge-time-mins 5

To configure the replica and shard count for the profile database and subscription database, use the following sample configuration:

config 
   cdl zookeeper replica replica_number 
   cdl datastore datastore_name 
      index { map map_value | write-factor write_factor } 
      slot { replica replica_number | map map_shards_number | write-factor write_factor } 
      exit 
   cdl kafka replica replica_number 
   k8 label cdl-layer key label_key value label_value 
   exit 

NOTES:

• cdl zookeeper replica replica_number : Specify the number of HA instances to be created for the CDL zookeeper configuration.

• cdl datastore datastore_name : Configure the CDL datastore.

• index { map map_value | write-factor write_factor } : Specify the configuration for index pods.

  • map map_value : Specifiy the number of partitions to be created for an index. map_value must be an integer in the range of 1–1024. Default value: 1.

  • write-factor write_factor : Specify the number of copies to be written into an index before successful response. write_factor must be an integer in the range of 0–2. Default value: 1.

    Note	This keyword is deprecated.

• slot { replica replica_number | map map_shards_number | write-factor write_factor } : Specify the configuration for slot pods.

  • replica replica_number : Specify the number of HA instances to be created in a slot. replica_number must be an integer in the range of 1–4. Default value: 1.

  • map map_shards_number : Specify the number of partitions to be created in a slot. map_shards_number must be an integer in the range of 1–1024. Default value: 1.

  • write-factor write_factor : Specify the number of copies to be written into a slot before successful response. write_factor must be an integer in the range of 0–16. Ensure that the value is lower than or equal to the number of replicas. Default value: 1.

• cdl kafka replica replica_number : Specify the number of kafka replicas. replica_number must be an integer in the range of 1–16. Default value: 2.

• k8 label cdl-layer key label_key value label_value : Specify the K8 CDL layer configuration.

Configuration Example

The following is an example configuration.

config
  cdl zookeeper replica 1
  cdl datastore session
    index map 1
    index write-factor 1
    slot replica 1
    slot map 1
    slot write-factor 1
    exit
  cdl kafka replica 1
  k8 label cdl-layer key disktype value ssd
  exit

To configure the logging service, use the following sample configuration:

config 
   logging level { application | monitor-subscriber | tracing | transaction } { trace | debug | info | warn | error | off } 
   exit 

NOTES:

• logging level { application | monitor-subscriber | tracing | transaction } { trace | debug | info | warn | error | off } : Specify the logging level service and configure the logging level.