Manual verification of the migration
Learn about the main tasks to perform manually to validate the migration.
Perform the following actions to validate the migration:
- Validate the number of project files, file sizes, and project settings in the target workbench.
- In the target workbench, the user's public SSH key, which can be found at , is different from the source SSH key. Update the SSH key in all external locations, such as the github repository.
- Following the migration, the Model API key and endpoint URL are different from the source. Update all applications that utilize these APIs.
- Jobs in the target workbench have the Spark addon enabled by default. Disable it or change the Spark version if needed.
- Administrators can change the ownership of the project after the migration, if necessary.
- To add collaborators to the project follow the guidelines in Adding Project Collaborators.
- You can export the custom Grafana dashboards from CDSW and import them to Cloudera AI following the steps in Import Dashboards - Grafana documentation.
- Validate the workloads running within the Project. All the Models, Jobs or applications are created in paused or stopped state in the destination workbench, so all the artifacts must be restarted after the migration. Before starting the Models, Jobs, or Applications in the target workbench, the corresponding workloads must be stopped in the source workbench to avoid any data corruption if both workbenches are accessing the same data simultaneously.
