Storage requirements

The IBM® Cloud Pak for Network Automation orchestration services use both persistent and dynamic storage. The services have different capacity requirements, file system permissions, and access modes.

Tested and supported storage providers

The following storage providers are tested and supported, and are recommended for a deployment of IBM Cloud Pak for Network Automation:

  • Red Hat® OpenShift® Ceph® Storage (rook-ceph-block and rook-cephfs).

IBM and Red Hat storage providers

The following IBM and Red Hat storage providers are not tested with IBM Cloud Pak for Network Automation, but are recommended alternative options:

  • IBM Storage Fusion.
  • IBM Storage Suite for IBM Cloud® Paks. The following products are included in this suite of offerings:
    • Block storage from IBM Spectrum® Virtualize, FlashSystem, or DS8000®
    • File storage from IBM Spectrum Scale
    • Object storage from IBM Cloud Object Storage or Red Hat Ceph
    • Fusion Data Foundation, version 4.x, from version 4.2 or higher (previously Red Hat OpenShift Data Foundation)
  • Red Hat OpenShift Ceph Storage (rook-ceph-block and rook-cephfs).
  • IBM Cloud Block storage and IBM Cloud File storage

Other storage providers

The storage providers in the Tested and supported storage providers section are the only providers that are tested and validated for a deployment of IBM Cloud Pak for Network Automation. You can choose to use an alternative storage provider if it meets the requirements for deploying IBM Cloud Pak for Network Automation.

The storage provider that you choose must meet the same storage and hardware requirements as the supported storage providers. For example, for deploying IBM Cloud Pak for Network Automation, your storage provider must support the required access modes and storage modes.

The following storage providers are not tested with IBM Cloud Pak for Network Automation, but are recommended alternative options:

  • Portworx Storage, version 2.5.5 or above
  • Amazon Elastic File Storage (EFS) for RWX mode access.

Storage types and access modes for services

Service Supported storage types Storage access mode
postgres Dynamic (rook-cephfs) ReadWriteOnce
cp4na-o-events-kafka Dynamic (rook-ceph-block) ReadWriteOnce
cp4na-o-events-zookeeper Dynamic (rook-ceph-block) ReadWriteOnce
cp4na-o-events-zookeeper-locking Dynamic (rook-ceph-block) ReadWriteOnce
cp4na-o-symmetricds Dynamic (rook-cephfs) ReadWriteOnce
zen-metastoredb Dynamic (rook-ceph-block) ReadWriteOnce
user-home Dynamic (rook-cephfs) ReadWriteMany
cp4na-o-vault emptyDir volume  
opensearch Dynamic (rook-cephfs) ReadWriteOnce
apollo emptyDir volume  
brent emptyDir volume  
daytona emptyDir volume  
doki emptyDir volume  
ibm-nginx Dynamic (rook-cephfs) ReadWriteMany
ishtar emptyDir volume  
nimrod emptyDir volume  
talladega emptyDir volume  
usermgmt user-home Dynamic (rook-cephfs) ReadWriteMany
zen-audit user-home Dynamic (rook-cephfs) ReadWriteMany
zen-core user-home Dynamic (rook-cephfs) ReadWriteMany
zen-core-api user-home Dynamic (rook-cephfs) ReadWriteMany
zen-core-api emptyDir volume  
zen-watcher user-home Dynamic (rook-cephfs) ReadWriteMany
zen-watcher emptyDir volume  
The cp4na-o-events-kafka service must use block storage and not file storage.

PVCs that are used for services

The following table lists the persistent volume claims (PVCs), their access modes, and their storage types:

PVC Access mode Storage type
cp4na-o-postgresql-1 RWO File
cp4na-o-postgresql-2 RWO File
cp4na-o-postgresql-3 RWO File
data-cp4na-o-events-kafka-0 RWO File
data-cp4na-o-events-zookeeper-0 RWO File
data-cp4na-o-zookeeper-locking-0 RWO File
data-ibm-opensearch-ib-6fb9-es-server-all-0 RWO File
data-ibm-opensearch-ib-6fb9-es-server-all-1 RWO File
data-ibm-opensearch-ib-6fb9-es-server-all-2 RWO File
datadir-zen-metastoredb-0 RWO Block
datadir-zen-metastoredb-1 RWO Block
datadir-zen-metastoredb-2 RWO Block
user-home-pvc RWX File