Goal

Provide users a way to automate VM renaming, so it fits RFC 1123, during the migration.

Background

The validation service includes a check for VM names so that they fit RFC 1123 and can exist with their original name in the target.

Customers use characters, such as dots ".", in the VM names that end in having the VM marked as critical for migration making it non-migratable.

The workaround currently being proposed is to automate renaming of the VMs to be migrated as the first step before the migration, reverting the changes once the migration is completed. This is doable but causes a lot of friction.

User Stories

As a migration owner, when creating a migration plan that has VMs with non-conformant names, I would like the ability to change the name of the target VM on the fly before it is migrated.

As a migration owner, I'd might also want to rename a VM if that name is already used by another VM inside OpenShift virt.

Implementation Notes

Being able to integrate the change in the MTV tool itself, instead of as a hook, would help reduce friction.

Suggestion by Kobi Gershon:
Allow with a checkbox at the beginning of the migration process that if a VM with the same name exists, that the migration will change the name automatically, optionally with a warning to the user on that.
For example, if the customer is migrating VMs that are for test/lab/etc, and doesn’t really care about the name
he can use this option.