Requirements for an installation on IBM Cloud Private

If you are installing base Netcool® Operations Insight® on IBM Cloud® Private, then ensure that you have the requisite requirements in place.

Requirements for the installation are listed under the following categories:
Note: The current version of Netcool Operations Insight is compatible with IBM Cloud Private version 3.1.1 and all of the links in this documentation point to that version of the IBM Cloud Private documentation. If you want to view a different version of the IBM Cloud Private documentation, then navigate to IBM Cloud Private documentation: Welcome page and select the desired version.

IBM Cloud Private

The following IBM Cloud Private prerequisites must be met:
  • IBM Cloud Private must be installed.
  • IBM Cloud Private cluster installed and configured with GlusterFS storage system.
  • A set of default ports must be available for the installation of IBM Cloud Private. For more information, see IBM Cloud Private documentation: Default ports.

Platform

The hardware platform on which IBM Cloud Private is installed must be amd64.

Kubernetes can have a mixture of worker node running different architecture, like amd64, s390x (zLinux), and arm8. In order for a Netcool Operations Insight deployment to be successful, you must have sufficient amd64 worker nodes in the cluster.

Minimum requirements for cluster nodes and resources

As a minimum you must have four virtual machines in your Kubernetes cluster dedicated to supporting base Netcool Operations Insight.
Restriction: This minimum configuration will not provide production-like performance; however, it will be sufficient for demonstration purposes.
The virtual machines must be assigned as follows:
  • 1 master/management/proxy/boot node
  • 3 worker nodes
Each worker node must meet the following minimum resource requirements. These values are already specified for each container within the relevant deployment.yaml file.
  • Number of CPUs: 8
  • Memory: 32 Gigabytes
In addition, when you perform the Operations Management on IBM Cloud Private installation you must set the Enable sub-chart resource requests field to false in the IBM Cloud Private GUI, as described in the Installing on IBM Cloud Private topic.
Note: If you are also planning to install Agile Service Manager within the IBM Cloud Private cluster, then extra resources are required. These extra resources are described in the relevant topic in the Agile Service Manager Knowledge Center.
As a guide to help you size your system, here are the values specified on a per pod basis for CPU and memory:
Table 1. CPU and memory values per pod

Pod

Containers

CPU

Memory

Primary Netcool/Impact core server

nciserver

configuration-share

4

2 GiB

Backup Netcool/Impact core server

nciserver

configuration-share

4

2 GiB

Operations Analytics - Log Analysis and Gateway for Message Bus

unity

gateway

configuration-share

2

3 GiB

Dashboard Application Services Hub

webgui

configuration-share

2

2 GiB

Primary ObjectServer

ncoprimary

2

1 GiB

Historical Event database

db2ese

configuration-share

0.5

Default value of 500m in Helm chart

4 GiB

Gateway for JDBC

jdbcgw

0.2

Default value of 200m in Helm chart

1 GiB

Netcool/Impact GUI server

impactgui

configuration-share

0.2

Default value of 200m in Helm chart

1 GiB

Backup ObjectServer and Gateway

ncobackup-agg-b

ncobackup-agg-gate

3

3 GiB

LDAP proxy server

openldap

0.1

Default value of 100m in Helm chart

1 GiB

Proxy

proxy

0.1

Default value of 100m in Helm chart

128 MiB

Storage

You must also provide a shared filesystem for storage purposes. This shared filesystem will be used by the pods in the cluster for their storage needs. In Kubernetes terms, this shared filesystem is known as persistent volume claim (PVC).

Utilities

You must have the following utilities installed on the machine used to connect to the Kubernetes cluster:
  • Kubernetes client
  • Helm client