Versions Compared

Old Version 12

changes.mady.by.user MS

Saved on

compared with

New Version 13

changes.mady.by.user MS

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Info

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 Remote services remoteservices appliance contains the Abiquo private datacenter and public cloud provider management components. A For each private datacenter, you must install a Remote services appliance is required for each private datacenter .

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

...

  1. Download the remoteservices and v2vservices v2v 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 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. server-ovaserverova.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

...

Note

Allow ICMP

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

Configure Abiquo properties

  1. Log in to the Remote services 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

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

  4. 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 Abiquo environmentdistributed scalable

...

Validating the remote services and V2V services install

...