2 Deployment Environment

This section provides information about the cloud native infrastructure used for SEPP benchmarking.

The following diagram represents the deployment configurations of SEPP:

Figure 2-1 Deployment Diagram

img/sepp_bm_deployment_24.1.0.png

The details about the deployment configurations are as follows:

  • cnDBTier, cSEPP, pSEPP, perfgo-client, and perfgo-server are deployed in same cluster
  • DNS server is running on a standalone VM in a different cluster
  • cSEPP to pSEPP n32 TLS 1.3 connection is on External IP (metalLB)
  • perfgo-client is sending traffic on SEPP external IP
  • SEPP to perfgo-server connection is using External IP (metalLB)
  • Both SEPP have 30 local PLMNs
  • Network delay of 50 ms on server side

2.1 Overall Summary of Benchmarking Configurations

The following table lists the overall summary of benchmarking configurations.

Overall Summary

Table 2-1 Overall Summary

Summary Values
SL. No Run 1
Execution Time 16 Hours
SEPP Release csepp-24.1.0-rc1 and psepp-24.1.0-rc1
CNC C Release 24.1.0-rc1
cnDBTier Release 24.1.0-rc5
ASM Enabled/Disabled Disabled
OSO Installed Yes
HA Proxy Installed NA
Cluster Hard_head 1
Site 1 (Ingress Traffic) 31K
Site 2 (Egress Traffic) 31K
Overall MPS 62K
Network Delay on server side 50ms
Features Enabled NA
Status PASS
Remarks NA

Note:

The maximum throughput is 62k

2.2 Deployed Components

Deployment Platform

Oracle Communications Cloud Native Environment (OCCNE) 24.1.0 and BareMetal are used for performing benchmark tests.

Observability Services

The following table lists observability services and their versions that are used for SEPP benchmark tests. These services fetch SEPP metrics, alerts, logs, and traces.

Table 2-2 Observability Services

Service Version
Fluentd 1.16.2
Kibana 7.9.3
Prometheus 1.51.1
Grafana 9.5.3
Jaeger 1.52.0

Cloud Native Orchestrator

Kubernetes 1.27.x is used for managing application pods across the cluster.

cnDBTier

cnDBTier 24.1.0 is used for performing benchmark tests.

For more information about above mentioned components, see Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.

2.3 Deployment Resources

The performance and capacity of SEPP can vary based on the chosen environment and how SEPP is deployed. This section provides information about CNE resources used to perform benchmark tests.

2.3.1 Resource Requirements for CNE Observability Services

The following table provides information about the number of pods required by each CNE service.

Table 2-3 Resource Requirements for CNE Observability Services

Service Name Number of Pods
Prometheus Server 1
Prometheus-pushgateway 1
Alert Manager 2
Fluentd 1 per worker node
Prom-node-exporter 1 per worker node
MetalLB speaker 1 per worker node
ES Data/Master 3/3
ES Curator 1
ES-exporter 1
Grafana 1
Kibana 1
kube-state-metrics 1
jaeger-agent 1 per worker node
jaeger-collector 1
jaeger-query 1
rook-ceph-osd 1 for each raw disk available to OS on all worker nodes
rook-ceph-mgr 1
rook-ceph-mon 3
rook-ceph-osd 1