Red Hat OpenShift cluster size

When you specify the IBM® Maximo® Application Suite installation parameters, if you want to create a new Red Hat® OpenShift® cluster, you must choose the size of the cluster that you want to create.

Cluster size

Choose a cluster size that is appropriate for the scale of your Maximo Application Suite installation. Consider the Maximo Application Suite applications that you might want to deploy after the installation is complete.
Tip: You can also resize your Red Hat OpenShift cluster after it is provisioned.

For more information, see Requirements and capacity planning.

You can choose to create a small, medium, or large cluster. By default, the cluster that you create spans multiple availability zones. For the node, CPU, and memory dimensions for each cluster size, see the following table:

Cluster size Node type Number of nodes EC2 instance size CPUs per node Total CPUs Memory per node (GB) Total memory (GB)
Small Primary 3 m5.2xlarge 8 24 32 96
  Worker 3 m5.4xlarge 16 48 64 192
  Bootnode and Bastion host 1 t3.small 2 4 2 2
  Infra 3 m5.4xlarge 16 48 64 192
Medium Primary 3 m5.2xlarge 8 24 32 96
  Worker 5 m5.4xlarge 16 80 64 320
  Bootnode and Bastion host 1 t3.small 2 4 2 2
  Infra 3 m5.4xlarge 16 48 64 192
Large Primary 5 m5.2xlarge 8 40 32 160
  Worker 7 m5.4xlarge 16 112 64 448
  Bootnode and Bastion host 1 t3.small 2 4 2 2
  Infra 3 m5.4xlarge 16 48 64 192
Note: The Bootnode is used only during the installation and shutdown after the installation is complete. It is a workstation from which the Red Hat OpenShift cluster deployment, Maximo Application Suite is deployed. Hence, it can be used later to access the deployment files, configurations, logs, or to run the ad hoc actions on the cluster as needed.