The following configurations are supported for an Abiquo trial environment.
|Abiquo Monolithic Server||Runs as VM on ESXi or KVM||VLAN tagging configuration is required|
|NFS Server||NFS on separate server is recommended (not hypervisor datastore)||Required to store VM templates|
|Persistent Storage||Any NFS storage (not available for Hyper-V), vFiler on NetApp, Nexenta||Optional|
|Hypervisors||ESXi (with vCenter), KVM||Configure ESXi or install Abiquo KVM|
|Public Cloud providers||AWS, Azure ARM, or other supported providers||Optional, See Public cloud provider features|
|Abiquo Monitoring Server||Optional install; monitoring can be disabled in the trial|
|Collectd||Optional Abiquo collectd plugin installation|
|OpenStack Neutron||With KVM hypervisors and OpenStack clouds|
|VMware NSX||For firewalls and load balancers use the Advanced edition or higher|
For versions, see Compatibility Tables
For server specifications, see Trial Requirements
You will need to enter the following parameters about your environment during the monolithic install. These parameters configure your system to interact with the platform prerequisites that you must configure prior to the install.
Management IP address
Interface of the VM in the management network
Management IP netmask
Netmask of the management network
|Default gateway||Default gateway for the VM in the management network|
|DNS server list||IPs of DNS servers for the VM, separated by a blank space|
|Abiquo Datacenter ID||For intercommunication of datacenter components. The datacenter must be the same on all Remote Services and V2V servers in the same datacenter, and unique to this datacenter.|
NFS Template repository
IP address and directory of NFS/CIFS Repository server to store the VM template repository.
Each private cloud datacenter (and therefore each Remote Services and V2V server) must have its own NFS template repository, except private OpenStack cloud and Docker
By default the directory is /opt/vm_repository.
Abiquo API Server FQDN
The fully qualified domain name of the Abiquo Server, in order for the Appliance manager to work with HTTPS for VM template operations.
The main platform networks to configure for Abiquo are:
Configure each of these networks as a separate network.
Within an Abiquo datacenter, every hypervisor should be connected to the top-of-rack switch to connect:
The Service Network is a VLAN network that includes the following virtual network types:
Abiquo can manage the service network with standard networking or software defined networking (SDN).
For standard networking, Abiquo management of the service network includes the following:
For SDN, Abiquo has integrations with popular systems, such as VMware NSX and OpenStack Neutron.
You will need to configure your firewalls to enable the following ports and communications.
Abiquo Monolithic Server
|Client||Abiquo Monolithic Server||TCP 443||HTTPS|
Nexenta storage agent
NetApp storage connector
LVM storage connector
Abiquo LVMSCSI server
Hypervisor, Abiquo V2V
Any Storage host
Volumes on the storage host iSCSI
|Monolithic Server||Monitoring Server||TCP 8080||KairosDB|
Monolithic Server, Hypervisor
Monolithic Server, Hypervisor
|Monolithic Server||ESXi||TCP 443|
|Monolithic Server||Hyper-V||TCP 135|
|Monolithic Server||KVM||TCP 8889|
|Monolithic Server||XenServer||TCP 443|
|Monolithic Server||Oracle VM||TCP 7002|
|Monolithic Server||Public cloud||TCP 443|
ICMP must be allowed between all components of the Abiquo platform, including hypervisors.
Abiquo can manage an external storage platform to offer self-service virtual storage to users. External storage can be used to allocate external storage volumes to Virtual Appliances, or to convert VM Templates to Persistent Virtual Templates. Persistent templates save a VM disk to the storage platform, allowing you to take advantage of storage features such as high availability. Use of external storage is optional, although some features may not be available if external storage is not available.
Abiquo has an NFS integration that can be used to create self-service iSCSI volumes on NFS storage, which is suitable for use in Proof of Concept tests. To use NFS storage, simply add the storage share to Abiquo as a storage device. Or you can install the Abiquo LVM storage server. See Trial Storage Server.
Abiquo recommends VMware hypervisors or Abiquo RedHat KVM hypervisors for the proof of concept test. Other hypervisors are supported as described in the Cloud Node documentation.
The Abiquo VM monitoring and metrics feature enables you to obtain a rapid and convenient overview of VM performance through the Abiquo cloud console. Abiquo supports monitoring and metrics of VMs on the AWS, Azure, ESXi, KVM and XenServer, as well as Docker. ESXi hypervisors must be connected to a vCenter server
Supported monitoring and metrics:
Test environment: install Monitoring OVA that includes:
The Abiquo Monitoring Appliance is a CentOS system with Abiquo watchtower, KairosDB and Cassandra on the same VM. For instructions on how to install it, see Quickstart Install Abiquo OVAs
After you complete the install, configure the following:
Edit the kairosdb.properties file and set KairosDB properties, such as data retention time. The following link describes the KairosDB property for the time to live for a datapoint and Cassandra will automatically delete it after this time has elapsed: https://github.com/kairosdb/kairosdb/blob/v0.9.4/src/main/resources/kairosdb.properties#L91-L95
On remote services (Monolithic and Remote Services, but not V2V services), edit the abiquo.properties file to add the following properties, then restart the Tomcat service.
Abiquo supports collectd for custom metrics collection on Linux VMs. The Abiquo-collectd-plugin automatically pushes the values gathered by collectd to the Abiquo API. There is a new Abiquo API endpoint that the plugin uses to perform the push. As with other custom metrics, the Abiquo API then pushes the collectd metrics to the Abiquo Monitoring Server. You can use this method for hypervisors and providers where Abiquo does not support built-in metrics.
To install and configure collectd:
Download the Abiquo Monolithic OVA. Before you begin, you will need the values of the following OVA properties for step 12 of the deploy.
Configure Abiquo properties. The default Abiquo properties file is as follows:
For a monolithic deployment, you will probably configure some of the following properties:
After configuring the properties, remember to restart the Abiquo Tomcat server
For more information about the configuration described in this section, see Configuring Abiquo
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.
If you change the name and/or password of the "default_outbound_api_user" in Abiquo, you will need to change them in the Abiquo properties file. The Abiquo "M" module completes event details in Abiquo and streams events in the outbound API. For more details see Abiquo Configuration Properties#Configure Abiquo Events Properties
For an overview of the Abiquo platform work through the tutorials built in to the product or try the Abiquo Quick Tutorial.