Capability storage requirements
CP4BA components that use block storage do not require the storage provider to perform cross-Availability Zone (AZ) replication when they run in a multi-replica mode because they include their own built-in replication. For more information, see Availability of stored data.
Block storage is suitable for databases and other data storage systems that require high-performance persistence, like MongoDB, Db2 and OpenSearch. RWO persistent volumes are often provisioned for databases and indexed workloads. Components that depend on RWX file storage rely on the storage provider to replicate across AZs. When possible, S3 storage is the preferred persistence for read-write-many scenarios as it is easily replicable by the storage provider.
Filesystem
.Component | RWO single-zone (For example, EBS) |
RWX (replicated File) |
S3 (replicated object storage) |
---|---|---|---|
Platform UI (Zen) * | Yes (EDB Postgres **) | Yes (Zen usermgmt - file system) | |
Cloud Pak foundational services | Yes (MongoDB **) | ||
Automation Decision Services | Yes, optional (MongoDB) | Yes, optional (archive storage for runtime) | |
Automation Document Processing | Yes, optional (MongoDB) | Yes (5 different components) | |
Automation Workstream Services * | Yes (Liberty JMS) | Yes (2 different components) | |
Business Automation Application | Yes | ||
Business Automation Insights * | Yes (Kafka ** and OpenSearch **) | Yes | |
Business Automation Navigator | Yes | ||
Business Automation Studio * | Yes (Liberty JMS) | Yes | |
Business Automation Workflow | Yes (Liberty JMS) | Yes | |
FileNet Content Manager | Yes (6 different components) | Yes (optional document content store) | |
Operational Decision Manager | Yes (2 optional scenarios) | ||
Resource Registry | Yes | ||
Workflow Process Service Authoring * | Yes (Liberty JMS, Postgres) | Yes |
* Component requires both RWO and RWX for different purposes.
** Native HA is recommended over multi-instance due to storage simplicity.
The following table lists the storage type and disk space requirements for production deployments. Ranges are for small to large environments.
The following table also provides storage requirements for production deployments. Kubernetes access modes include Read Write Once (RWO), Read Write Many (RWX), and Read Only Many (ROX).
Capability or runtime | Storage type | Disk space | Access mode | Number of persistent volumes for non-HA/HA | Posix compliance |
---|---|---|---|---|---|
Automation Decision Services | [optional] mongo_embedded: File or Block [optional] runtime storage: File |
50 GB | 1 (non-HA) 1 (shared) |
Posix compliance needed Posix compliance not needed |
|
Automation Document Processing | File Block (for mongo) |
64 GB |
|
Posix compliance needed | |
Automation Workstream Services | File | 9 GB | RWX | 4 for Workflow Server (log, dump, messaging, file) | Posix compliance not needed |
Business Automation Application | File | Application Engine: 50 MB | 1 | Posix compliance not needed | |
Business Automation Insights | File Block (mandatory for OpenSearch) |
Flink: 20 GB
Sizing depends on the size of the projects.
|
Posix compliance not needed | ||
Business Automation Navigator | File | 6 for BAN | Posix compliance not needed | ||
Business Automation Studio | File File |
2 - 6 GB |
|
Posix compliance not needed | |
Business Automation Workflow with or without Automation Workstream Services | File File |
Workflow Runtime: 21
GB Workflow Authoring: 39 GB |
RWO RWX |
Workflow Runtime
Workflow Authoring
|
Posix compliance not needed |
Process Federation Server | File | 6 GB | RWO | 2 for Process Federation Server | Posix compliance not needed |
FileNet Content Manager | File | Component logs and configuration information: 500 MB for each component. Temporary working space: Workload dependent, with a minimum of 1 GB for each component. CPE and CSS content and index stores: Size of the content elements your users store/index, which grows over time. |
|
Posix compliance not needed | |
Operational Decision Manager | [optional] File For product customization [optional] DB support to retrieve jdbc driver |
10 - 100 GB If the database is outside the cluster, the size of internal storage is reduced to 1 GB. |
1 (non-HA) 1 (non-HA) |
Posix compliance not needed Posix compliance not needed |
|
Resource Registry | File | Resource Registry: 5 - 16 GB | 1 | Posix compliance not needed | |
Workflow Process Service Authoring | File | 2 – 6 GB |
|
Posix compliance not needed |
The following table shows an example of CP4BA storage in the public cloud on AWS.
Component | AWS EBS (Single-zone block RWO) |
AWS EFS (replicated File RWX) |
AWS S3 (Replicated object storage) |
AWS FSx ONTAP (offers replicated RWO, RWX) |
OpenShift Data Foundation (offers replicated RWO, RWX) |
Portworx (offers replicated RWO, RWX) |
---|---|---|---|---|---|---|
Platform UI (Zen) | Yes | Yes | Yes | Yes | Yes | |
Cloud Pak foundational services | Yes | Yes | Yes | Yes | Yes | |
Automation Decision Services | Yes, optional (MongoDB) | Yes, optional (archive storage for runtime) | Yes, optional | Yes, optional | Yes, optional | |
Automation Document Processing | Yes, optional (MongoDB) | Yes (5 different components) | Yes | Yes | Yes | |
Automation Workstream Services | Yes (Liberty JMS) | Yes (2 different components) | Yes | Yes | Yes | |
Business Automation Application | Yes | Yes | Yes | Yes | ||
Business Automation Insights | Yes (Kafka and OpenSearch) | Yes | Yes | Yes | Yes | |
Business Automation Navigator | Yes | Yes | Yes | Yes | ||
Business Automation Studio | Yes (Liberty JMS) | Yes | Yes | Yes | Yes | |
Business Automation Workflow | Yes (Liberty JMS) | Yes | Yes | Yes | Yes | |
FileNet Content Manager | Yes (6 different components) | Yes (optional document content store) | Yes | Yes | Yes | |
Operational Decision Manager | Yes (2 optional scenarios) | Yes (2 optional scenarios) | Yes (2 optional scenarios) | Yes (2 optional scenarios) | ||
Resource Registry | Yes | Yes | Yes | Yes | ||
Workflow Process Service Authoring | Yes (Liberty JMS, Postgres) | Yes | Yes | Yes | Yes |
AWS EFS requires NFS subdir external provisioner.
Use the Trident ontap-nas driver.
ODF is not currently supported for use with the ROSA managed OpenShift platform, see ODF support on ROSA.
Some components require both RWO and RWX for different purposes.
The following table shows an example of CP4BA storage in the public cloud on Azure.
Component | Azure Disks (single-zone or replicated RWO) |
Azure Files (replicated File RWX) |
Azure Blob (replicated object storage) |
OpenShift Data Foundation (offers replicated RWO, RWX) |
Portworx (offers replicated RWO, RWX) |
---|---|---|---|---|---|
Platform UI (Zen) | Yes | Yes | Yes | Yes | |
Cloud Pak foundational services | Yes | Yes | Yes | ||
Automation Decision Services | Yes, optional (MongoDB) | Yes, optional (archive storage for runtime) | Yes, optional | Yes, optional | |
Automation Document Processing | Yes, optional (MongoDB) | Yes (5 different components) | Yes | Yes | |
Automation Workstream Services | Yes (Liberty JMS) | Yes (2 different components) | Yes | Yes | |
Business Automation Application | Yes | Yes | Yes | ||
Business Automation Insights | Yes (Kafka and OpenSearch) | Yes | Yes | Yes | |
Business Automation Navigator | Yes | Yes | Yes | ||
Business Automation Studio | Yes (Liberty JMS) | Yes | Yes | Yes | |
Business Automation Workflow | Yes (Liberty JMS) | Yes | Yes | Yes | |
FileNet Content Manager | Yes (6 different components) | Yes (optional document content store) | Yes | Yes | |
Operational Decision Manager | Yes (2 optional scenarios) | Yes (2 optional scenarios) | Yes (2 optional scenarios) | ||
Resource Registry | Yes | Yes | Yes | ||
Workflow Process Service Authoring | Yes (Liberty JMS, Postgres) | Yes | Yes | Yes |
Use the Azure Files NFS driver, and not the SMB driver.