Cloudera Docs

Automated verification of the migration

After the migration, an automated verification starts. Learn about what is being validated, what to consider before running the validation, and what elements do not require validation.

The automated verification ensures the validation of the following elements:
  • The similarity of project files between the source and local directories.
  • The similarity of project files between the local directory and the target.
  • The consistency in the number of Jobs, Models, and Applications between the source and target.
  • The similarity in the metadata of Jobs, Models, and Applications between the source and target.
No validation exists for the following elements:

  • Job dependencies– The migration command does not validate job dependencies at the source and target workbenches. Ensure that all necessary job dependencies are manually verified to maintain workflow integrity.

  • Environment variables– The verification process does not validate environment variables, as these variables might differ between the source and target projects. Manually verify any environment-specific configurations or variables to ensure proper functionality.

  • Hidden files or other files being continuously updated– If your Project contains hidden files or files that are continuously updated, Cloudera recommends excluding such files from validation by adding them to the .exportignore file at the root of the source Project. This ensures a more accurate comparison and prevents unnecessary discrepancies during the verification process.

  • ML Runtimes or engine– This tool does not undertake the validation of ML Runtimes or engine-related information between the source and target. Therefore, the user must ensure the accuracy and compatibility of such details.

Before running the validation command ensure the following requirements:
  • You have access to the Cloudera AI command line utility tool.
  • Python and the necessary dependencies are installed.
  • Project details are added in the export-config.ini and import-config.ini files.
  • No changes are made to the source and target before starting validation.
Open a terminal or command prompt and run one of the following commands: 
cmlutil project validate-migration -p [***PROJECT NAME***]

or

cmlutil project validate-migration --project_name [***PROJECT NAME***]