Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.

Abiquo 4.7

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 64 Next »


The following components have requirements that must be fulfilled before you deploy an Abiquo environment:

  • Clock synchronization: Platform clocks must be synchronized. Abiquo will use NTP to keep platform clocks synchronized. Check your vendor documentation for other components.
  • VM repository folder: A unique NFS or CIFS dedicated shared folder must be present in each Abiquo DC before deployment. Check NFS Server Setup for more details.
  • Hypervisors: Check your HVs requirements in the corresponding Cloud Node documentation.
  • Network: A trunk capable network segment with VLAN tagging capabilities is required.

Before you install a test or production environment, check the essential prerequisites steps for your environment. See Abiquo Prerequisites.

For supported versions additional information, see the Compatibility Tables


Every time a VM is deployed, Abiquo creates its NICs and attaches them to the corresponding networks inside the service network. Abiquo manages the service network in different ways depending on the underlying network solution:

  • Standard VLAN network management
  • SDN management

Standard VLAN management uses ISC DHCP servers with OMAPI support and DHCP relay servers to manage the IP networks. Check the links below for further details:

For SDN as VMware NSX and OpenStack Neutron, check the configuration requirements in the links below:

Finally, Abiquo can inject network connections into the VMs using cloud-init or hypervisor tools, which requires VM templates that support these methods. Abiquo will use this option if the DHCP server is not found.

VM repository folder

In Abiquo, all private DCs must have their own VM repository folder, which holds the VM templates for all enterprises in each DC.

 The Monolithic, Remote Services and V2V appliances and your HVs must be able to mount and manage this folder remotely depending on the underlying HV technology.

When you configure the platform, enter the location of the VM repository folder, and the platform will automatically configure the appliances to use it as VM repository and mount it automatically on the HVs when needed.

For further details, please check the VM repository documentation at the link below:

Environment installation

Once your infrastructure fulfills the requirements, choose whether you will deploy a Monolithic Environment or a Distributed Environment.

You will need to install the Abiquo appliances corresponding to the environment, and optionally, the monitoring appliance.

These appliances require some configuration parameters before deployment. Some of them are common, while others are specific to the appliance functions inside the platform.

These details are required during the bootstrap process, and you must have them in place before the deployment:

These are the common requirements for both Abiquo platform appliances:



Friendly hostnameThis is the name the appliance will use internally. Abiquo does not use this for anything and it can be freely choosen.

Management IP address

IP of the management NIC

Management IP netmask

Netmask of the management NIC

Default gatewayDefault gateway in the management network
DNS server listIPs of DNS servers separated by a blank space
NTP server listAbiquo appliances use NTP to fulfill the platform clock synchronization requirements

It is a good idea to document the required information for each component in the corresponding worksheet in the links below. We provide an empty worksheet and an example for you to document all the Abiquo platform relevant configuration details:

  • Monolithic environments install all the Abiquo components inside the same appliance, and they are good for probe of concept and testing purposes
    Monolithic environments only require a monolithic appliance, and optionally, a monitoring appliance.
    Monolithic Environment

  • Distributed environments separate Abiquo components depending on they characteristics for improved performance and reliability, and they are good for production environments
    Distributed environments require at least one Server, one Remote Services and one V2V appliance.
    Distributed environment

Monitoring installation

This step is completely optional

The Abiquo monitoring appliance is completely optional. To deploy the Monitoring appliance, you need the following requirements:



Server management IP addressAbiquo server IP management address, which will be used to connect to the RabbitMQ services (Port 5672)

 The remote services appliance must be reachable from the monitoring appliance at the ports below:


Destination port


Monolithic appliance

TCP/36638 (HTTP)

Monitoring services

Follow the steps in Deploy the Abiquo appliances for further details. 

Once installed:

  1. Edit the monitoring appliance properties to set the data retention policy. See the following link for further details: Abiquo monitoring appliance configuration

  2. Edit the monolithic/server/remote services appliance /opt/abiquo/config/abiquo.properties file, add the properties below. Remember to replace the MONITORING_IP by the monitoring appliance management IP: 

    # Enable/disable monitoring and alarms
    abiquo.monitoring.enabled = true
    # Address where watchtower is located
    # Port where watchtower is listening
  3. Restart the abiquo-tomcat service in the Abiquo appliances for the monitoring changes to be applied:

    service abiquo-tomcat restart


Check the links below accordingly to the environment where the Abiquo appliances will be deployed:

Post-installation steps

  1. Change the Abiquo default passwords as soon as possible (Base OS and UI passwords)
  2. Extend the appropriate filesystems accordingly to the VM templates sizes that the environment will manage
  3. Review the appliances /opt/abiquo/config/abiquo.properties file. You may need to tune it depending on your environment configuration.
  4. If the Server appliance is not connected to the internet, configure the UI accordingly.
  5. Monitor the appliance to prevent outages: See Monitor platform servers
  6. Work through the section on Configuring Abiquo

Log In to the Abiquo UI

Now open your web browser and type in the site address for the Abiquo server.


The default cloud administrator login username and password are admin and xabiquo, respectively. Remember to change these credentials as soon as you log in for the first time.

Add a License

The link below describes how to get an Abiquo license and add it to the platform:

Configure a platform license

Further steps

For an overview of the Abiquo platform work through the tutorials built in to the product or try the Abiquo Quick Tutorial.

The following components are optional and you do not need them in a trial environment. Check the related links for further details on each component:

UI configurationSee Configure Abiquo UI
UI brandingCheck Abiquo Branding Guide
Abiquo platform configurationChange the platform settings accordingly to your needs: Configuring Abiquo
Public Cloud providersConfigure AWS, Azure ARM, or other supported cloud providers: Public cloud provider features
CollectdUse Abiquo collectd plugin integration for customized metrics: Use collectd plugin for custom metrics 
Persistent StorageConfigure NFS storage as vFiler on NetApp or Nexenta: Storage Servers
Jaspersoft ReportsFor Abiquo reports. Check Install Abiquo Reports
Chef Server integrationCheck Abiquo Chef Integration Guide


  • No labels