Admin Guide 1. Abiquo
Compatibility Tables
Only tested and supported versions are listed here and it is recommended that you use these versions.
Servers
Remember that the Abiquo platform is integrated into Abiquo Linux, which is derived from the CentOS 5 Linux distribution. Therefore, you should ensure that your server hardware is compatible with CentOS and that suitable drivers are available. CentOS/RedHat expertise is required to maintain the Linux servers.
Virtualizing Abiquo
If you are installing Abiquo on a virtual machine, this will also need to be compatible with the CentOS operating system. For example, if you wish to install Abiquo on a virtual machine on ESX/ESXi, you should choose the e1000 Ethernet adapter as this is the most compatible adapter for this system and the drivers are included in the Abiquo installer.
Remember that Abiquo platform networks require DHCP services with VLAN support for listening to multiple VLANs. The default DHCP solution is a DHCP Server (on Remote Services in distributed install; on Abiquo Server in monolithic install). Or you can provide DHCP services with a DHCP relay server or separate DHCP server. If you wish to install your chosen DHCP solution on a virtual machine, the hypervisor must support listening to multiple VLANs. At this time, the recommended hypervisors with VLAN support are: ESXi with VLAN tagging and KVM with Open vSwitch.
See Configuring a DHCP Server with VLAN Support. Thus, in practice, if you will be virtualizing Abiquo and using Abiquo Platform networks, then you will usually need to run ONE of the servers in this table on a VM on a hypervisor with VLAN support.
Install on Hypervisor with VLAN Support | Explanation |
|---|---|
DHCP Relay Server | This is the recommended configuration. The relay server manages VLANs and relays their DHCP requests to the Abiquo DHCP server. The other Abiquo platform components can now be installed on any suitable VM/hypervisor |
DHCP Server | Replaces the Abiquo default DHCP server. The other Abiquo platform components can now be installed on any suitable VM/hypervisor |
Abiquo Remote Services | In a distributed installation without a separate DHCP relay server or DHCP server, the main Abiquo Server must be installed on a hypervisor with VLAN support |
Abiquo Monolithic Server | In a distributed installation without a separate DHCP relay server or DHCP server, the Remote Services must be installed on a hypervisor with VLAN support |
Hypervisors
| Supported Hypervisors Abiquo only supports hypervisors installed and configured by following the Abiquo documentation. |
Vendor | Hypervisor | Version____________________________ |
|---|---|---|
VMware | vSphere 4: Standard, Advanced, Enterprise, Enterprise Plus. Distributed Virtual Switch requires Enterprise Plus. VSphere 5. | ESX 4.0, 4.1; ESXi 4.0, 4.1; |
Xen.org | Xen | Abiquo Linux package only |
Citrix | XenServer. Abiquo High Availability is not supported on XenServer. | 5.6 SP2 (with Linux Support). |
KVM | KVM | Abiquo Linux package only |
Oracle | VirtualBox | Abiquo Linux package only |
Microsoft | Hyper-V | Hyper-V role on Windows 2008 R2 Standard, Enterprise or Datacenter Edition. Hyper-V on Server Core is not supported. |
See also Template Compatibility Table and VM Template Guide
Remote Access Support
Abiquo allows remote access to virtual machines through the eye icon.
Hypervisor | Remote Access Support |
|---|---|
ESX/ESXi |
|
XenServer |
|
KVM |
|
XEN |
|
VirtualBox |
|
Hyper-V |
|
Captured Virtual Machines
Abiquo can capture virtual machines from physical machines managed by Abiquo
- Prerequisites
- The hypervisor datastore must be enabled in Abiquo. See Manage Physical Machines#Datastore Management
- The format of the hard disk must be compatible. See Template Compatibility Table
- Process
- Adds the VM to the Abiquo database as an imported machine
- Imports:
- CPU and RAM
- One hard disk
- Existing remote access configuration
- Capabilities
- Power on
- Power off
- Pause
- Create an instance (on all hypervisors except KVM and Xen)
- Undeploy - destroys the virtual machine on the hypervisor.
Storage
Storage type | Vendor | Protocol |
|---|---|---|
Hypervisor Datastore | Any | iSCSI, NFS, CIFS, FC, FCoE, or direct attached |
Generic iSCSI Storage | Any | iSCSI |
Managed Tiered Storage | NetApp | ONTAP 7 |
Managed Tiered Storage | Nexenta | 3.0.4 enterprise |
Managed Tiered Storage | LVM | Red Hat 5.x |
Persistent Virtual Machines can use Managed Tiered Storage or Generic iSCSI Storage.
Managed Racks
Vendor | Rack and Components |
|---|---|
Cisco | Unified Computing System. |
Networking
Abiquo supports IPv4 for DHCP and access to the Abiquo console/UI.
LDAP Implementations
- Windows 2003
- Windows 2008
- Windows 2008R2
- ApacheDS
- OpenLDAP 2.4
Chef Integration
Abiquo Chef Integration requires an Opscode Chef server. Opscode Chef requires time synchronization between your servers and hypervisors. Abiquo Chef Integration supports Linux virtual machines only. Abiquo Chef Integration requires a DHCP server configured in the Abiquo platform to pass parameters to virtual machines. If you wish to use the Chef recipes in the Opscode community repository, then Abiquo recommends that you use Ubuntu virtual machines.
Web Client
Browsers
Vendor | Browser | From Version | Recommended Operating System |
|---|---|---|---|
Microsoft | Internet Explorer | 8, no VM upload from local disk | Windows |
Mozilla | Firefox | 3 | Windows, Linux, Macintosh |
Chrome | 10 | Windows, Linux, Macintosh | |
Apple | Safari | 5 | Macintosh |
Required Plugins
Vendor | Plugin | From Version |
|---|---|---|
Adobe | Flash Player | 9 |
Oracle | Java (previously Sun Java) | Java SE 6 Update 26 (or higher) |
