Installing watsonx Orchestrate

Information you need to complete this task

Review the following information before you install watsonx Orchestrate:

Version requirements

All of the components that are associated with an instance of IBM Software Hub must be installed at the same release. For example, if the IBM Software Hub control plane is installed at Version 5.3.0, you must install watsonx Orchestrate at Version 5.3.0.

Environment variables

The commands in this task use environment variables so that you can run the commands exactly as written.

• If you don't have the script that defines the environment variables, see Setting up installation environment variables.
• To use the environment variables from the script, you must source the environment variables before you run the commands in this task. For example, run:

  source ./cpd_vars.sh

Security context constraint

watsonx Orchestrate works with the default Red Hat OpenShift Container Platform security context constraint, restricted-v2.

Storage requirements

You must specify storage classes when you install watsonx Orchestrate. The following storage classes are recommended. However, if you don't use these storage classes on your cluster, ensure that you specify a storage class with an equivalent definition.

Storage	Notes	Storage classes
OpenShift Data Foundation	When you install the service, specify file storage and block storage.	File storage: ocs-storagecluster-cephfs Block storage: ocs-storagecluster-ceph-rbd
IBM Fusion Data Foundation	When you install the service, specify file storage and block storage.	File storage: ocs-storagecluster-cephfs Block storage: ocs-storagecluster-ceph-rbd
IBM Fusion Global Data Platform	When you install the service, specify the same storage class for both file storage and block storage.	File storage: Either of the following storage classes: ibm-spectrum-scale-sc ibm-storage-fusion-cp-sc Block storage: Either of the following storage classes: ibm-spectrum-scale-sc ibm-storage-fusion-cp-sc
IBM Storage Scale Container Native	Not supported.	Not applicable.
Portworx	When you install the service, the --storage_vendor=portworx option ensures that the service uses the correct storage classes.	File storage: portworx-shared-gp3 Block storage: portworx-db-gp3-sc
NFS	Not supported.	Not applicable.
Amazon Elastic storage	Not supported.	Not applicable.
NetApp Trident	When you install the service, specify the same storage class for both file storage and block storage.	File storage: ontap-nas Block storage: ontap-nas
Nutanix	Not supported.	Not applicable.

Before you begin

This task assumes that the following prerequisites are met:

System requirements

This task assumes that the cluster meets the minimum requirements for watsonx Orchestrate.

Where to find more information
If this task is not complete, see System requirements.

In addition, if you plan to use features that require GPU, ensure that you have the appropriate type and number of GPU for watsonx Orchestrate.

Where to find more information
If this task is not complete, see GPU requirements.

Workstation

This task assumes that the workstation from which you will run the installation is set up as a client workstation and has the following command-line interfaces:

• IBM Software Hub CLI: cpd-cli
• OpenShift CLI: oc
• Helm CLI: helm

Where to find more information
If this task is not complete, see Setting up a client workstation.

Control plane

This task assumes that the IBM Software Hub control plane is installed.

Where to find more information
If this task is not complete, see Installing an instance of IBM Software Hub.

Private container registry

If your environment uses a private container registry (for example, your cluster is air-gapped), this task assumes that the following tasks are complete:

1. The watsonx Orchestrate software images are mirrored to the private container registry.

   Where to find more information
   If this task is not complete, see Mirroring images to a private container registry.

2. The cpd-cli is configured to pull the olm-utils-v4 image from the private container registry.

   Where to find more information
   If this task is not complete, see Pulling the olm-utils-v3 image from the private container registry.

Red Hat OpenShift AI

If you plan to use features that require Red Hat OpenShift AI, this task assumes that Red Hat OpenShift AI is installed.

Where to find more information
If this task is not complete, see Installing Red Hat OpenShift AI.

Multicloud Object Gateway

This task assumes that the following tasks are complete:

1. Multicloud Object Gateway is installed and configured.

   Where to find more information
   If this task is not complete, see Installing Multicloud Object Gateway.

2. The secrets that enable watsonx Orchestrate to connect to Multicloud Object Gateway exist.

   Where to find more information
   If this task is not complete, see Creating secrets for services that use Multicloud Object Gateway.

Red Hat OpenShift Serverless Knative Eventing

This task assumes that Red Hat OpenShift Serverless Knative Eventing is installed.

Where to find more information
If this task is not complete, see Installing Red Hat OpenShift Serverless Knative Eventing.

Cluster-scoped resources

This task assumes that the cluster-scoped resources, such as custom resource definitions, cluster roles, and cluster role bindings, exist.

Where to find more information
If this task is not complete, see Creating cluster-scoped resources for the IBM Software Hub platform and services.

Image pull secrets

This task assumes that the secrets that contain the image pull credentials for the instance exist.

Where to find more information
If this task is not complete, see Creating image pull secrets for an instance of IBM Software Hub.

Identity Management Service

This task assumes that IBM Software Hub is configured to use the Identity Management Service.

To check whether IBM Software Hub is using the Identity Management Service, run:

oc get zenservice lite-cr \
-n ${PROJECT_CPD_INST_OPERANDS} \
-o jsonpath='{.spec.iamIntegration}'

• If the command returns true, no additional action is required.
• If the command returns false, complete Integrating with the Identity Management Service.

Procedure

Complete the following tasks to install watsonx Orchestrate:

1. Specifying installation options
2. Installing the service
3. Validating the installation
4. What to do next

Specifying installation options

Installing the service

To install watsonx Orchestrate:

1. Log the cpd-cli in to the Red Hat OpenShift Container Platform cluster:

   ${CPDM_OC_LOGIN}

   Remember: CPDM_OC_LOGIN is an alias for the cpd-cli manage login-to-ocp command.
2. Install the operator and custom resource for watsonx Orchestrate.

   The command that you run depends on the storage on your cluster.

   ---

   Red Hat OpenShift Data Foundation storage

   Run the appropriate command for your environment:

   Default installation (without installation options)

   cpd-cli manage install-components \
   --license_acceptance=true \
   --components=watsonx_orchestrate \
   --release=${VERSION} \
   --operator_ns=${PROJECT_CPD_INST_OPERATORS} \
   --instance_ns=${PROJECT_CPD_INST_OPERANDS} \
   --block_storage_class=${STG_CLASS_BLOCK} \
   --file_storage_class=${STG_CLASS_FILE} \
   --image_pull_prefix=${IMAGE_PULL_PREFIX} \
   --image_pull_secret=${IMAGE_PULL_SECRET}

   Custom installation (with installation options)

   cpd-cli manage install-components \
   --license_acceptance=true \
   --components=watsonx_orchestrate \
   --release=${VERSION} \
   --operator_ns=${PROJECT_CPD_INST_OPERATORS} \
   --instance_ns=${PROJECT_CPD_INST_OPERANDS} \
   --block_storage_class=${STG_CLASS_BLOCK} \
   --file_storage_class=${STG_CLASS_FILE} \
   --image_pull_prefix=${IMAGE_PULL_PREFIX} \
   --image_pull_secret=${IMAGE_PULL_SECRET}\
   --param-file=/tmp/work/install-options.yml

   ---

   IBM Fusion Data Foundation storage

   Run the appropriate command for your environment:

   Default installation (without installation options)

   cpd-cli manage install-components \
   --license_acceptance=true \
   --components=watsonx_orchestrate \
   --release=${VERSION} \
   --operator_ns=${PROJECT_CPD_INST_OPERATORS} \
   --instance_ns=${PROJECT_CPD_INST_OPERANDS} \
   --block_storage_class=${STG_CLASS_BLOCK} \
   --file_storage_class=${STG_CLASS_FILE} \
   --image_pull_prefix=${IMAGE_PULL_PREFIX} \
   --image_pull_secret=${IMAGE_PULL_SECRET}

   Custom installation (with installation options)

   cpd-cli manage install-components \
   --license_acceptance=true \
   --components=watsonx_orchestrate \
   --release=${VERSION} \
   --operator_ns=${PROJECT_CPD_INST_OPERATORS} \
   --instance_ns=${PROJECT_CPD_INST_OPERANDS} \
   --block_storage_class=${STG_CLASS_BLOCK} \
   --file_storage_class=${STG_CLASS_FILE} \
   --image_pull_prefix=${IMAGE_PULL_PREFIX} \
   --image_pull_secret=${IMAGE_PULL_SECRET} \
   --param-file=/tmp/work/install-options.yml

   ---

   Portworx storage

   Run the appropriate command for your environment:

   Default installation (without installation options)

   cpd-cli manage install-components \
   --license_acceptance=true \
   --components=watsonx_orchestrate \
   --release=${VERSION} \
   --operator_ns=${PROJECT_CPD_INST_OPERATORS} \
   --instance_ns=${PROJECT_CPD_INST_OPERANDS} \
   --storage_vendor=portworx \
   --image_pull_prefix=${IMAGE_PULL_PREFIX} \
   --image_pull_secret=${IMAGE_PULL_SECRET}

   Custom installation (with installation options)

   cpd-cli manage install-components \
   --license_acceptance=true \
   --components=watsonx_orchestrate \
   --release=${VERSION} \
   --operator_ns=${PROJECT_CPD_INST_OPERATORS} \
   --instance_ns=${PROJECT_CPD_INST_OPERANDS} \
   --storage_vendor=portworx \
   --image_pull_prefix=${IMAGE_PULL_PREFIX} \
   --image_pull_secret=${IMAGE_PULL_SECRET} \
   --param-file=/tmp/work/install-options.yml

   ---

   NetApp Trident

   Remember: When you use NetApp Trident storage, both ${STG_CLASS_BLOCK} and ${STG_CLASS_FILE} point to the same storage class, typically ontap-nas.

   Run the appropriate command for your environment:

   Default installation (without installation options)

   cpd-cli manage install-components \
   --license_acceptance=true \
   --components=watsonx_orchestrate \
   --release=${VERSION} \
   --operator_ns=${PROJECT_CPD_INST_OPERATORS} \
   --instance_ns=${PROJECT_CPD_INST_OPERANDS} \
   --block_storage_class=${STG_CLASS_BLOCK} \
   --file_storage_class=${STG_CLASS_FILE} \
   --image_pull_prefix=${IMAGE_PULL_PREFIX} \
   --image_pull_secret=${IMAGE_PULL_SECRET}

   Custom installation (with installation options)

   cpd-cli manage install-components \
   --license_acceptance=true \
   --components=watsonx_orchestrate \
   --release=${VERSION} \
   --operator_ns=${PROJECT_CPD_INST_OPERATORS} \
   --instance_ns=${PROJECT_CPD_INST_OPERANDS} \
   --block_storage_class=${STG_CLASS_BLOCK} \
   --file_storage_class=${STG_CLASS_FILE} \
   --image_pull_prefix=${IMAGE_PULL_PREFIX} \
   --image_pull_secret=${IMAGE_PULL_SECRET} \
   --param-file=/tmp/work/install-options.yml

   ---

Validating the installation

[SUCCESS]... The install-components command ran successfully

If you want to confirm that the custom resource status is Completed, you can run the cpd-cli manage get-cr-status command:

cpd-cli manage get-cr-status \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=watsonx_orchestrate

What to do next