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® Software Hub agents on a remote cluster.

If you plan to use remote physical locations to expand your IBM Software Hub deployment to remote clusters, you must ensure that the cluster where you plan to install the IBM Software Hub agents has the required hardware, software, and storage.

Prerequisites

Before you create remote physical locations, you must have an instance of IBM Software Hub that you want to expand. You cannot run the commands required to create a remote physical location unless you have an existing IBM Software Hub deployment.

This instance is called the primary instance of IBM Software Hub 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.

IBM Software Hub supports the following versions of Red Hat OpenShift Container Platform. (IBM Software Hub supports the same operating system requirements as Red Hat OpenShift Container Platform.)

Important: IBM Software Hub supports only the specified releases of Red Hat OpenShift Container Platform.

Version	Learn more
Version 4.12.0 or later fixes	Red Hat OpenShift Container Platform 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 Cluster sizing guidance Refer to the platform hardware requirements as you configure your cluster: x86_64 clusters ppc64le clusters s390x clusters 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.
Version 4.14.0 or later fixes	Red Hat OpenShift Container Platform 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 Cluster sizing guidance Refer to the platform hardware requirements as you configure your cluster: x86_64 clusters ppc64le clusters s390x clusters
Version 4.15.0 or later fixes	Red Hat OpenShift Container Platform 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 Cluster sizing guidance Refer to the platform hardware requirements as you configure your cluster: x86_64 clusters ppc64le clusters s390x clusters
Version 4.16.4 or later fixes	Red Hat OpenShift Container Platform 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 Cluster sizing guidance Refer to the platform hardware requirements as you configure your cluster: x86_64 clusters ppc64le clusters s390x clusters
Version 4.17.0 or later fixes	Red Hat OpenShift Container Platform 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 Cluster sizing guidance Refer to the platform hardware requirements as you configure your cluster: x86_64 clusters ppc64le clusters s390x clusters
Version 4.18.6 or later fixes	Red Hat OpenShift Container Platform 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 Cluster sizing guidance Refer to the platform hardware requirements as you configure your cluster: x86_64 clusters ppc64le clusters s390x clusters
Version 4.19.0 or later fixes	Red Hat OpenShift Container Platform 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 Cluster sizing guidance Refer to the platform hardware requirements as you configure your cluster: x86_64 clusters ppc64le clusters s390x clusters

Hardware

Only x86-64 hardware is supported.

You can use a multi-node cluster or a single node OpenShift ( SNO) cluster.

You must have sufficient resources to install:

The shared cluster components
The IBM Software Hub agents
The service-specific software

Requirements for shared cluster components

Certificate manager

vCPU	Memory	Storage	Notes
1.6 vCPU	1.94 GB RAM	This information is not currently available.	A certificate manager is required. This software is installed once on the cluster. For more information, see Cluster-wide components. Review the Hardware requirements and recommendations for foundational services in the IBM Cloud Pak foundational services documentation for updates to the hardware requirements: Version 4.13 Version 4.14

License Service

vCPU	Memory	Storage	Notes
3.1 vCPU	0.735 GB RAM	This information is not currently available.	Required. This software is installed once on the cluster. For more information, see Cluster-wide components. Review the Hardware requirements and recommendations for foundational services in the IBM Cloud Pak foundational services documentation for updates to the hardware requirements: Version 4.13 Version 4.14

Scheduling service

vCPU	Memory	Storage	Notes
Operator pods: 0.2 vCPU Catalog pods: 0.01 vCPU Operand: Up to 0.9 vCPU	Operator pods: 0.54 GB RAM Catalog pods: 0.05 GB RAM Operand: 3.65 GB RAM	Persistent storage: Not applicable Ephemeral storage: 0.9 GB Image storage: Up to 2.69 GB	Required in some situations, but generally recommended. This software is installed once on the cluster. For more information, see Cluster-wide components. Minimum resources for an installation with a single replica per service.

vCPU

Memory

Storage

Notes

Operator pods:
0.2 vCPU

Catalog pods:
0.01 vCPU

Operand:
Up to 0.9 vCPU

Operator pods:
0.54 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
3.65 GB RAM

Persistent storage:
Not applicable

Ephemeral storage:
0.9 GB

Image storage:
Up to 2.69 GB

Required in some situations, but generally recommended.

This software is installed once on the cluster. For more information, see Cluster-wide components.

Minimum resources for an installation with a single replica per service.

Requirements for IBM Software Hub agents

Software	vCPU	Memory	Storage	Notes
IBM Software Hub 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

Analytics Engine powered by Apache Spark

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Instance pods:	Operator pods: 0.256 GB RAM Instance pods:	Persistent storage: Ephemeral storage: Image storage:	The resources required depend on the following factors: The number of instances you plan to provision on the remote physical location. The size of each instance on the physical location

DataStage

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Instance pods: Small: 7 vCPU Medium: 14 vCPU Large: 28 vCPU	Operator pods: 0.256 GB RAM Instance pods: Small: 28 GB RAM Medium: 52 GB RAM Large: 100 GB RAM	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: The number of instances you plan to provision on the remote physical location. The size of each instance on the physical location

Orchestration Pipelines

Tech preview This feature is available as a technical preview.

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Instance pods: 0.250 vCPU	Operator pods: 0.256 GB RAM Instance pods: 0.512 GB RAM	Persistent storage: Not applicable Ephemeral storage: 11 GB Image storage: Up to 1.2 GB	The resources required depend on the following factors: The number of instances you plan to provision on the remote physical location. The size of each instance on the physical location

Storage

The remote physical location must use the same persistent storage as the primary instance of IBM Software Hub. Ensure that the storage class names are the same on the primary instance and on the remote physical location.

For more information, see:

Shared storage

If you plan to create Analytics Engine powered by Apache Spark service instances on the remote physical location, you must have shared storage that is accessible to the primary instance of IBM Software Hub and the remote physical location. This storage is in addition to the storage described in the preceding Storage section.

The following storage is supported for the shared storage:

NFS
Important: The storage must be configured to support dynamic provisioning.