Sizing reference for Agile Service Manager on OCP (Watson AIOps)
This topic only describes the sizing requirements for a stand-alone Private Cloud deployment of Agile Service Manager on RedHat OpenShift Container Platform for IBM Watson AIOps.
Agile Service Manager stand-alone on RedHat OpenShift Container Platform (for Watson AIOps)
Important: The following sizing only applies to a stand-alone deployment of Agile
Service Manager on RedHat OpenShift Container Platform for use with IBM Watson AIOps. For Agile
Service Manager deployment with Netcool Operations Insight, see the NOI Knowledge Center
topics.
Category | Resource | Trial | Production | smallProduction |
---|---|---|---|---|
Event Management sizing information | ||||
Topology Management sizing information | ||||
System size | Approx. resources | 200,000 | 1,000,000 | 70,000 |
Environment options |
Container size |
Trial | Production | smallProduction |
High Availability |
NO | YES | YES |
The following table shows the total hardware requirements for an Agile Service Manager standalone
system deployed on a OCP cluster, including both the Agile Service Manager standalone and OCP
related hardware needs. This information is intended for customers that need to create a new OCP
cluster to deploy the full OCP+ASMstandalone stack.
Category | Resource | Demo/PoC/Trial | Production | smallProduction |
---|---|---|---|---|
Minimum CPU/MEM/DISK |
x86 CPUs |
8 | 45 | 20 |
Memory (GB) |
32 | 120 | 108 | |
Disk (GB) |
240 | 720 | 720 | |
Persistent storage Requirements (Gi) | 820 | 2740 | 480 | |
Requirements | 1300 | 7450 | 7450 |
The following table shows the hardware requirements attributed to the Agile Service Manager
standalone footprint deployed on OCP. This information is useful for customers who already have an
OCP cluster installed, but need to add worker/compute nodes to it to accommodate Agile Service
Manager standalone.
Category | Resource | Demo/PoC/Trial | Production | smallProduction |
---|---|---|---|---|
Minimum CPU/MEM/DISK |
x86 CPUs (Min) |
4 | 33 | 8 |
Memory (GB) (Min) |
16 | 72 | 60 | |
Disk (GB) (Min) |
120 | 360 | 360 | |
Persistent storage Requirements (Gi) | 820 | 2740 | 480 | |
Requirements | 1300 | 7450 | 7450 |
The following table illustrates the recommended resource allocation for the OCP Master and Worker
nodes, along with the recommended configuration for the disk volumes associated with each persisted
storage resource. Worker nodes may be larger when Agile Service Manager standalone is deployed along
with other applications.
Category | Resource | Demo/PoC/Trial | Production | smallProduction |
---|---|---|---|---|
OCP Control Plane (Master) Node(s) | Minimum Nodes Count | 1 | 3 | 3 |
CPU cores and memory requirements | x86 CPUs | 4 | 4 | 4 |
Memory (GB) (Min) | 16 | 16 | 16 | |
Disk (GB) (Min) | 120 | 120 | 120 | |
Agile Service Manager standalone components suggested configuration | ||||
OCP Compute (Worker) Nodes | Minimum Nodes Count | 1 | 3 | 3 |
CPU cores and memory requirements | x86 CPUs | 4 | 11 | 3 |
Memory (GB) | 16 | 24 | 20 | |
Disk (GB) | 120 | 120 | 120 | |
Persistent storage min Requirements (Gi) | Cassandra | 200 | 1500 | 200 |
Kafka | 150 | 300 | 60 | |
Zookeeper | 15 | 30 | 15 | |
Elasticsearch | 450 | 900 | 200 | |
File Observer | 5 | 10 | 5 | |
Persistent storage recommended IOPS Requirements | Cassandra | 600 | 2400 | 2400 |
Kafka | 300 | 2400 | 2400 | |
Zookeeper | 50 | 150 | 150 | |
Elasticsearch | 300 | 2400 | 2400 | |
File Observer | 50 | 100 | 100 |