Deploy distributed scalable remote services

Remote services and V2V server

The remoteservices appliance contains the Abiquo private datacenter and public cloud provider management components. For each private datacenter, you must install a Remote services appliance .

The v2v appliance contains the Abiquo virtualization format conversion components, and it is isolated for performance reasons. This appliance creates conversions, so we recommend fast HD storage and networking for it.

Requirements

Remote services installation requirements

• 2 CPUs

• 8 GB RAM

• 64 GB HD

V2V services installation requirements

• 2 CPUs

• 4 GB RAM

• 256 GB HD (Depending on template conversion requirements. Get in touch with Abiquo support for further information)

Install remote services and V2V server

The same steps apply to remote services and V2V servers

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

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

   1. Friendly hostname, e.g. rsova and v2vova, 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. serverova.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

Remote services firewall requirements

V2V firewall requirements

Configure other firewalls

Additionally, open the following ports on the NFS server and hypervisors.

NFS server

Hypervisors

Configure Abiquo properties

Remote services

1. Log in to the remoteservices server as root

2. Edit the /opt/abiquo/config/abiquo.properties file

3. Check the RabbitMQ port is correct and deactivate monitoring until you have installed the monitoring server

   abiquo.rabbitmq.addresses = 10.10.203.212:5672 abiquo.monitoring.enabled = false

4. Save the file and restart the abiquo-tomcat server

V2V services

1. Log in to the v2v server as root

2. Edit the /opt/abiquo/config/abiquo.properties file

3. Check the RabbitMQ port is correct

   abiquo.rabbitmq.addresses = 10.10.203.212:5672

4. Save the file and restart the abiquo-tomcat server

Configure HTTPS for the Remote services

To upload or download templates, you will need to configure HTTPS for the Appliance Manager remote services.

To improve security or to support connections over the internet to remote services in a different location, configure TLS for all remote services. See https://abiquo.atlassian.net/wiki/spaces/ABI61/pages/652333999

Validating the remote services and V2V services install

Log in to Abiquo and create a datacenter, then create a virtual datacenter, and deploy a VM.

To do this, follow the steps in the Abiquo quick tutorial

Next steps

Install Abiquo Monitoring server. See Deploy distributed scalable monitoring server