Installing watsonx Orchestrate
An instance administrator can install watsonx Orchestrate on IBM® Software Hub Version 5.1.
- Who needs to complete this task?
-
Instance administrator To install watsonx Orchestrate, you must be an instance administrator. An instance administrator has permission to install software in the following projects:
- The operators project for the instance
-
The operators for this instance of watsonx Orchestrate are installed in the operators project.
In the installation commands, the
${PROJECT_CPD_INST_OPERATORS}environment variable refers to the operators project. - The operands project for the instance
-
The custom resources for the control plane and watsonx Orchestrate are installed in the operands project.
In the installation commands, the
${PROJECT_CPD_INST_OPERANDS}environment variable refers to the operands project.
- When do you need to complete this task?
-
Review the following options to determine whether you need to complete this task:
- If you want to install multiple services at the same time, follow the process in Running a batch installation of solutions and services instead.
- If you didn't install watsonx Orchestrate as part of a batch installation, complete this task
to add watsonx Orchestrate to your environment.
Repeat as needed If you are responsible for multiple instances of IBM Software Hub, you can repeat this task to install more instances of watsonx Orchestrate on the cluster.
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.1.3, you must install watsonx Orchestrate at Version 5.1.3.
- 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.
Before you begin
This task assumes that the following prerequisites are met:
| Prerequisite | Where to find more information |
|---|---|
| The cluster meets the minimum requirements for installing watsonx Orchestrate. | If this task is not complete, see System requirements. |
The workstation from which you will run the installation is set up as a client workstation
and includes the following command-line interfaces:
|
If this task is not complete, see Setting up a client workstation. |
| The IBM Software Hub control plane is installed. | If this task is not complete, see Installing an instance of IBM Software Hub. |
| For environments that use a private container registry, such as air-gapped environments, the watsonx Orchestrate software images are mirrored to the private container registry. | If this task is not complete, see Mirroring images to a private container registry. |
For environments that use a private container registry, such as air-gapped environments,
the cpd-cli is configured to pull the olm-utils-v3 image from the private container registry. |
If this task is not complete, see Pulling the olm-utils-v3 image from the private container registry. |
| The operators that are required to use GPUs are installed. | If this task is not complete, see Installing operators for services that require GPUs. |
| Red Hat OpenShift AI is installed. | If this task is not complete, see Installing Red Hat OpenShift AI. |
| Multicloud Object Gateway is installed and configured. | If this task is not complete, see Installing Multicloud Object Gateway. |
| The secrets that enable watsonx Orchestrate to connect to Multicloud Object Gateway exist. | If this task is not complete, see Creating secrets for services that use Multicloud Object Gateway. |
| Red Hat OpenShift Serverless Knative Eventing is installed and configured. | If this task is not complete, see Installing Red Hat OpenShift Serverless Knative Eventing. |
| IBM App Connect in containers is installed and
configured. 5.1.0 5.1.1 5.1.2 This software is required only if you are installing IBM Software Hub Version 5.1.0, Version 5.1.1, or Version 5.1.2. |
If this task is not complete, see Installing App Connect in containers. |
Preparing to install
- Verify that Identity and Access Management (IAM) Service is enabled. By default, the Identity and Access Management (IAM) Service is enabled with the IBM Software Hub Version 5.1.x. For more information, see Integrating with the Identity Management Service.
- watsonx Orchestrate and standalone watsonx Assistant cannot be installed on the same namespace. If you want to install both separately, then you can install on different namespaces.
Procedure
Complete the following tasks to install watsonx Orchestrate:
Specifying installation options
If you plan to install watsonx™ Orchestrate, you
can specify the following installation option in a file named install-options.yml in the cpd-cli
work directory (For example: cpd-cli-workspace/olm-utils-workspace/work).
The parameter is optional. If you do not set the installation parameter, the default values are used. Uncomment the parameter if you want to override the default behavior.
The sample YAML content uses the default values.
################################################################################
# watsonx Orchestrate parameters
################################################################################
#watson_orchestrate_watsonx_ai_type: false
#watson_orchestrate_syom_models: []
#watson_orchestrate_ootb_models: []
| Property | Description |
|---|---|
watson_orchestrate_watsonx_ai_type |
5.1.0
5.1.1
5.1.2 This parameter applies only
to IBM Software Hub Version 5.1.0, Version 5.1.1, and Version 5.1.2. Specify whether you want to install Inference foundation models (
For more information about supported GPUs, see the Hardware requirements for watsonx Orchestrate.
|
watson_orchestrate_syom_models |
5.1.3 and later This option is
available starting in IBM Software Hub
Version 5.1.3. Specify whether you want to use a specialized model
that is specifically tuned for use with watsonx Orchestrate for:
Important: The following model will be automatically installed
if you do not specify a value for
watson_orchestrate_syom_models or
watson_orchestrate_ootb_models:
|
watson_orchestrate_ootb_models |
5.1.3 and later This option is
available starting in IBM Software Hub
Version 5.1.3. Specify whether you want to use a general model for:
Important: The following model will be automatically installed
if you do not specify a value for
watson_orchestrate_syom_models or
watson_orchestrate_ootb_models:
|
Installing the service
To install watsonx Orchestrate:
-
Log the
cpd-cliin to the Red Hat OpenShift Container Platform cluster:${CPDM_OC_LOGIN}Remember:CPDM_OC_LOGINis an alias for thecpd-cli manage login-to-ocpcommand. - Important:Create an instance of App Connect for watsonx Orchestrate:
- Do this step only if you are in Version 5.1.0, 5.1.1, or 5.1.2.
- Before you proceed to deploy the App Connect instance and create App Connect secret, you must create dedicated namespaces for Cloud Pak for Data operators and Cloud Pak for Data instance.
For more information, see Manage setup App Connect.cpd-cli manage setup-appconnect \ --appconnect_ns=${PROJECT_IBM_APP_CONNECT} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --release=${VERSION} \ --components=watsonx_orchestrate \ --file_storage_class=${STG_CLASS_FILE} - Run the following command to create the required OLM objects for watsonx Orchestrate in the
operators project for the
instance:
cpd-cli manage apply-olm \ --release=${VERSION} \ --cpd_operator_ns=${PROJECT_CPD_INST_OPERATORS} \ --components=watsonx_orchestrateWait for thecpd-clito return the following message before you proceed to the next step:[SUCCESS]... The apply-olm command ran successfullyIf the
apply-olmfails, see Troubleshooting the apply-olm command during installation or upgrade. - Create the 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 to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=watsonx_orchestrate \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --license_acceptance=true - Custom installation (with installation options)
-
cpd-cli manage apply-cr \ --components=watsonx_orchestrate \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
IBM Fusion Data Foundation storage
Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=watsonx_orchestrate \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --license_acceptance=true - Custom installation (with installation options)
-
cpd-cli manage apply-cr \ --components=watsonx_orchestrate \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
Portworx storage
Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=watsonx_orchestrate \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --storage_vendor=portworx \ --license_acceptance=true - Custom installation (with installation options)
-
cpd-cli manage apply-cr \ --components=watsonx_orchestrate \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --storage_vendor=portworx \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
NetApp Trident
Remember: When you use NetApp Trident storage, both${STG_CLASS_BLOCK}and${STG_CLASS_FILE}point to the same storage class, typicallyontap-nas.Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=watsonx_orchestrate \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --license_acceptance=true - Custom installation (with installation options)
-
cpd-cli manage apply-cr \ --components=watsonx_orchestrate \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
Validating the installation
apply-cr command
returns:[SUCCESS]... The apply-cr 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
Optional: Enabling the models and GPU features
- Prerequisites for enabling the models in Version 5.1.2
- The foundation models must be enabled to use the AI agent and other features in watsonx Orchestrate.
- Enabling the default models for using AI agent feature in Version 5.1.2
- For using the AI agent feature in watsonx Orchestrate, you must enable the
default models. Choose one of the following options:
- You can enable
llama-3-1-70b-instructas default to use AI agent features and other features in watsonx Orchestrate. This model requires a minimum of 4 GPUs. - You can enable two Granite models:
ibm-granite-8b-unified-api-model-v2andgranite-3-8b-instruct. Enabling both the models require a minimum of 2 GPUs. In addition, you must update the models through an API to use the AI agent and other features. For more information, see Updating the Granite models.
To enable
llama-3-1-70b-instructas default, use the following command:
To enableoc patch wo wo \ --namespace=${PROJECT_CPD_INST_OPERANDS} \ --type=merge \ --patch='{ "spec": { "watsonAssistants": { "config": { "configOverrides": { "enabled_components": { "store": { "ifm": true } }, "watsonx_enabled": true, "ifm": { "model_config": { "ootb": { "llama-3-1-70b-instruct": {} } } } } } } } }'ibm-granite-8b-unified-api-model-v2andgranite-3-8b-instruct, use the following command:oc patch wo wo \ --namespace=${PROJECT_CPD_INST_OPERANDS} \ --type=merge \ --patch='{ "spec": { "watsonAssistants": { "config": { "configOverrides": { "enabled_components": { "store": { "ifm": true } }, "watsonx_enabled": true, "ifm": { "model_config": { "ootb": { "granite-3-8b-instruct": {} }, "syom": { "ibm-granite-8b-unified-api-model-v2": {} } } } } } } } }' - You can enable
- Updating the Granite models in Version 5.1.2
-
Note: Before you start to update, you must create a Zen API key using Generating a Zen API key.
- Enabling the GPU feature for Version 5.1.0 and 5.1.1
-
watsonx Orchestrate uses the watsonx Assistant's GPU feature, which is disabled by default. GPU configuration is a prerequisite to use features such as Skill-based actions and Conversational search. To enable GPU features on watsonx Assistant through watsonx Orchestrate, run the following command.
For more information about supported GPUs, see Hardware requirements for watsonx Orchestrate.oc patch wo wo \ --namespace=${PROJECT_CPD_INST_OPERANDS} \ --type=merge \ --patch='{"spec": {"watsonAssistants": {"config": {"configOverrides": {"enabled_components": {"store": {"ifm": true}}, "watsonx_enabled": true}}}}}'
What to do next
wxo-assistant-ab
watsonx Assistant service instance. For more
information, see Giving users access to a watsonx Orchestrate instance. - Enable manual scaling for the IBM Software Hub control plane. For more information, see Manually scaling resources for services.
- Complete the mandatory post-installation setup tasks to enable users to access watsonx Orchestrate. For more information, see Post-installation setup for watsonx Orchestrate.