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.

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 custom sizing option, which is not currently supported at install time. If you have requirements that meet those for a custom sizing install, contact your local support team.

Note: Red Hat® OpenShift user-provisioned infrastructure is not sized as part of this sizing. Please refer to Red Hat OpenShift documentation for more details.

Note: If Red Hat OpenShift is installed on VMware virtual machines, set the value of the sched.cpu.latencySensitivity parameter to high.

Table 1. Detailed supported throughput rates for given sized environments.
General sizing information
Category	Resource	Trial	Production	Custom sizing
Event Management sizing information
Event Rate Throughput	Steady state events per second	20	100	100
Event Rate Throughput	Burst rate events per second	100	500	500
Topology Management sizing information
System size	Approximate resources	200,000	5,000,000	15,000,000
System size	Number of groups	1,000	30,000	30,000
Metric Management sizing information
System size	Number of metrics	10,000	100,000	100,000
Environment options	Minimum metric granularity	5 minutes	5 minutes	5 minutes
Environment options	High availability	No	Yes	Yes
Runbook Automation sizing information
Fully automated runbooks	Run per second	1	2	Note: 4 runs per second for a large production environment

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 additional work node is required for node maintenance.

Table 2. 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/compute nodes to it to accommodate Netcool Operations Insight.
Total hardware requirements Netcool Operations Insight services only
Category	Resource	Trial	Production	Custom sizing
Resource requirements	Node count	3	6	9
	vCPUs	24	84	126
	Memory (GB)	72	210	315
	Disk (GB)	360	720	1080
Persistent storage requirements (Gi)		611	5921	10371
Total disk IOPS requirements*		5000	10000	20000

*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 external icon topic in the IBM Cloud Virtual Private Cloud documentation. The IOPS specification that you provision should be suitable for I/O-intensive database workloads.

Table 3. This table shows the total hardware requirements for a Netcool Operations Insight (including Event Management, Metric 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 Control plane and Compute nodes
Category	Resource	Trial	Production	Custom sizing
Resource requirements	Nodes count	4	9	12
	vCPUs	28	96	138
	Memory (GB)	88	258	363
	Disk (GB)	480	1080	1440
Persistent storage requirements (Gi)		611	5921	10371
Total disk IOPS requirements*		5000	10000	20000

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.

Table 4. This table illustrates the recommended resource allocation for the Red Hat OpenShift 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	Trial	Production	Custom sizing
OpenShift control plane (master) node(s) 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
OpenShift compute (worker) nodes Resource requirements per compute node	Node count	3	6	9
	vCPUs	8	14	14
	Memory (GB)	24	35	35
	Disk (GB)	120	120	120
Persistent storage minimum requirements (Gi)	NCI	10	20	20
	LDAP	1	1	1
	NCO	10	20	20
	Cassandra	250	3900	4900
	Kafka	150	600	1800
	Zookeeper	10	30	30
	Elasticsearch	150	1275	3525
	File-observer	5	10	10
	CouchDB	20	60	60
	ImpactGUI	5	5	5

Additional 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 39 GB.

Bastion host method - the local registry must have at least 39 GB of storage space.
Portable compute device method - the local registry must have at least 39 GB of storage space.
Portable storage device method - the local registry must have at least 39 GB of storage space.