Sizing for a hybrid deployment
Learn about the sizing requirements for a hybrid deployment on Red Hat® OpenShift® Container Platform.
Hardware sizing for a hybrid deployment on Red Hat OpenShift Container Platform
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.
Trial sizes are provided for limited scenarios, such as proof of concept demonstrations. Do not use trial sizes in a test or production environment.
Note: The sizing tables provide a large production sizing option, which is not currently supported
at installationation time. If you have requirements for a large production sizing installation,
contact your local support team.
Note: Red Hat
OpenShift Container Platform
user-provisioned infrastructure is not sized as part of this sizing. Refer to Red Hat
OpenShift Container Platform documentation for more
details.
Note: If Red Hat
OpenShift Container Platform is
installed on VMware virtual machines, set the value of the
sched.cpu.latencySensitivity parameter to high.| General sizing information | ||||
|---|---|---|---|---|
| Category | Resource | Trial | Production | Large production sizing |
| ObjectServer Event Management sizing information | ||||
| Event Rate Throughput | Steady state events per second | 20 | 600 | 600 |
| Burst rate events per second | 100 | 600 | 600 | |
| Standing event count | 10,000 | 200,000 | 200,000 | |
| Max concurrent users | 5 | 50 | 130 | |
| Cloud Native Event Analytics sizing information | ||||
| Event Rate Throughput* | Steady State Events per second | 20 | 600 | 600 |
| Burst Rate Events per second | 100 | 600 | 600 | |
| Topology Management sizing information | ||||
| System size | Approx. resources | 200,000 | 5,000,000 | 15,000,000 |
| Number of groups | 1,000 | 30,000 | 30,000 | |
| Metric Anomaly Detection sizing information | ||||
| System size | Number of KPIs | 10,000 | 1,000,000 | 2,000,000 |
| Environment options | Minimum metric granularity | 5 minutes | 5 minutes | 5 minutes |
| High availability | No | Yes | Yes | |
| Runbook Automation sizing information | ||||
| Fully automated runbooks | Run per second | 1 | 2 | 4 |
Note: Event rates for Cloud Native Event Analytics assume a deduplication rate of 6 to 1 (17% unique
events) on the ObjectServer.
Note: The requirements are the minimum CPU, memory, and storage requirements for Netcool® Operations Insight® services
only. If these minimum requirements are not in place, do not install the
product.
Note: To avoid outages, a minimum of one extra work node is required for node
maintenance.
| Total hardware requirements Netcool Operations Insight services only | ||||
|---|---|---|---|---|
| Category | Resource | Trial | Production | Large production sizing |
| Resource requirements | Minimum node count | 3 | 7 | 11 |
| vCPUs (Total) | 24 | 98 | 147 | |
| Memory (GB)(Total) | 72 | 224 | 368 | |
| Disk (GB)(Total) | 360 | 840 | 1,260 | |
| Netcool Operations Insight Persistent storage requirements (Gi) | 635 | 7,182 | 12,432 | |
| Total disk IOPS requirements* | 5,000 | 10,000 | 20,000 | |
*You might need to convert IOPS values, depending on your specific network storage solution and
cloud vendor environment. For example, when you provision block storage for Virtual Private Cloud
data volumes, you specify an IOPS profile that best meets your storage requirements. For more
information, see the IOPS tiers 
topic in the IBM Cloud® Virtual Private Cloud documentation. The IOPS specification that you provision should be
suitable for I/O-intensive database workloads.
| Total requirements Netcool Operations Insight including Red Hat OpenShift Container Platform Control plane and Compute nodes | ||||
|---|---|---|---|---|
| Category | Resource | Trial | Production | Large production sizing |
| Resource requirements | Node count | 4 | 10 | 14 |
| vCPUs | 28 | 110 | 159 | |
| Memory (GB) | 88 | 272 | 416 | |
| Disk (GB) | 480 | 1,200 | 1,620 | |
| Persistent storage requirements (Gi) | 635 | 7,182 | 12,432 | |
| Total disk IOPS requirements* | 5,000 | 10,000 | 20,000 | |
Note: These requirements do not include CPU and memory resources for hosting a storage provider, such as Red Hat OpenShift Data Foundation (previously called Red Hat OpenShift Container Storage) or Portworx. These storage providers can require more nodes, resources, or both, to run. The extra resources that are needed can vary based on your selected storage provider.
| Hardware allocation and configuration | ||||
|---|---|---|---|---|
| Category | Resource | Trial | Production | Large production sizing |
|
Red Hat OpenShift control plane (master) nodes Resource requirements per control plane |
Node count | 1 | 3 | 3 |
| vCPUs | 4 | 4 | 4 | |
| Memory (GB) | 16 | 16 | 16 | |
| Disk (GB) | 120 | 120 | 120 | |
| Netcool Operations Insight components - suggested configuration | ||||
|
Red Hat OpenShift compute (worker) nodes Resource requirements per compute node |
Node count | 3 | 7 | 11 |
| vCPUs | 8 | 14 | 14 | |
| Memory (GB) | 24 | 32 | 35 | |
| Disk (GB) | 120 | 120 | 120 | |
| Persistent storage minimum requirements (Gi) | Cassandra | 250 | 4,407 | 5,407 |
| Kafka | 150 | 600 | 1,800 | |
| Zookeeper | 10 | 30 | 30 | |
| Elasticsearch | 150 | 1,275 | 3,525 | |
| File-observer | 5 | 10 | 10 | |
| CouchDB | 20 | 60 | 60 | |
| MinIO | 50 | 800 | 1,600 | |
Extra requirements for offline (airgap) deployments
If you are installing in an air-gapped environment (offline), you must ensure that you have
adequate space to download the Netcool Operations Insight on Red Hat OpenShift images to a
local registry in your offline environment. The Netcool Operations Insight on Red Hat OpenShift images total
31 GB.
- Bastion host method - the local registry and the bastion host must each have at least 31 GB of storage space.
- Portable method - the local registry and the portable device must have at least 31 GB of storage space.
Added ASM disabled numbers in parentheses