Resource requirements

IBM Fusion Data Foundation services consist of an initial set of base services, and can be extended with additional device sets. All of these Fusion Data Foundation services pods are scheduled by Kubernetes on OpenShift Container Platform nodes. Expanding the cluster in multiples of three, one node in each failure domain, is an easy way to satisfy the pod placement rules.

For more information, see pod placement rules.
Important: These requirements relate to Fusion Data Foundation services only, and not to any other services, operators, or workloads that are running on these nodes.
Table 1. Aggregate available resource requirements for IBM Fusion Data Foundation only
Deployment Mode Base services Additional device Set
Internal

  • 30 CPU (logical)

  • 72 GiB memory

  • 3 storage devices

  • 6 CPU (logical)

  • 15 GiB memory

  • 3 storage devices
External

  • 4 CPU (logical)

  • 16 GiB memory

 Not applicable

For example, for a three node cluster in an internal mode deployment with a single device set, a minimum of 3 x 10 = 30 units of CPU are required.

For more information, see Subscription Offerings and CPU units.

For additional guidance with designing your IBM Fusion Data Foundation cluster, see the ODF Sizing Tool.
Note:
1 CPU Unit maps to the Kubernetes concept of 1 CPU unit.
  • 1 unit of CPU is equivalent to 1 core for non-hyperthreaded CPUs.
  • 2 units of CPU are equivalent to 1 core for hyperthreaded CPUs.
  • Fusion Data Foundation core-based subscriptions always come in pairs (2 cores).
Table 2. Aggregate minimum resource requirements for IBM Power
Deployment Mode Base services
Internal

  • 48 CPU (logical)

  • 192 GiB memory

  • 3 storage devices, each with additional 500GB of disk
External

  • 24 CPU (logical)

  • 48 GiB memory

For example, for a three node cluster in an internal-attached devices mode deployment, a minimum of 3 x 16 = 48 units of CPU and 3 x 64 = 192 GB of memory is required.