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 (and 64K for synthetic 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 ServiceReplication Factor = 1Message Size = 3500KFEED 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) | 1 | 2 | 1 | 2 | 1 | 2 | 12 | SCP |
| ocnaddnrfaggregation (15K) | 1 | 2 | 1 | 2 | 1 | 1 | 6 | NRF |
| ocnaddseppaggregation (30K) | 1 | 2 | 1 | 2 | 1 | 2 | 12 | SEPP |
| ocnaddadapter | 2 | 3 | 3 | 4 | HTTP:2
SYNTHETIC:1 |
HTTP:13
SYNTHETIC:5 |
117 | MAIN |
| ocnaddkafka | 2 | 5 | 4 | 48 | 4 | 4 | ||
| zookeeper | 1 | 1 | 1 | 2 | 3 | 3 | ||
| ocnaddgui | 1 | 2 | 1 | 1 | 1 | 2 | ||
| ocnadduirouter | 1 | 2 | 1 | 1 | 1 | 2 | ||
| ocnadd-cache | 1 | 1 | 22 | 24 | 3 | 3 |
Note:
- Four instances of Kafka brokers might be required when running 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.
Deployment Profile Kafka and Aggregation
Table 3-5 Deployment Profile Kafka and Aggregation
| OCNADD ServiceReplication Factor = 1Message Size = 3500KFEED Type = HTTP2 | vCPU Req | vCPU Limit | Memory Req (Gi) | Memory Limit (Gi) | Min Replica | Max Replica | Partitions | Topic Name |
|---|---|---|---|---|---|---|---|---|
| ocnaddscpaggregation (41K) | 1 | 2 | 1 | 2 | 1 | 2 | 12 | SCP |
| ocnaddnrfaggregation (9K) | 1 | 2 | 1 | 2 | 1 | 1 | 6 | NRF |
| ocnaddseppaggregation (15k) | 1 | 2 | 1 | 2 | 1 | 1 | 6 | SEPP |
| ocnaddkafka | 2 | 5 | 4 | 24 | 3 | 3 | ||
| zookeeper | 1 | 1 | 1 | 2 | 3 | 3 |
Note:
- Four instances of Kafka brokers might be required when running 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.
Deployment Profile Kafka and Egress Adapter
Table 3-6 Deployment Profile Kafka and Egress Adapter
| OCNADD ServiceReplication Factor = 1Message Size = 3500KFEED Type = HTTP2 | 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 | ||
| ocnaddadapter | 2 | 3 | 3 | 4 | HTTP:2
SYNTHETIC:1 |
8 | 72 | MAIN |
| ocnaddkafka | 2 | 5 | 4 | 24 | 3 | 3 | ||
| zookeeper | 1 | 1 | 1 | 2 | 3 | 3 | ||
| ocnaddgui | 1 | 2 | 1 | 1 | 1 | 2 | ||
| ocnadduirouter | 2 | 2 | 1 | 1 | 1 | 2 | ||
| ocnaddcache | 1 | 1 | 22 | 24 | 2 | 3 |
Note:
- Four instances of Kafka brokers might be required when running 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.