Upgrading the Watson OpenScale service
Upgrade scenarios for Watson OpenScale
You can upgrade Watson OpenScale directly from either version 3.5.10 or version 4.0.x to Watson OpenScale version 4.6.x
- Upgrade Watson OpenScale version 3.5.10 to Watson OpenScale version 4.6.x
- For more information, see Upgrading Watson OpenScale from Version 3.5 to Version 4.6.
- Upgrade Watson OpenScale version 4.0.x to Watson OpenScale version 4.6.x.
- For more information, see Upgrading Watson OpenScale from Version 4.0 to Version 4.6.
Upgrade scenarios for Watson OpenScale with OpenPages
The following upgrade scenarios may require you to complete tasks in OpenPages, in addition to updating information in Watson OpenScale.
- Upgrade Watson OpenScale version 3.5.10 and OpenPages version 3.5.1 to Watson OpenScale version 4.6.x and OpenPages version 3.5.1.
- You can upgrade Watson OpenScale from version 3.5.10 directly to version 4.6.x, while keeping your instance of OpenPages at version 3.5.1. Because of the security enhancements that are part of the new version of Watson OpenScale, you must update the information in the System setup > Integrations window. Specifically, you must select the location as Cloud, and update the URL, username, and password fields.
- Upgrade Watson OpenScale version 3.5.10 and OpenPages version 3.5.1 to Watson OpenScale version 4.6.x and OpenPages version 4.6.x while keeping an instance of OpenPages version 3.5.1.
- You can upgrade Watson OpenScale from version 3.5.10 directly to version 4.6.x, while keeping your instance of OpenPages at version 3.5.1. Because of the security enhancements that are part of the new version of Watson OpenScale, you must update the information in the System setup > Integrations window. Specifically, for a version 3.5.1 instance of OpenPages you must select the OpenPages location information as IBM Cloud.
- Upgrade Watson OpenScale version 4.0.x and OpenPages version 4.0.x to Watson OpenScale version 4.6.x and OpenPages version 4.6.x.
- Because of the security enhancements that are part of the new version of Watson OpenScale, you must update the information in the System setup > Integrations window. Specifically, you must add the required OpenPages location and API key information.
Upgrade scenarios for Watson OpenScale with IBM Analytics Engine Powered by Apache Spark
The following upgrade scenarios are supported for Watson OpenScale with Analytics Engine Powered by Apache Spark. Depending on your specific upgrade path, you might need to complete tasks in Watson OpenScale to re-establish the connection with Analytics Engine Powered by Apache Spark.
- Upgrade Watson OpenScale version 3.5.10 and Analytics Engine Powered by Apache Spark version 3.5.1 to Watson OpenScale version 4.6.x and Analytics Engine Powered by Apache Spark version 3.5.1.
- After you upgrade Watson OpenScale from version 3.5.10 to version 4.6.x without making changes to your Analytics Engine Powered by Apache Spark instance, you must rebuild the wos_env virtual environment.
- Upgrade Watson OpenScale version 3.5.10 and Analytics Engine Powered by Apache Spark version 3.5.1 to Watson OpenScale version 4.6.x and Analytics Engine Powered by Apache Spark version 4.6.x.
- When you create a new instance of Analytics Engine Powered by Apache Spark, you must update the subscription to use the new connection. From the Model details window, click the Analytics Engine tile, and enter the updated connection information.
- Upgrade Watson OpenScale version 4.0.x and Analytics Engine Powered by Apache Spark version 4.0.x to Watson OpenScale version 4.6.x and Analytics Engine Powered by Apache Spark version 4.0.x.
- You must rebuild the wos_env virtual environment.
- Upgrade Watson OpenScale version 4.0.x and Analytics Engine Powered by Apache Spark version 4.0.x to Watson OpenScale version 4.6.x and Analytics Engine Powered by Apache Spark version 4.6.x.
- You must rebuild the wos_env virtual environment.
Known issues with upgrading Watson OpenScale and Watson Machine Learning
After upgrade, Watson Machine Learning runtime pods are hibernated and restart only after the first scoring request. Because of the time that it takes to restart the runtime pods, the initial request might timeout. The workaround is to reattempt the scoring evaluation.
Next steps
To start the upgrade process, choose one of the following tasks: