Cloudera Docs

Additional steps to check both the source and the target workbenches

Learn about additional checks to take for the source and the target workbenches before the migration.

The following additional steps must be taken to check the source and the target workbenches before the migration:

  • Make sure that you have the rsync-enabled Runtime image added to your Cloudera AI Workbench Runtime catalog. The image is hosted on DockerHub. If the rsync image is not readily accessible, the image can be created from Dockerfile hosted here and hosted in any registry. If you do not succeed, ask your workbench Administrator to make these changes.
  • Make sure that your default SSH public key is added under your user settings. If it is not, please add them in User Settings > Remote Editing > SSH public keys for session access. The default SSH public key must be available on your machine at the ~/.ssh/\<something\>.pub location. The SSH public key must be uploaded to both the source and target workbenches.
    • If no SSH key pair is defined in your system yet, create one. Cloudera recommends not setting a passphrase for the SSH key because SSH connections are established in multiple instances. If a passphrase is set, the automation using the utility might take too long.
    • The Legacy API key must be available and must be noted down, as it will be required during migration. To generate a new key, go to User Settings > API Keys > Legacy API key.