System requirements

The system requirements for installing IBM Fusion software.

The IBM Fusion operators and your workloads run on OpenShift® Container Platform that in turn uses 64-bit Intel, AMD x86, Linux on IBM Z, or Power hardware architecture. For more information about Fusion data services on the different deployment platforms of IBM Fusion, see IBM Fusion Services platform support matrix.

The following table lists the system requirements for IBM Fusion software:

Note: Though there is no minimum number of nodes requirement, the following table provides data based on three control nodes and three compute nodes cluster. However, sizing changes based on the number of nodes for components with "Per node".

Fusion Data Foundation can be deployed on Infra or worker nodes, whereas all other IBM Fusion services including Base must be deployed on worker nodes.

Component	vCPUs	Memory	Storage	GPU
IBM Fusion Base	Request CPU: 4 Limit CPU: 10	Request memory: 4 GiB Limit memory: 13 GiB	Overall storage is a minimum of 500 MB.	For CAS, you need a GPU based solution.
Fusion Data Foundation	Internal mode (Local and dynamic) Request CPU: 22+2(total count of Object Storage Daemon ) Limit CPU: 26 (total count of Object Storage Daemon) External mode Request CPU: 6 Limit CPU: 5 For IBM Power Systems*: Internal mode 48 CPU (logical) External mode 24 CPU (logical)	Internal mode (Local and dynamic) Request memory: 56+5(total count of Object Storage Daemon) GiB Limit memory: 56+5(total count of Object Storage Daemon) GiB External mode Request memory:16 GiB Limit memory: 16 GiB For IBM Power Systems: Internal mode 192 GiB memory External mode 48 GiB memory	Minimum three storage Nodes For more information about Fusion Data Foundation, see Important considerations when deploying Red Hat OpenShift Data Foundation. For IBM Power Systems: Internal 3 storage devices, each with additional 500 GB of disk	NA
Global Data Platform	Per node Request CPU: 10% (total vCPU of the node) Cluster Request CPU: 3 Limit CPU: 12	Per node Request memory: 10% (total memory of the node) Cluster Request memory: 13 Limit memory: 30	For more information about IBM Spectrum Scale Container Native Storage Access, see Hardware requirements for IBM Storage Scale Container Native Storage Access.	NA
Backup & Restore hub	Request CPU: 5 Limit CPU: 30	Request memory: 17 GiB Limit memory: 44 GiB	200 GB Minimum	NA
Backup & Restore spoke	Request CPU: 2 Limit CPU: 8	Request Memory: 2 GiB Limit Memory 10 GiB	10GiB	NA
Data Cataloging	Request CPU: 14 Limit CPU: 77	Request memory: 29 GiB Limit memory: 162 GiB	120 GB Minimum For more information about Data Cataloging, see Data Cataloging.	NA
Content-Aware Storage ( CAS)	Starter Configuration: <12TB Ingested Data: 160 vCPU (SMT=2) >12TB Ingested Data with High Availability: 320 vCPU	Starter configuration: 768 GiB 12TB Ingested Data with High Availability: 2560 GiB	The minimum required filesystem size is 200 GB. For more information about IBM Spectrum Scale Container Native Storage Access, see Hardware requirements for IBM Storage Scale Container Native Storage Access.	Starter configuration <12TB Ingested Data: 6 L40S GPU 1 GPU worker node 2 non-GPU worker nodes >12TB Ingested Data with High Availability: 4 L40S GPU 2 GPU worker nodes 1 non-GPU worker node

The following table lists the component versions:

Component	Versions
On-premises VMware	Version 7.0
On-premises IBM z/OS Container Extensions (IBM zCX)	All the zCX hypervisor versions on which OpenShift Container Platform is supported. Note: CAS service is not supported on zCX.
Red Hat® OpenShift Container Platform	4.12, 4.14, 4.15, 4.16, 4.17.
Red Hat OpenShift Kubernetes Engine (OKE)	You can use OKE as an alternative for OpenShift Container Platform. The supported version of OKE is same as OpenShift Container Platform.
Red Hat OpenShift Virtualization Engine (OVE)	IBM Fusion provides support for OVE as an alternative for OpenShift Container Platform. The supported version of OVE is same as OpenShift Container Platform. For more information about the limitations and considerations of using OVE, see OVE considerations.
Storage	Fusion Data Foundation 4.12, 4.14, 4.15, 4.16, 4.17 Note: For deployment platforms and supported services, see IBM Fusion Services platform support matrix. IBM Storage Scale Note: IBM Fusion supports IBM Storage Scale 5.2.2.x. Remote mount of IBM Storage Scale storage: IBM Storage Scale remote storage cluster release 5.1.3 or higher. The IBM Fusion cluster accesses the storage owned by an IBM Storage Scale storage cluster by using a remote mount. The IBM Storage Scale file system version of the owning storage cluster cannot be newer than version 33.00. For more information, see Software requirements. To determine the version of your IBM Storage Scale cluster, run the mmdiag --version command on the IBM Storage Scale cluster. To determine the version of your IBM Storage Scale file system, run the mmlsfs all -V command. For further information, including installation/upgrade instructions for the remote IBM Storage Scale cluster, see IBM Storage Scale documentation.
Backup & Restore	IBM Fusion supports backup and recovery operations on Red Hat OpenShift Container Platform environment with any storage provider that implemented the Container Storage Interface (CSI) driver and meets the following prerequisites: The Container Storage Interface driver must be v1 or higher (no support for alpha or beta versions) The Container Storage Interface driver must support Volume Snapshot and Restore. StorageClass must be created with `volumeBindingMode: Immediate` or `volumeBindingMode: WaitForFirstConsumer` and `allowVolumeExpansion: true`. PersistentVolume (PV) must be created with `volumeMode: Filesystem` or `volumeMode: Block` Note: It is also recommended that the `VolumeSnapshotClass` deletion policy is configured to delete snapshots after the corresponding `VolumeSnapshotContent` is deleted (`deletionPolicy: Delete`). Note: For backups of PVCs provisioned on IBM Storage Scale, snapshots are be created only from independent fileset-based persistent volume claims (PVCs). PVCs that are based on lightweight directories and dependent file sets are not supported.