Sizing for a Netcool Operations Insight on Red Hat OpenShift deployment

Learn about the sizing requirements for a full Netcool Operations Insight on OpenShift deployment.

Hardware sizing for a full deployment on Red Hat OpenShift

Note: vCPU is defined as when one x86 CPU splits each of its physical cores into virtual cores (vCPU). It is assumed that one x86 CPUs physical core can be split into two logical vCPUs.
Table 1. Detailed supported throughput rates for given sized environments.
General sizing information
Category Resource Demo/PoC/Trial Production
Event Management sizing information
Event Rate Throughput Steady state events per second 20 50
Burst rate events per second 100 500
Topology Management sizing information
System size Approx. resources 200,000 1,000,000
Event Rate Throughput Steady state events per second 10 50
Burst rate events per second 10 200
Environment options Container size Trial Production
High availability No Yes
Table 2. This table shows the total hardware requirements for a Netcool Operations Insight (including Event Management & Topology Management) system deployed on a Red Hat OpenShift cluster, including both the Netcool Operations Insight and Red Hat OpenShift related hardware needs. This table is useful for sizing when there is a need to create a new Red Hat OpenShift cluster to deploy the full Red Hat OpenShift and Netcool Operations Insight stack.
Total requirements Netcool® Operations Insight® including Red Hat OpenShift and infrastructure nodes
Category Resource Demo/PoC/Trial Production
Recommended vCPU/MEM/DISK Node count (Recommended 8 12
vCPUs (Recommended) 60 128
Memory (GB) (Recommended) 120 344
Disk (GB) (Recommended) 1400 4000
Minimum vCPU/MEM/DISK Minimum Nodes count 7 11
vCPUs (Min) 52 126
Memory (GB) (Min) 104 336
Disk (GB) (Min) 1300 3500
Persistent storage requirements (Gi)   851 2796
Total disk IOPS requirements   1760 8550
Table 3. This table shows the hardware requirements attributed to the Netcool Operations Insight footprint deployed on Red Hat OpenShift. This table is useful for sizing when there is a Red Hat OpenShift cluster already installed but there is a need to add worker/computer nodes to it to accommodateNetcool Operations Insight.
Total hardware requirements Netcool Operations Insight services only
Category Resource Demo/PoC/Trial Production
Recommended vCPU/MEM/DISK Node count (Recommended) 6 7
vCPUs (Recommended) 48 112
Memory (GB) (Recommended) 96 280
Disk (GB) (Recommended) 600 2100
Minimum vCPU/MEM/DISK Minimum Nodes count 5 7
vCPUs (Min) 40 112
Memory (GB) (Min) 80 280
Disk (GB) (Min) 500 2100
Persistent storage requirements (Gi)   851 2796
Total disk IOPS requirements   1760 8550
Table 4. This table illustrates the recommended resource allocation for the Red Hat OpenShift Infrastructure, Master and Worker nodes, along with the recommended configuration for the disk volumes associated with each persisted storage resource.
Hardware allocation and configuration
Category Resource Demo/PoC/Trial Production

OpenShift infrastructure node

vCPU, disk and memory requirements

 Minimum nodes count 1 1
Recommended nodes count 1 2
vCPUs 2 2
Memory (GB) 8 8
Disk (GB) 500 500

OpenShift control plane (master) node(s)

 

vCPU, disk and memory requirements

 Minimum nodes count 1 3
Recommended nodes count 1 3
vCPUs 4 4
Memory (GB) 16 16
Disk (GB) 300 300
Netcool Operations Insight components - suggested configuration

OpenShift compute (worker) nodes

 

vCPU disk and memory requirements

Minimum nodes count 5 7
Recommended node count 6 7
vCPUs 8 16
Memory (GB) 16 40
Disk (GB) 100 300
Persistent storage minimum requirements (Gi) NCI 5 10
LDAP 1 1
DB2® 5 5
NCO 10 20
Cassandra 200 1500
Kafka 150 300
Zookeeper 15 30
Elasticsearch 450 900
File-observer 5 10
CouchDB 5 15
ImpactGUI 5 5
Persistent storage minimum IOPS requirements (Gi) NCI 100 200
LDAP 50 100
DB2 50 100
NCO 100 200
Cassandra 600 2400
Kafka 300 2400
Zookeeper 50 150
Elasticsearch 300 2400
File-observer 50 100
CouchDB 60 300
ImpactGUI 100 200