Upgrading Watson Studio Runtimes from Version 4.8 to Version 5.0
An instance administrator can upgrade Watson Studio Runtimes from Cloud Pak for Data Version 4.8 to Version 5.0.
- Who needs to complete this task?
-
Instance administrator To upgrade Watson Studio Runtimes, you must be an instance administrator. An instance administrator has permission to manage software in the following projects:
- The operators project for the instance
-
The operators for this instance of Cloud Pak for Data are installed in the operators project. In the upgrade commands, the
${PROJECT_CPD_INST_OPERATORS}
environment variable refers to the operators project. - The operands project for the instance
-
The Cloud Pak for Data control plane and the services for this instance of Cloud Pak for Data are installed in the operands project. In the upgrade 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 upgrade the Cloud Pak for Data control plane and one or more services at the same time, follow the process in Upgrading an instance of Cloud Pak for Data instead.
- If you didn't upgrade Watson Studio Runtimes when
you upgraded the Cloud Pak for Data control
plane, complete
this task to upgrade Watson Studio Runtimes.
Repeat as needed If you are responsible for multiple instances of Cloud Pak for Data, you can repeat this task to upgrade more instances of Watson Studio Runtimes on the cluster.
Information you need to complete this task
Review the following information before you upgrade Watson Studio Runtimes:
- Version requirements
-
All the components that are associated with an instance of Cloud Pak for Data must be installed at the same release. For example, if the Cloud Pak for Data control plane is at Version 5.0.3, you must upgrade Watson Studio Runtimes to Version 5.0.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
- Storage requirements
- You don't need to specify storage when you upgrade Watson Studio Runtimes.
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 Watson Studio Runtimes. | If this task is not complete, see System requirements. |
The workstation from which you will run the upgrade is set up as a client workstation and
the following command-line interfaces:
|
If this task is not complete, see Updating client workstations. |
The Cloud Pak for Data control plane is upgraded. | If this task is not complete, see Upgrading an instance of Cloud Pak for Data. |
For environments that use a private container registry, such as air-gapped environments, the Watson Studio Runtimes 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. |
Ensure that the correct components are specified before running the upgrade. | If this task is not complete, see Watson Studio Runtimes in the Services list. |
Prerequisite services
Before you upgrade Watson Studio Runtimes, ensure that the following services are upgraded and running:
Procedure
Complete the following tasks to upgrade Watson Studio Runtimes:
Upgrading the service
cpd-cli
manage
apply-olm
updates all of the OLM objects in the operators
project at the same time.To upgrade Watson Studio Runtimes:
-
Log the
cpd-cli
in to the Red Hat® OpenShift Container Platform cluster:${CPDM_OC_LOGIN}
Remember:CPDM_OC_LOGIN
is an alias for thecpd-cli manage login-to-ocp
command. - Update the custom resources for
Watson Studio Runtimes.
cpd-cli manage apply-cr \ --components=ws_runtimes \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --license_acceptance=true \ --upgrade=true
Important: If you want to upgrade all existing runtimes automatically when you upgrade Watson Studio, specify thews_runtimes
component when you upgrade Watson Studio.If you do not specify the
ws_runtimes
component when you upgrade Watson Studio, only the default runtime is upgraded. You must upgrade the non-default runtimes manually.
Validating the upgrade
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=ws_runtimes
What to do next
If you are using custom runtime images in Watson Studio, you must create and register these images again after you have upgraded Cloud Pak for Data to rebase the image with the latest Cloud Pak for Data runtime image. See Building custom images.
The service is ready to use. For details, see Notebook environments.