The following components have requirements that must be fulfilled before you deploy an Abiquo environment:
Before you install a test or production environment, check the essential prerequisites steps for your environment. See Abiquo Prerequisites.
For supported versions additional information, see the Compatibility Tables.
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 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:
Once your infrastructure fulfills the requirements, choose whether you will deploy a Monolithic Environment or a Distributed Environment.
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:
|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|
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:
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:
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
This step is completely optional
The Abiquo monitoring appliance is completely optional. To deploy the Monitoring appliance, you need the following requirements:
|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:
Follow the steps in Deploy the Abiquo appliances for further details.
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:
Restart the abiquo-tomcat service in the Abiquo appliances for the monitoring changes to be applied:
Review the appliances /opt/abiquo/config/abiquo.properties file. You may need to tune it depending on your environment configuration.
Log In to the Abiquo UI
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.
The link below describes how to get an Abiquo license and add it to the platform:
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:
|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|