Beside the command line interface (CLI), Coriolis provides a web UI designed for a guided user experience.

To begin with, just point the browser (Firefox, Chrome, Safari or Edge) to the address of your Coriolis VM. The website uses a self signed certificate by default, so you might want to add a security exception in your browser.

You can use the “admin” user to login with the password randomly generated during the deployment. To retrieve the password, just connect to the VM using SSH (default credentials: root / coriolis) and run:

Once logged in, click on “Cloud Endpoints”:

Creating an endpoint for OpenStack

After clicking on “New” you will see all available cloud endpoint options currently installed, for example:

Choose “OpenStack” and provide all the required data. Make also sure to set “Allow Untrusted” to “Yes” if your OpenStack API endpoint uses a HTTPS self signed certificate.

Once done, click “Save”. This will create the endpoint and trigger a validation of the data by attempting a connection to the OpenStack API.

Creating an endpoint for VMware vSphere

You can repeat the same procedure choosing “VMware” and provide the required data. Also in this case make sure to set “Allow Untrusted” to “Yes” if your VMware vSphere API endpoint uses a self signed certificate.

Like in the previous case, clicking “Save” will create the endpoint and trigger the connection validation.

 

Configuring a replica for a VM from vSphere to OpenStack

Click on “Replicas” and choose “New”. You will be greeted by an introductory screen:

Click “Next” and select the source endpoint (VMware):

Click “Next” and choose the target endpoint (OpenStack):

After clicking “Next” again, it’s time to select the VM(s) to migrate. You can apply filters on the name to simplify the search:

Click “Next” to set the OpenStack specific options, starting with the name of the flavor to be used:Clicking once more “Next” will bring you to the Network Mapping, where for each network used by the VM(s) on the source cloud we need to select a matching network on the target. This is where the VMs will be connected after being migrated.Click “Next” and you will see the scheduling options:

One more “Next” and you have a final confirmation screen:

Click “Finish” and the replica will start executing:You can now click on the replica to see the execution details:Once completed, the replica can be executed incrementally multiple times to update the replicated content (this is typically scheduled, e.g. hourly, daily, weekly, etc).

 

Migrating the VM from the replica

From the replica details, you can click on “Migrate Replica” to get the VM(s) running on OpenStack:

You can click on “View Migration Status” to watch the migration progress. The “migrations” view can also be reached through the main menu (click on the top left icon).Once completed, the migration status will change accordingly:

Congratulations, your VM is now running and accessible from the OpenStack Horizon dashboard: