Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Install remote services and V2V server

The Remote services appliance contains the Abiquo private datacenter and public cloud provider management components. A Remote services appliance is required for each private datacenter.

The server 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 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 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

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

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 HTTPS for the AM

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

See Add certificates for Abiquo environment


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

  • No labels