This section describes about the Revert operation.
This outcome is irreversible. The VMs will be permanently deleted. Ensure that the input and VM details (VM names) are proper. The intention is to delete failed VMs (3.0 VMs). The migration tool has some safety checks for wrong VM names (that are not TCA VMs and the version) and failed revert operation. This operation is recommended to revert entire topology. The tool does not check whether appliances are successfully migrated and it deletes all the specified appliances.
To revert the migration, run the revert CLI to delete the new 3.0 VMs and power on the 2.3 VMs.
revert CLI
$ python3 vm_cn_migration.py revert -h
usage: vm_cn_migration.py revert [-h] input_file
Reverts the migrated setup to original setup. Deletes new appliance(s) and powers on the VMware-Telco-Cloud-Automation-e old appliance(s)
positional arguments:
input_file input file containing TCA manager and TCA-CP details.
options:
-h, --help show this help message and exit
Following is the usage:
revert CLI
python3 vm_cn_migration.py revert input.json
If you retry migration after revert, wait for three minutes for the 2.3 VMs to power on and initialize.
If you revert to 2.3 setup and use it for a while before trying again, ensure that you delete old backups by using -c option with e2e-migrate or backup CLI to migrate new or modified data.
