The SMI Ops Center is the platform to deploy cnBNG cluster with the offline or online repository. It is mandatory to deploy the SMI Ops Center to install the BNG Ops Center.

The cnBNG is built on the Kubernetes cluster strategy, which implies that it has adopted the native concepts of containerization, high availability, scalability, modularity, and ease of deployment. To achieve the benefits offered by Kubernetes, cnBNG uses the construct that includes the components such as pods and services.

Depending on the deployment environment, the cnBNG deploys the pods on the virtual machines that you have configured. Pods operate through the services that are responsible for the intra-pod communications. If the machine hosting the pods fail or experiences network disruption, the pods are terminated or deleted. However, this situation is transient and BNG spins new pods to replace the invalid pods.

The following workflow provides a high-level visibility into the host machines, and the associated pods and services. It also represents how the pods interact with each other. The representation might defer based on your deployment infrastructure.

The following figure shows the cnBNG cluster pod layout.

Kubernetes deployment includes the kubectl command-line tool to manage the Kubernetes resources in the cluster. You can manage the pods, nodes, and services.

For generic information on the Kubernetes concepts, see the Kubernetes documentation.

The following sections provide more information on the Kubernetes components in cnBNG.

This section describes how to associate a pod to the node based on their labels.

After you have configured a cluster, you can associate pods to the nodes through labels. This association enables the pods to get deployed on the appropriate node based on the key-value pair.

Labels are required for the pods to identify the nodes where they must get deployed and to run the services. For example, when you configure the protocol-layer label with the required key-value pair, the pods are deployed on the nodes that match the key-value pair.

To associate pods to the nodes through the labels, use the following configuration:

1. To associate pods to the nodes through the labels, use the following configuration:

   config 
   k8 label protocol-layer key key_value vm-type value protocol 
   exit   
   k8 label service-layer key key_value vm-type value service 
   exit   
   k8 label cdl-layer key key_value vm-type value cdl 
   exit   
   k8 label oam-layer key key_value vm-type value oam 
   exit   
   

NOTES:

• If you opt not to configure the labels, then BNG assumes the labels with the default key-value pair.

  • k8 label protocol-layer key key_value vm-type value protocol : Configures the key value pair for protocol layer.

  • k8 label service-layer key key_value vm-type value service : Configures the key value pair for the service layer.

  • k8 label cdl-layer key key_value vm-type value cdl : Configures the key value pair for CDL.

  • k8 label oam-layer key key_value vm-type value oam : Configures the key value pair for OAM layer.

To configure the cnBNG pod layout when the virtual machine is short of CPU and memory resources, use the following sample configuration:

config 
   instance instance-id instance_id 
      endpoint sm 
         cpu { max-process max_os_threads | request cpu_resource_request } 
         memory { limit max_memory_resource | request memory_resource_request } 
         end 

NOTES:

• cpu { max-process max_os_threads | request cpu_resource_request } : Enable the K8s pod CPU configuration.

  • max-process max_os_threads : Specify the maximum number of parallel OS threads to use. max_os_threads must be an integer in the range of 1 to 32.

  • request cpu_resource_request : Specify the CPU resource request in millicores. cpu_resource_request must be an integer in the range of 100 to 1000000.

• memory { limit max_memory_resource | request memory_resource_request } : Enable the K8s pod memory configuration.

  • limit max_memory_resource : Specify the maximum number of used memory resources in megabytes. max_memory_resource must be an integer in the range of 100 to 200000.

  • request memory_resource_request : Specify the memory resource request in megabytes. memory_resource_request must be an integer in the range of 100 to 200000.

To configure event tracing, use the following sample configuration:

config 
   subscriber [ event-trace-disable | event-trace-max-count event_trace_count ] 
   end 

NOTES:

• event-trace-disable : Disable subscriber event tracing. cnBNG uses event traces for session level event history in CDL records.

• event-trace-max-count event_trace : Specify the number of entries in event tracing.

  event_trace must be an integer in the range of 1 to 8192. Default value: 100.