Requirements
The following components have requirements that must be fulfilled before you deploy an Abiquo environment:
- Clock synchronization: Platform clocks must be synchronized. Abiquo will use NTP to keep platform clocks synchronized. Check your vendor documentation for other components.
- VM repository folder: A unique NFS or CIFS dedicated shared folder must be present in each Abiquo DC before deployment. Check NFS Server Setup for more details.
- Hypervisors: Check your HVs requirements in the corresponding Cloud Node documentation.
- Network: A trunk capable network segment with VLAN tagging capabilities is required.
For supported versions additional information, see the Compatibility Tables. Once your infrastructure fulfill the requirements, you have to chose whether you will deploy a Monolithic Environment or a Distributed Environment.
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:
- Monolithic environments install all the Abiquo components inside the same appliance, and they are good for probe of concept and testing purposes
Monolithic environments only require a monolithic appliance, and optionally, a monitoring appliance.
Monolithic environment worksheet (See this link for an example) - Distributed environments separate Abiquo components depending on they characteristics for improved performance and reliability, and they are good for production environments
Distributed environments require at least one Server, one Remote Services and one V2V appliance.
Distributed environment worksheet (See this link for an example)
Network
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:
For SDN as VMware NSX and OpenStack Neutron, check the configuration requirements in the links below:
Finally, 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.
VM repository folder
In Abiquo, all private DCs must have their own VM repository folder, which holds the VM templates for all enterprises in each DC.
The Monolithic, Remote Services and V2V appliances and your HVs must be able to mount and manage this folder remotely 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 it as VM repository and mount it automatically on the HVs when needed.
For further details, please check the VM repository documentation at the link below:
Appliances
You will need to install the Abiquo appliances corresponding to the environment, and optionally, the monitoring appliance.
These appliances require some configuration parameters before deployment. Some of them are common, while others are specific to the appliance functions inside the platform.
These details are required during the bootstrap process, and you must have them in place before the deployment:
These are the common requirements for both Abiquo platform appliances:
Parameter | Notes |
|---|---|
| Friendly hostname | This 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 gateway | Default gateway in the management network |
| DNS server list | IPs of DNS servers separated by a blank space |
| NTP server list | Abiquo appliances use NTP to fulfill the platform clock synchronization requirements |
Monolithic deployment
Monolithic environments install all the Abiquo functionality but monitoring in the same appliance, and they are ideal for probe of concept and trial purposes.
To deploy a monolithic environment, get the monolithic appliance OVA and install it on your environment.
Monolithic appliance
Installation requirements
- 2 CPUs
- 8 Gb RAM
- 64 Gb HD
Installation parameters
Parameter | Notes |
|---|---|
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 ID | Internal 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 repository | NFS share for the VM repository of the DC. Each private DC must have a different NFS share |
Firewall requirements
From | To | Notes |
|---|---|---|
Anywhere | TCP/80 (HTTP) | It will be redirected to port 443 by default |
| Anywhere | TCP/443 (HTTPS) | Proxy port for API/AM/UI services |
| Anywhere | TCP/41337 (HTTPS) | Proxy port for VNC services |
| Monitoring appliance | TCP/5672 | RabbitMQ default port for Abiquo components to exchange messages |
Distributed deployment
Distributed environments split the Abiquo platform functionality among different servers to improve reliability and performance. They are ideal for production environments.
To deploy a distributed environment, you will need to deploy at least a server, remote services and v2v appliances.
Server appliance
The server appliance contains the Abiquo UI, API and Events servers, and is
Installation requirements
- 2 CPUs
- 8 Gb RAM
- 64Gb HD
Installation parameters
Parameter | Notes |
|---|---|
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 |
Firewall requirements
From | To | Notes |
|---|---|---|
Anywhere | TCP/80 (HTTP) | It will be redirected to port 443 by default |
| Anywhere | TCP/443 (HTTPS) | Proxy port for API/AM/UI services |
| Anywhere | TCP/41337 (HTTPS) | Proxy port for VNC services |
Remote services appliance V2V appliance | TCP/8009 TCP/8010 | |
Monitoring appliance Remote services appliance V2V appliance | TCP/5672 | RabbitMQ default port for Abiquo components to exchange messages |
Remote Services appliance
The Remote Services appliance contains the Abiquo private datacenter and Public Cloud provider management components. A Remote services appliance is require for each private datacenter.
Installation requirements
- 2 CPUs
- 8 Gb RAM
- 64 GB HD
Installation parameters
Parameter | Notes |
|---|---|
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 ID | Internal 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 repository | NFS share for the VM repository of the DC. Each private DC must have a different NFS share |
| Abiquo RabbitMQ server address | Abiquo server appliance IP and and port. |
Firewall requirements
From | To | Notes |
|---|---|---|
Server appliance | TCP/8009 TCP/8010 | |
| Server appliance | TCP/41338 |
V2V appliance
The server appliance contains the Abiquo virtualization format conversion components, and it is isolated for performance reasons.
As this appliance deals with conversions, fast HD storage is recommended for this appliance.
Installation requirements
- 2 CPUs
- 4 Gb RAM
- 256 GB HD (Depending on template conversion requirements. Get in touch with Abiquo support for further information)
Installation parameters
Parameter | Notes |
|---|---|
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 ID | Internal 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 repository | NFS share for the VM repository of the DC. Each private DC must have a different NFS share |
| Abiquo RabbitMQ server address | Abiquo server appliance IP and and port. |
Firewall requirements
From | To | Notes |
|---|---|---|
Server appliance | TCP/8009 TCP/8010 |
Deploy the appliances
If you are not deploying the appliances in a VMWare environment, you will need to convert and deploy the OVAs first, and configure them manually later as described in the link below:
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:
- Download the appliance OVA from the corresponding link to your desktop
- Open the vCenter vSphere web client
- Go to Host and clusters section in the client side panel
- Go to Actions and click on Deploy OVF template
- Select Local file and choose the OVA you downloaded in step 1. Click Next
- The vSphere client will display the OVA details. Click Next
- Accept the EULA and click Next
- Edit the deployed VM name and choose where you want to deploy it. After this, click Next
- Select which cluster or host will be used for deploy and click Next
- Choose the datastore for the deployed VM and click Next
- Select the network destination for the VM management NIC and click Next
Enter the template details depending on the OVA you are deploying. For more details, see the parameters table above. When configured, click Next
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
Monitoring installation
This step is completely optional
The Abiquo monitoring appliance is completely optional. To deploy the Monitoring appliance, you need the following requirements:
Parameter | Notes |
|---|---|
| Server management IP address | Abiquo 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:
Source | Destination port | Notes |
|---|---|---|
Monolithic appliance | TCP/36638 (HTTP) | Monitoring services |
Follow the steps in Deploy the Abiquo appliances for further details.
Once installed:
Edit the monitoring appliance properties to set the data retention policy. See the following link for further details: Abiquo monitoring appliance configuration
Edit the monolithic/server/remote services appliance /opt/abiquo/config/abiquo.properties file, add the properties below. 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 abiquo.watchtower.host=MONITORING_IP # Port where watchtower is listening abiquo.watchtower.port=36638
Restart the abiquo-tomcat service in the Abiquo appliances for the monitoring changes to be applied:
service abiquo-tomcat restart
Post-install steps
- Log into the Abiquo UI in the https://FQDN URL.
- Remember to change the Abiquo default passwords as soon as possible (Base OS and UI passwords)
- 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.
Review the appliances /opt/abiquo/config/abiquo.properties file. You may need to tune it depending on your environment configuration.
- Review the appliances file systems configurations, as their usage is completely dependant on the use the platform will have and you will need to increase them accordingly
- Monitor the platform appliances accordingly to prevent outages: Monitor platform servers
Log In to the Abiquo UI
Now open your web browser and type in the site address for the Abiquo server.
https://FQDN
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:
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:
| Component | Notes |
|---|---|
| UI configuration | See Configure Abiquo UI |
| UI branding | Check Abiquo Branding Guide |
| Abiquo platform configuration | Change the platform settings accordingly to your needs: Configuring Abiquo |
| Public Cloud providers | Configure AWS, Azure ARM, or other supported cloud providers: Public cloud provider features |
| Collectd | Use Abiquo collectd plugin integration for customized metrics: Use collectd plugin for custom metrics |
| Persistent Storage | Configure NFS storage as vFiler on NetApp or Nexenta: Storage Servers |
| Jaspersoft Reports | For Abiquo reports. Check Install Abiquo Reports |
| Chef Server integration | Check Abiquo Chef Integration Guide |