System requirements
The administrator must make sure that the target cluster on OpenShift® Container Platform has the capacity for all of the capabilities that you plan to install.
The deployment profile to use is starter (sc_deployment_profile_size=starter).
The starter profile cannot be used for production usage.
| Profile | Description | Scaling (per 8-hour day) | Minimum number of worker nodes |
|---|---|---|---|
| Starter | For environments that are used by a 2 developers and up to 5 users. This profile is for first-time users and useful for demonstrations or evaluation. |
|
3 |
Note: PostgreSQL and OpenLDAP are installed along with a set of foundational services as part of the
deployment. For evaluation workloads where higher levels of activity are needed, you must install a
production deployment and configure a dedicated database.
The cluster hardware architecture can be Intel (amd64 or x86_64 the 64-bit edition for Linux® x86) on all platforms, Linux on IBM Z®, or Linux on Power®. A cluster where you want to install all of the capabilities needs the following configuration.
- Worker (5 nodes): 16 vCPU and 32 Gi memory on each node.
- Approximately 1,200 GB of storage.
The following table shows the minimum requirements for each Cloud Pak capability. Storage
includes all persistent volumes (PVs) and all the databases that are needed.
| Capability / Pattern | vCPU | Memory | Storage |
|---|---|---|---|
| IBM FileNet® Content Manager | 3 master nodes with 4 vCPUs 3 worker nodes with 4 vCPUs |
16 Gi on each node | 70 GB |
| Platform foundation For more information about IBM Cloud Pak® foundational services requirements, see Hardware requirements and recommendations for foundational
services
|
3 master nodes with 4 vCPUs 3 worker nodes with 4 vCPUs |
8 Gi on each node | 20 GB per pod |
Note: Machine Learning Server (including Intelligent Task Prioritization and Workforce Insights) is not supported on Linux on IBM Z or Linux on Power.