Remote physical location requirements
A remote physical location is processing infrastructure on a remote cluster. When you set up a remote physical location, you install IBM Cloud Pak for Data agents on a remote cluster.
If you plan to use remote physical locations to expand your IBM Cloud Pak for Data deployment to remote clusters, you must ensure that the cluster where you plan to install the Cloud Pak for Data agents has the required hardware, software, and storage.
Prerequisites
Before you create remote physical locations, you must have an instance of IBM Cloud Pak for Data that you want to expand. You cannot run the commands required to create a remote physical location unless you have an existing Cloud Pak for Data deployment.
This instance is called the primary instance of Cloud Pak for Data or the hub.
Software
You must have the following software on the cluster where you plan create a remote physical location:
- Red Hat® OpenShift® Container Platform
-
For entitlement information see Licenses and entitlements.
Cloud Pak for Data supports the following versions of Red Hat OpenShift Container Platform. (Cloud Pak for Data supports the same operating system requirements as Red Hat OpenShift Container Platform.)
Important: Cloud Pak for Data supports only the specified releases of Red Hat OpenShift Container Platform.Different versions of Cloud Pak for Data support different versions of Red Hat OpenShift Container Platform.
Version Supported on Learn more Cluster sizing guidance Version 4.12.0 or later fixes - 5.0.0
- 5.0.1
- 5.0.2
- 5.0.3
For details, see the Red Hat OpenShift Container Platform documentation: - Installation overview
- Selecting a cluster installation method and preparing it for users
- Control plane node sizing
Restriction: Data Virtualization and Db2 Big SQL are not supported on Red Hat OpenShift Container Platform Version 4.12. If you plan to install either of these services, you must install Red Hat OpenShift Container Platform Version 4.14 or later.Refer to the Cloud Pak for Data platform hardware requirements as you configure your cluster. Version 4.14.0 or later fixes - 5.0.0
- 5.0.1
- 5.0.2
- 5.0.3
For details, see the Red Hat OpenShift Container Platform documentation: Refer to the Cloud Pak for Data platform hardware requirements as you configure your cluster. Version 4.15.0 or later fixes - 5.0.0
- 5.0.1
- 5.0.2
- 5.0.3
For details, see the Red Hat OpenShift Container Platform documentation: Refer to the Cloud Pak for Data platform hardware requirements as you configure your cluster. Version 4.16.4 or later fixes - 5.0.3
For details, see the Red Hat OpenShift Container Platform documentation: Refer to the Cloud Pak for Data platform hardware requirements as you configure your cluster. Restriction: Do not install the KubeVirt HyperConverged Cluster Operator from the Community Operator catalog source on the cluster.
Hardware
Only x86-64 hardware is supported.
You can use a multi-node cluster or a single node OpenShift ( SNO) cluster.
Requirements for Cloud Pak for Data agents
| Software | vCPU | Memory | Storage | Notes |
|---|---|---|---|---|
| Cloud Pak for Data agents | 4.5 vCPU | 0.451 GB RAM |
Persistent storage:
32 GB Ephemeral storage: 1.04 MB Image storage: Up to 2.42 GB |
Requirements for service-specific software
| Software | vCPU | Memory | Storage | Notes |
|---|---|---|---|---|
| DataStage |
Operator pods:
0.1 vCPU Instance pods:
|
Operator pods:
0.256 GB RAM Instance pods:
|
Persistent storage:
10 GB per instance (assuming defaults) Ephemeral storage: 10 GB per instance Image storage: Up to 11 GB |
The resources required depend on the following factors:
|
Storage
The remote physical location must use the same persistent storage as the primary instance of Cloud Pak for Data. Ensure that the storage class names are the same on the primary instance and on the remote physical location.