Storage requirements

Concert platform storage requirements

A Concert deployment requires several types of storage:

Storage for images in the private container registry

Depending on your environment, you might need to store images in a private container registry rather than pulling them directly from the IBM Entitled Registry.

If you use a private container registry, you must have sufficient space for the Concert components that you plan to install.

Sizing

A minimum of 500 GB of storage space in the private container registry.

Best practices:

• Review the image size information in Hardware requirements to ensure that you have sufficient space for the images you plan to mirror.

Local storage for container images

Each node on your cluster must have local storage for the container images that are running on that node.

Storage location

The container images are stored in the root file system on the nodes.

On the Red Hat® OpenShift® Container Platform, local copies of the images are stored in /var/lib/containers. For details, see Data storage management in the Red Hat OpenShift Container Platform documentation:

• Version 4.14
• Version 4.15

Sizing

A minimum of 500 GB of storage space per node.

Persistent storage

Concert supports and is optimized for several types of persistent storage:

Storage option	Version	Notes
OpenShift Data Foundation	Version 4.12 or later fixes Version 4.14 or later fixes Version 4.15 or later fixes	Available in Red Hat OpenShift Platform Plus. Ensure that you install a version of OpenShift Data Foundation that is compatible with the version of Red Hat OpenShift Container Platform that you are running. For details, see https://access.redhat.com/articles/4731161.
IBM Storage Fusion Data Foundation	Version 2.6.1 or later fixes Version 2.7.1 or later fixes	Available in IBM Storage Fusion. Ensure that you install a version of IBM Storage Fusion Data Foundation that is compatible with the version of Red Hat OpenShift Container Platform that you are running.
IBM Storage Fusion Global Data Platform	Version 2.6.1 or later fixes Version 2.7.1 or later fixes	Available in IBM Storage Fusion or IBM Storage Fusion HCI System
IBM Storage Scale Container Native (with IBM Storage Scale Container Storage Interface)	Version 5.1.7 or later fixes, with CSI Version 2.9.0 or later fixes	Available in the following storage: IBM Storage Fusion IBM Storage Suite for IBM Cloud® Paks
Portworx	Version 2.13.3 or later fixes Version 3.0.2 or later fixes	If you are running Red Hat OpenShift Container Platform Version 4.12, you must use Portworx Version 2.13.3 or later. If you are running Red Hat OpenShift Container Platform Version 4.14, you must use Portworx Version 3.0.2 or later.
NFS	Version 3 or 4
Amazon Elastic Block Store (EBS)	Not applicable	Not applicable
IBM Cloud Block Storage	Not applicable	Not applicable
IBM Cloud File Storage	Not applicable	It is recommended that you use both IBM Cloud Block Storage and IBM Cloud File Storage storage.
NetApp Trident	Version 22.4.0 or later fixes	This information applies to both self-managed and managed NetApp Trident.

When you plan your environment, ensure that you review the storage types that are supported by the components that you plan to install:

• Shared component persistent storage requirements

Tip: The preceding storage options have been evaluated by IBM. You can run the Concert recommended storage validation tool to assess storage that is provided by other vendors. However, this tool does not guarantee support for other types of storage. You can use other storage environments at your own risk.

Sizing

The minimum amount of storage depends on the type of storage that you plan to use. For details, see the Resource requirements section in the Storage comparison .

As a general rule, Concert with all services installed can use up to 700 GB of storage space. Review the Storage comparison to ensure that you have sufficient storage space available for user data based on the type of storage that you select. You can add additional capacity depending on your user data volume requirements.

Concert persistent storage requirements

Concert uses ReadWriteOnce (RWO) storage.

The following table lists the recommended storage classes. If your cluster uses different storage class names, ensure that you specify equivalent storage classes.

PostgreSQL database and object storage bucket requirements

Shared component persistent storage requirements

The following table indicates the type of storage that each component supports. For information about the recommended storage classes for each component, see #compute-requirements__shared-comps-sc.

• File req indicates that a service can use the specified block storage only if file storage is also provided.
• -- indicates that the service does not use persistent storage.

In the following table, Data Foundation means either Red Hat OpenShift Data Foundation or IBM Storage Fusion Data Foundation.