Migrating Runtime 22.1 environments from Cloud Pak for Data 4.6 or 4.7

When you upgrade to Cloud Pak for Data 4.8, only the following Python and R runtimes are available:

Runtime 23.1 on Python 3.10 (with and without GPU)
Runtime 22.2 on Python 3.10 (with and without GPU)
Runtime 22.2 on R 4.2
Runtime 23.1 on R 4.2
JupyterLab with Runtime 23.1 on Python 3.10
JupyterLab with Runtime 22.2 on Python 3.10
Default Spark 3.3 & Python 3.10
Default Spark 3.4 & Python 3.10
Default Spark 3.3 & R 4.2
Default Spark 3.4 & R 4.2

You can select any of the default environments with Python 3.10 or R 4.2 that are included in Watson Studio, or create custom environments that use Python 3.10 or R 4.2. You can also continue using environments that use Python 3.9 or R 3.6, if you perform a migration step that is detailed in the following section.

Note: You must migrate these environments before you upgrade. You won't be able to migrate them after you upgrade.

You can no longer select any default Python 3.9 or and R 3.6 environments because these environments are no longer included in Watson Studio. This means that you can't start notebooks or JupyterLab, run jobs, or create custom runtime images that use these environments.

What does this mean for existing Python and R notebooks and jobs?

After you upgrade to Cloud Pak for Data 4.8:

The Default Python 3.9 and Default R 3.6 environments are not available anymore. Notebooks and jobs that use these environments will not run.
Custom environments with Default Python 3.9 or Default R 3.6 as software version will be migrated, but all notebooks and jobs associated with these environments will not run. Also, these custom environments will become corrupted when they are exported from a project and can't be used if imported to a new project. Issues can also occur in Git-based projects.
Custom environments that you created based on custom runtime definitions will still be valid. Notebooks and jobs that are associated with these environments will still run.

Before you upgrade to Cloud Pak for Data 4.8:

Evaluate the differences between the libraries that are used in the environment runtime that you are currently using and the libraries that are used in the 22.2 or 23.1 runtime environments. Then, evaluate the code changes that you must make.
If you are on Cloud Pak for Data 4.6 or 4.7 and you want to continue using the Default Python 3.9 or Default R 3.6 runtime:
1. Download the appropriate runtime configuration file. See Downloading the runtime configuration.
  - For Notebooks, use one of the following runtime definitions:
    - jupyter-py39
    - jupyter-py39gpu
    - jupyter-r36py39t1
  - For Jupyterlab, use:
    - jupyter-lab-py39
    - jupyter-lab-py39gpu
2. Rename the runtime configuration, for example, to cpd47-py39-server.json.
3. Upload the file to the Cloud Pak for Data cluster. See Step 7 in Uploading the custom configuration.
4. Switch to using an environment with this image in your notebooks and jobs. For details, see Changing the environment of a notebook.
5. Test run the notebooks and jobs.
6. If they run successfully, you can upgrade to Cloud Pak for Data 4.8. Your custom environments with this change will be migrated.
If you determined that your existing notebooks and jobs work with the Runtime 22.2 or the Runtime 23.1 environment (for Python 3.10 and R 4.2):
1. Upgrade to Cloud Pak for Data 4.8.
2. Go to your existing notebooks and jobs, and select a Runtime 22.2 or a Runtime 23.1 environment.
Optional: (only if ws_runtimes was not included in the components list when you ran the upgrade script: cpd-cli manage apply-cr --upgrade=true --components=....). After you upgrade to Cloud Pak for Data 4.8, delete any remaining Jupyter Notebook runtimes with Python 3.9 or R 3.6:
1. Run the following command to see which runtimes are installed:
```
$ cpd-cli manage get-cr-status \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=ws_runtimes
```
2. If one of the following environments is included in the output:
  - ibm-cpd-ws-runtime-py39
  - ibm-cpd-ws-runtime-py39gpu
  - ibm-cpd-ws-runtime-r36
  Delete the runtime by running the following command:
```
oc delete -n ${PROJECT_CPD_INST_OPERANDS} --ignore-not-found NotebookRuntime ibm-cpd-ws-runtime-py39 ibm-cpd-ws-runtime-py39gpu ibm-cpd-ws-runtime-r36
```

Parent topic: Environments