3.1 Deployment Profiles

Default Deployment Profile

This profile can stream NFs (SCP, NRF, SEPP) data up to 15K MPS and can be scaled to handle up to 100K MPS for HTTP2 feed when weighted_lb and Filter (Ingress and Egress) are "OFF".

Replication Factor should be "1" and the incoming message size on OCNADD should be less than or equal to 3500K.

Table 3-4 Default Deployment Profile

OCNADD Service Default Deployment Profile

Replication Factor = 1

Message Size = 3500K

FEED Type = HTTP2, Synthetic

vCPU Req vCPU Limit Memory Req (Gi) Memory Limit (Gi) Min Replica Max Replica Partitions Topic Name
ocnaddconfiguration 1 1 1 1 1 1 - -
ocnaddalarm 1 1 1 1 1 1 - -
ocnaddadmin 1 1 1 1 1 1 - -
ocnaddhealthmonitoring 1 1 1 1 1 1 - -
ocnaddscpaggregation (55K) 2 2 4 4 1 4 24 SCP
ocnaddnrfaggregation (15K) 2 2 2 2 1 1 6 NRF
ocnaddseppaggregation (30K) 2 2 4 4 1 2 12 SEPP
ocnaddadapter 3 3 6 6 HTTP:2

SYNTHETIC:1

HTTP:14

SYNTHETIC:9

126 MAIN
ocnaddkafka 6 6 48 48 4 4 - -
zookeeper 1 1 1 2 3 3 - -
ocnaddgui 1 2 1 1 1 2 - -
ocnadduirouter 1 2 1 1 1 2 - -

Note:

  • Four instances of Kafka brokers might be required when running Replication Factor (RF) =2, based on the setup performance. The end-to-end latency might increase when DISK I/O is slow.
  • For DISK I/O, see Disk Throughput Requirements.
  • For Kafka PVC-Storage, see Kafka PVC Storage Requirements.