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

Versions Compared


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

Table of Contents

This page describes the key platform components and their installation on different appliances in production and test environments.

Abiquo platform servers

Abiquo UI allows cloud consumers to interact with the resource cloud through the Abiquo platform servers. The following table and diagram describe the main Abiquo platform servers:


The server contains the business logic and it manages all the private datacenters and public cloud regions. Also, It handles and stores all of the information and events created in the cloud environment.


Each private datacenter and public cloud region has a Remote Services server to perform the operations requested by the Abiquo Server on the infrastructure, including storage, networking and Apps library related tasks.

Consider this example of how the storage remote service works: when a cloud user creates a volume in the user interface, Abiquo communicates with the storage manager, which communicates with the API of the storage device to create the volume.


The V2V (Virtual to Virtual conversion) services server is one of the remote services but it is usually installed on a separate server for performance reasons.

It is a process that runs when users download VM templates, create VM instances, or when a new template is uploaded to convert it into the default format for each Hypervisor in the platform. If there are no hypervisors present, it will convert templates into the default base formats of all hypervisors .


Appliance library

A key element in Abiquo is the Appliance library. In private cloud,  cloud and enterprise administrators upload VM templates to the Appliance Library, for users to easily create their own VMs. The Appliance library stores disks on NFS shares called NFS repositories. Each private datacenter must have its own private NFS repository.  In public cloud regions,  Abiquo caches the cloud provider public templates details instead of using a NFS repository.

Production installations

In production installations, the servers are configured as Distributed environments with separate Abiquo components for improved performance and reliability. Distributed environments require at least one Server, one Remote Services and one V2V appliance for private cloud, and usually, a monitoring appliance. 

Image Removed

For more information, see Distributed environment

Datacenters and public cloud regions

The diagram below shows an Abiquo Server managing several private datacenters in a distributed environment.  The important point to note is that each private cloud datacenter has its own NFS repository and Remote Services server. 

Image Removed

Test installations

Test installations are usually Monolithic environments with all the Abiquo components on the same appliance, which is useful for proof of concept and other testing. Monolithic environments only require a monolithic appliance, and optionally, a monitoring appliance.

Image Removed

For all the requirements to install a monolithic test environment, see Monolithic Environment


Include Page
Abiquo Components
Abiquo Components