Revision history [back]

Hello there,

Coriolis' main purpose is to migrate virtual machines, and as such its API is geared towards operations on the vm level as seen in the demo videos. However, it does also bring any relevant resources directly attached to the virtual machine along with it (ex: it tries to best recreate the network topology the VM was in, add devices such as CD-ROMS, USBs etc..).

That being said, and coupled with the 'coordinated migrations' Coriolis does, it should be more that straightforward to just ask for all the VM's you need to be migrated in part.

As for rollbacks; Coriolis does NOT delete or modify any of the items on the source cloud at all by default (note that VM downtime may be necessary on some platforms though (for example on ESXi exporting a VM requires the machine to be powered off)), but Coriolis restarts them ASAP to keep lost time at a minimum. As such, there is no real need for a rollback mechanism as nothing would require it.

The 'validation' part is a bit trickier... Coriolis DOES indeed validate the instance has been migrated successfully (i.e. if they have booted properly on the destination cloud and are up and running), but it cannot reason about whether or not the application(s) running on that VM have started as expected, which is left to the VM owner(s) to determine (which could be done programmatically, but is sadly too application-specific to be within Coriolis' scope).

Hope this helped, Nashwan.