Installing watsonx Assistant
An instance administrator can install watsonx Assistant on IBM Software Hub Version 5.2.
- Who needs to complete this task?
-
Instance administrator To install watsonx Assistant, 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 Assistant 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 Assistant 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 Assistant as part of a batch installation, complete this task
to add watsonx Assistant 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 Assistant on the cluster.
Information you need to complete this task
Review the following information before you install watsonx Assistant:
- 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.2.2, you must install watsonx Assistant at Version 5.2.2.
- 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 Assistant works with the default Red Hat® OpenShift® Container Platform security context constraint,
restricted-v2.
- Common core services
-
watsonx Assistant requires the IBM Software Hub common core services.
If the common core services are not installed in the operands project for the instance, the common core services are automatically installed when you install watsonx Assistant. The common core services installation increases the amount of time the installation takes to complete.
- Storage requirements
- You must specify storage classes when you install watsonx Assistant. 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:
- System requirements
- This task assumes that the cluster meets the minimum requirements for watsonx Assistant.
Where to find more information If this task is not complete, see System 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
Where to find more information If this task is not complete, see Setting up a client workstation. - IBM Software Hub CLI:
- 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:
- The watsonx Assistant 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. - The
cpd-cliis configured to pull theolm-utils-v3image 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.
- The watsonx Assistant software images are mirrored to the private container
registry.
- GPU operators
- If you plan to use
features that require GPUs, this task assumes that the operators required to use GPUs are
installed.
Where to find more information If this task is not complete, see Installing operators for services that require GPUs. - 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:
- Multicloud Object Gateway is installed and
configured.
Where to find more information If this task is not complete, see Installing Multicloud Object Gateway. - The secrets that enable watsonx Assistant 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.
- Multicloud Object Gateway is installed and
configured.
- 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.
- watsonx Assistant supports only single-zone OpenShift deployments. It does not support multi-zone deployments.
- You cannot install watsonx Assistant and watsonx™ Orchestrate on the same instance of IBM Software Hub. If you want to install these services on the same Red Hat OpenShift Container Platform cluster, you must install each service on a different instance of IBM Software Hub. For more information see Multitenancy considerations.
Procedure
Complete the following tasks to install watsonx Assistant:
Specifying installation options
If you plan to install watsonx Assistant, you
can specify the following installation options in a file named install-options.yml in the cpd-cli
work directory (For example: cpd-cli-workspace/olm-utils-workspace/work).
The parameters are optional. If you do not set these installation parameters, the default values are used. Uncomment the parameters that you want to override and update the values appropriately.
The sample YAML content uses the default values.
################################################################################
# watsonx Assistant parameters
################################################################################
#watson_assistant_size: Production
#watson_assistant_bigpv: false
#watson_assistant_analytics_enabled: true
#watson_assistant_watsonx_ai_type: embedded
#watson_assistant_syom_models: []
#watson_assistant_ootb_models: []
| Property | Description |
|---|---|
watson_assistant_size |
The deployment size for watsonx Assistant. The deployment size determines the number of resources allocated to watsonx Assistant.
|
watson_assistant_bigpv |
Specify whether to create larger physical volumes to improve IOPS performance. Create larger physical volumes if your storage class IOPS performance depends on the size of the physical volume. Important: You cannot change this setting after you install watsonx Assistant.
You do not need to create larger physical volumes if you use the following storage:
|
watson_assistant_analytics_enabled |
Specify whether to store chat logs and analytics.
|
watson_assistant_watsonx_ai_type |
Specify this option if you want to install Inference foundation models (watsonx_ai_ifm) to enable the following features, which require GPUs:
Omit this option if you do not want to enable the preceding features. For more information about supported GPUs, see the GPU requirements for models.
|
watson_assistant_syom_models |
Specify whether you want to use a specialized model that is specifically tuned for use with
watsonx Assistant for:
Important: The following models will be automatically installed if
you install Inference foundation models
(
) and
you do not specify a value for watson_assistant_syom_models or
watson_assistant_ootb_models:
|
watson_assistant_ootb_models |
Specify whether you want to use a general model for:
Important: The following models will be automatically installed if
you install Inference foundation models
(
) and
you do not specify a value for watson_assistant_syom_models or
watson_assistant_ootb_models:
|
Installing the service
To install watsonx Assistant:
-
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. - Run the following command to create the required OLM objects for watsonx Assistant in the
operators project for the
instance:
cpd-cli manage apply-olm \ --release=${VERSION} \ --cpd_operator_ns=${PROJECT_CPD_INST_OPERATORS} \ --components=watson_assistantWait 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 Assistant.
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=watson_assistant \ --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=watson_assistant \ --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=watson_assistant \ --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=watson_assistant \ --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 Global Data Platform storage
Remember: When you use IBM Fusion Global Data Platform storage, both${STG_CLASS_BLOCK}and${STG_CLASS_FILE}point to the same storage class, typicallyibm-spectrum-scale-scoribm-storage-fusion-cp-sc.Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=watson_assistant \ --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=watson_assistant \ --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 Storage Scale Container Native storage
Remember: When you use IBM Storage Scale Container Native storage, both${STG_CLASS_BLOCK}and${STG_CLASS_FILE}point to the same storage class, typicallyibm-spectrum-scale-sc.Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=watson_assistant \ --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=watson_assistant \ --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=watson_assistant \ --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=watson_assistant \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --storage_vendor=portworx \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
AWS with EFS storage only
Remember: When you use EFS storage, both${STG_CLASS_BLOCK}and${STG_CLASS_FILE}point to the same storage class, typicallyefs-nfs-client.Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=watson_assistant \ --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=watson_assistant \ --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
AWS with EFS and EBS storage
Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=watson_assistant \ --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=watson_assistant \ --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
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=watson_assistant \ --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=watson_assistant \ --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=watson_assistant
What to do next
Your next steps depend on the version of IBM Software Hub that you upgraded to:
- Version 5.2.1 or later
-
After you complete the preceding steps, watsonx Assistant is ready to use.
- Version 5.2.0
-
- If your watsonx Assistant installation does not use GPU features:
After you complete the preceding steps, watsonx Assistant is ready to use.
- If your watsonx Assistant installation uses GPU features, such as skills-based actions and
conversational search:
- Install the services that you need on this instance of IBM Software Hub
- Apply the IBM Software Hub Version 5.2.0 - Day 0 patch
You must apply the patch to each instance of IBM Software Hub Version 5.2.0 that you install.
- Complete Creating a service instance for watsonx Assistant from the web client.
After you complete the preceding steps, watsonx Assistant is ready to use.
- If your watsonx Assistant installation does not use GPU features: