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


To deploy a trial environment, you need to get and deploy the Abiquo Monolithic appliance in your infrastructure and configure it according to your datacenter environment. In addition, you can optionally deploy the Abiquo Monitoring appliance.

The following components have requirements that must be fulfilled to deploy an Abiquo trial environment:

  • Hypervisors
  • Network
  • VM repository folder
  • Monolithic appliance
  • Monitoring appliance (Optional)

Some appliance requirements are common, while others are specific to the appliance functions and requirements inside the platform.

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:

The link below shows an example worksheet:


The following requirements must be fulfilled in the infrastructure for Abiquo deployment to work as expected:

VM repository folderA unique NFS or CIFS dedicated shared folder must be present in each Abiquo DC before deployment. Check NFS Server Setup for more details
HypervisorsAbiquo recommends ESXi with vCenter, Hyper-V or KVM. Check your HVs requirements in the Cloud Node documentation
Clock synchronization

Platform clocks must be synchronized. Abiquo will use NTP to keep platform clocks synchronized. Check your vendor documentation for other components

Service networkA trunk capable network segment with VLAN tagging capabilities.

For versions, see Compatibility Tables 

For server specifications, see Trial Requirements


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:

Also, 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.

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


For the trial deployment, you will need to install the Abiquo monolithic appliance, and optionally, the monitoring appliance.

These are the common requirements for both Abiquo platform appliances. All appliances require these details during the bootstrap process, and you must have them in place before the deployment:



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

You will need to enter the parameters below during the server appliance installation:



Server FQDN

This FQDN must be resolvable from customer premises, in order for SSL and the Appliance manager to work as expected. Abiquo will use self-signed certificates for trial environments

Abiquo Datacenter IDInternal ID of the trial DC. It must be unique for each DC, and all remote services and V2V appliances inside the DC must use the same datacenter ID
NFS Template repositoryNFS share for the VM repository of the DC. Each private DC must have a different NFS share

The monolithic appliance must be reachable from customer premises through its FQDN at the ports below:


Destination port




It will be redirected to port 443 by default

AnywhereTCP/443 (HTTPS)Proxy port for API/AM/UI services
AnywhereTCP/41337 (HTTPS)Proxy port for VNC services
Monitoring applianceTCP/5672RabbitMQ default port for Abiquo components to exchange messages

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

VM repository folder

In Abiquo, all DCs must have their own VM repository folder, which holds the VM templates for all enterprises in each DC. The Remote Services and HVs must be able to mount and manage this folder through NFS or CIFS (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 this folder as VM repository and mount it on the HVs when needed automatically.

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

Deploy the Abiquo appliances

We assume you will be installing the Abiquo appliances in a VMWare environment. If you are deploying the appliances in a different environment, you will need to deploy the OVAs first and configure them manually later, as described in the link below:

Deploy the Abiquo appliances in other environments

Download the corresponding Abiquo appliance. During their deployment, you will need the values of each OVA properties as described in the previous sections.

The steps to install the appliances on ESXi are these:

  1. Download the appliance OVA from the corresponding link to your desktop
  2. Open the vCenter vSphere web client
  3. Go to Host and clusters section in the client side panel
  4. Go to Actions and click on Deploy OVF template
  5. Select Local file and choose the OVA you downloaded in step 1. Click Next
  6. The vSphere client will display the OVA details. Click Next
  7. Accept the EULA and click Next
  8. Edit the deployed VM name and choose where you want to deploy it. After this, click Next
  9. Select which cluster or host will be used for deploy and click Next
  10. Choose the datastore for the deployed VM and click Next
  11. Select the network destination for the VM management NIC and click Next
  12. Enter the template details depending on the OVA you are deploying. For more details, see the parameters table above. When configured, click Next
  13. Review the deployment configuration details. If they are OK, you can select the "Power on after deployment" checkbox. But if you need to add extra NICs and HDDs to the VM before deployment, do not select it. Click Finish

Enable monitoring

For monitoring to work, on the monolithic appliance file /opt/abiquo/config/abiquo.properties, add the properties below and restart the abiquo-tomcat service after. 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

Post-install steps

  1. Log into the Abiquo UI in the https://FQDN URL.
  2. Remember to change the Abiquo default passwords as soon as possible (Base OS and UI passwords)
  3. Template operations will require space on the Monolithic appliance before they are moved the VM repository. Extend the appropiate filesystems accordingly if you will be using big templates.
  4. Edit the monitoring appliance properties to set the data retention policy. See the following link for further details: Abiquo monitoring appliance configuration

  5. review the monolithic appliance /opt/abiquo/config/abiquo.properties file. You will probably need to configure some of the following properties:

    • For Hyper-V or XenServer hypervisors, you may need to configure the repository location properties which are described as part of the hypervisor configuration

    • To use a monitoring server, enter the monitoring server IP address and port, and enable it

After changing the appliances /opt/abiquo/config/abiquo.properties file, remember to restart the Abiquo Tomcat service always:

service abiquo-tomcat restart

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 your password 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