The Abiquo Monolithic server is a simple environment suitable for trial and proof-of-concept environments.
The Monolithic Appliance includes Abiquo Server, Abiquo Remote Services and Abiquo V2V Services on the same host. It does not include the NFS repository.
The Monolithic Appliance is a single server installation of the full Abiquo platform. You can use this platform to manage separate hypervisors and external storage in demonstrations or very small environments. Remember that the server where you are installing the Abiquo platform will also be performing the virtual image conversions. The number and size of the VMs you deploy using this setup may affect the performance of your system.
The Monolithic platform can support a single private cloud datacenter with hypervisors and Docker, as well as a number of public cloud regions.
The following diagram shows the monolithic install. The main connections configured during this install process are shown with solid black lines.
You can extend the monolithic install to add more private cloud datacenters and public cloud regions. To do this, install another Remote services server.
It is important to install and configure the following Abiquo platform components in this order :
The Abiquo monolithic appliance has the following system requirements.
test server specifications
If you just want to "try out" Abiquo with a few small virtual machine templates, you can run the virtual machine as it is! However, you should keep an eye on logs and disk space.
For Abiquo DHCP server without a separate DHCP relay server, install the Abiquo Monolithic Appliance on a hypervisor with VLAN support configured. For example, for ESXi, see How to configure an ESXi host to support VLAN tagging
Connect the Abiquo Monolithic server to these platform networks:
For GoogleMaps, Abiquo remote image repository, public cloud
|vCenter Integration (optional)|
vCenter admin credentials are required
Download Abiquo Monolithic Appliance and check the MD5 sum.
Load the appliance into your hypervisor and check the configuration. The following table describes the default appliance settings.
|Guest OS Type||Red Hat (64 bit)|
|Network adapter||Intel PRO/1000 MT Server|
|Hard Disk Controller (SCSI)||LsiLogic|
|Virtual Disk Image Capacity||9.77 GB|
Connect to the Management Network and for this interface configure the network with a VLAN tag that is not trunked in the switch and will be EXCLUDED from the tags available to Abiquo for assigning to private networks.
If you are using the Abiquo Server's built-in DHCP server, connect to the Service Network, which should be configured in trunk mode to support virtual networks.
After you click Accept, a confirmation screen will advise you to wait. Click OK to continue.
Abiquo requires an NFS repository that will hold the VM template library for private cloud. Abiquo will mount the NFS repository on the Abiquo Remote Services and V2V Server. It will also configure the NFS repository in the abiquo.properties file of the Abiquo Server. This will enable the template repository to be mounted on your hypervisors.
Enter the IP address in the <nfs-ip> field and the exported directory (by default this is /opt/vm_repository). For example, mynfs.exmaple.com:/opt/vm_repository
The IP address cannot be a localhost value (127.0.0.1 or localhost). It must be reachable by other hosts in your LAN.
If you are installing Abiquo to use with a public datacenter only, no NFS repository is required, so you can enter a valid IP address where no NFS server is present.
Enter the unique ID for the physical datacenter where this remote service is being installed and click OK to continue.
The Datacenter ID must be the same as it is for the other Remote Services of this datacenter and different from all other datacenters. This ID is used to configure the RabbitMQ queues and the routing keys. The configuration information you enter on this screen is used to configure the abiquo.properties file. See Abiquo Configuration Properties#Datacenter
On a test monolithic machine, you should accept the default endpoint, which is the IP address of the monolithic server.
Abiquo recommends that you always use SSL for your platform. This will enable your users to make secure connections from the client UI to the UI Server. However, you could run the platform without SSL for a very basic test install.
The installer will extract the default randomly-generated M user password from the Abiquo database and add the M user credentials the Abiquo properties file. The M user credentials is required for completing event details in Abiquo and event streaming. If you change the credentials of the M user in Abiquo, you must also change them in the Abiquo properties file. See Abiquo Configuration Properties#Configure Abiquo Events Properties
When the configuration is complete, Abiquo will display the address where you can log in and the login details. Remember to change your Abiquo passwords as soon as possible.
The Monolithic Server is a CentOS system. After install, log in and configure the server, including:
Edit the Abiquo Configuration Properties file, which by default can be found at:
Set the recommended properties as described in the Abiquo Administrator's Guide.
Some example configuration properties may be:
the monitoring server IP address and port
for Hyper-V or XenServer hypervisors, the repository location properties which are described as part of the hypervisor configuration
to enable Docker, enter the Docker repository location
for virtualized KVM servers, enter the fullvirt property
See Abiquo Configuration Properties for a complete properties reference.
After completing the configuration step, remember to restart the Abiquo Tomcat server:
If you wish to configure the UI, for example, to change the UI text or translate it into different languages, see Configure Abiquo UI
Now open your web browser and type in the site address for the Abiquo server.
The default cloud admin login and password are "admin" and "xabiquo", respectively.
Remember to change your cloud admin password as soon as you log in for the first time.
For an overview of the Abiquo platform work through the tutorials built in to the product or try the Abiquo Quick Tutorial.
Check that your abiquo.properties file is correctly formatted, for example, there should be no spaces after the property values. Also check that property names are spelled correctly and appropriate values are supplied.
Review the Abiquo UI Configuration file, which by default can be found at.
Check that the file is correct JSON format and check that the property names are typed correctly and appropriate values have been entered.
Check that your API endpoint is set correctly and add any other required options.
See Configure Abiquo UI for a complete reference.
Check that you have set up an external NFS/CIFS server as described in NFS Server Setup.
Check that the /opt/abiquo/config/abiquo.properties file contains values for the following properties.
For example, if the Abiquo Server is located at 10.10.10.5 and the NFS repository is located at 10.10.10.4, the abiquo.properties file would look as follows.
After changing these settings, restart abiquo-tomcat service:
Log in to the hypervisors as root and check that the external NFS server is mounted, for example, using the df command.
The NFS shared directory must have an empty file named .abiquo_repository (the dot prefix is required). If you selected "Abiquo NFS Repository" as recommended by this guide, this file is automatically created for you. Otherwise, to create this file, mount the NFS share and enter the command:
For further details of NFS configuration and troubleshooting, please see NFS Server Setup and Distributed Install - 4. Post-install Configuration.