2 Deployment Environment

This section provides information about the cloud native infrastructure used for UDR, SLF, and EIR benchmarking.

2.1 Deployed Components

Deployment Platform

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

Observability Services

The following table lists services that are used for UDR benchmark tests. These services fetch UDR metrics, alerts, logs, and traces. For more information about mentioned software, see Oracle Communications Cloud Native Core, Unified Data Repository Installation, Upgrade, and Fault Recovery Guide

Table 2-1 Observability Services

Service
Opensearch
Fluentd
Kibana
Prometheus
Grafana
Jaeger

Cloud Native Orchestrator

Kubernetes is used for managing application pods across the cluster.

cnDBTier

cnDBTier is used for performing benchmark tests.

For more information about above mentioned components, see Oracle Communications Cloud Native Core, Unified Data Repository Installation, Upgrade, and Fault Recovery Guide.

2.2 Deployment Resources

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

2.2.1 Resource Requirements for CNE Observability Services

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

Table 2-2 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
Opensearch Data/Master	3/3
Opensearch Client	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