Migrating Projects from Legacy Engines
You can migrate legacy engine projects to use ML Runtimes.
Open the selected project that uses the Legacy Engine.
Observe the current Project Settings options.
Using the Project Settings page, switch to ML Runtime.
You should be able to see the ML Runtime selector when you start a new Session.The Project Overview page might display warnings for workloads (for example, Jobs) that are configured to use Legacy Engines.
If the project has jobs, update each job to use your preferred ML Runtime.
In this Churn modeling example, switch each workload to the following:
- Editor - Workbench
- Kernel - Python 3.6
- Edition - Standard
- Version: 2021.02 Runtimes
- You can now use the following sequence to retrain your Churn model using ML Runtimes via the updated jobs:
- Install dependencies.
- Ingest data.
- Train Model.
If the project has models, redeploy each model to use ML Runtimes.
Validate that the endpoint is using ML Runtime.You can also test the Model.
If the project has applications, redeploy each application to use ML Runtime.
The Applications detail page will display a warning that the Legacy Engine is configured.
- Redeploy the application based on the required ML Runtime.
- When the application is restarted, check to ensure it is up and running.
Optionally, you can follow the same steps to update Runtime kernels from using Python
3.6 to Python 3.7.