The following components are required for an Abiquo trial environment.
|Abiquo Monolithic Server||Runs as VM on ESXi or KVM.|
|NFS share||NFS on separate server is recommended (not hypervisor datastore).|
|Hypervisors||Abiquo recommends ESXi with vCenter, Hyper-V or KVM. Check your HVs requirements in the Cloud Node documentation|
Platform clocks must be synchronized. Abiquo will require NTP to be functional on all servers.
|ICMP||The monolithic appliance must be able to ping the infrastructure management IPs|
|Service network||A trunk capable network segment with VLAN tagging capabilities|
For versions, see Compatibility Tables
For server specifications, see Trial Requirements
The following components are optional for an Abiquo trial environment. We will describe how to configure a Monitoring appliance in this document later. Check the links for further details on each component.
|Abiquo Monitoring Server||Optional install; monitoring can be disabled in the trial|
|Public Cloud providers||AWS, Azure ARM, or other supported providers. Optional, See Public cloud provider features|
|Collectd||Use Abiquo collectd plugin installation|
|Persistent Storage||Any NFS storage (not available for Hyper-V), vFiler on NetApp, Nexenta|
|OpenStack Neutron||With KVM hypervisors and OpenStack clouds|
|VMware NSX||For firewalls and load balancers use the Advanced edition or higher|
For SDN as VMware NSX and OpenStack Neutron, check the configuration requirements in the links below:
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
IP of the management NIC
Management IP netmask
Netmask of the management NIC
|Default gateway||Default gateway in the management network|
|DNS server list||IPs of DNS servers separated by a blank space|
|Abiquo Datacenter ID||Internal ID of the trail DC.|
NFS Template repository
NFS share for the VM repository of the DC. Each private DC must have a different NFS
Abiquo API Server FQDN
This FQDN must be resolvable from the customer premises, iin order for SSL and the Appliance manager to work as expected. Abiquo will use self-signed certificates for the trial environment
The main platform networks to configure for Abiquo are:
Configure each of these networks as a separate network.
Abiquo manages the service network in different ways depending on the underlying network solution.
Standard VLAN service networks includes the following:
Every time a VM is deployed, Abiquo will generate his NICs MAC adresses, and it will bind and assign them to available IPs in the choosen network and appropriate VLANs.
Abiquo relies in 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 environments, refer to the appropiate documention.
You will need to configure your firewalls to enable the following ports and communications.
Abiquo Monolithic Server
|Client||Abiquo Monolithic Server||TCP 443||HTTPS|
|Websockify||Abiquo Monolithic Server||TCP||HTTPS|
Platform and Storage Servers
Nexenta storage agent
NetApp storage connector
LVM storage connector
Abiquo LVMSCSI server
Hypervisor, Abiquo V2V
Any Storage host
Volumes on the storage host iSCSI
Abiquo Monitoring Server with KairosDB
|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|
Download the Abiquo Monolithic OVA. Before you begin, you will need the values of the following OVA properties for step 12 of the deploy.
review the Abiquo properties file at /opt/abiquo/config/abiquo.properties . For trial deployments, you will probably configure some of the following properties:
After changing the properties, remember to restart the Abiquo Tomcat service always:
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.
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.