Page Comparison

...

1. Download the remoteservices and v2vservices OVA files and launch them on your hypervisor

2. Enter the standard parameters, which are as follows:

   1. Friendly hostname, e.g. rs-ova and v2v-ova, which must be a valid Linux hostname

   2. Management interface IPv4 Address, e.g. 10.60.10.110, which should be a static network configuration

   3. Management interface IPv4 Netmask, e.g. 255.255.255.0

   4. Default Gateway, e.g. 10.60.10.1

   5. Space separated DNS Server list, e.g. 10.60.10.1

   6. Space separated NTP Server list, e.g. 10.60.10.1, which is required for features that depend on clock synchronization

3. Enter the remoteservices OVA parameters, which are as follows:

   1. Abiquo API server FQDN, e.g. server-ova.abiquo.com

      1. This FQDN must be resolvable from customer premises for SSL and the Appliance manager to work properly

   2. Abiquo Datacenter ID, e.g. 10.

      1. The datacenter ID must be unique for each DC, and all remote services and V2V appliances inside the DC must use the same datacenter ID

   3. NFS template repository, e.g. 10.60.10.25:/volume1/nfs-t.

      1. This is the NFS share for the VM repository of the DC. Each private DC must have a different NFS share

   4. RabbitMQ IP, e.g. 10.60.10.185, which is the IP address of the datanode server

4. Repeat the above steps for the V2V server

...

• Log in to Abiquo and create a datacenter, then create a virtual datacenter, and ideally, deploy a VM. To do this, follow the steps in the Abiquo quick tutorial

...