Deploy distributed scalable remote services

This section describes how to deploy the remoteservices and V2V services as the second step in deploying a staged Abiquo distributed scalable environment.

At the end of this deployment, you should be able to create a datacenter and add a hypervisor.

Install 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

Download the remoteservices and v2v OVA files and launch them on your hypervisor
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
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
Repeat the above steps for the V2V server

Remote services firewall requirements

From	To	Notes
Server appliance	8009/tcp
	8010/tcp
	4822/tcp	Remote access server with Guacamole

V2V firewall requirements

From	To	Notes
Server appliance	8009/tcp
Server appliance	8010/tcp

Configure other firewalls

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

NFS server

Source	Destination	Input port	Description
Remote services (RS & V2V), hypervisor	NFS	TCP/UDP 2049	NFS
Remote services (RS & V2V), hypervisor	NFS	TCP/UDP 111	RPC

Hypervisors

Source	Destination	Input port	Description
Remote services (RS & V2V)	vCenter or ESXi	TCP 443

Allow ICMP

You must allow ICMP between all components of the Abiquo platform, including hypervisors.

Configure Abiquo properties

Log in to the Remote services server as root
Edit the /opt/abiquo/config/abiquo.properties file
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 
```
Save the file and restart the abiquo-tomcat server

Configure HTTPS for the AM

To let users upload or download templates, you will need to configure HTTPS for the AM.

See Add certificates for distributed scalable

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