Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.


Abiquo 4.4

Skip to end of metadata
Go to start of metadata

This section describes how to install and configure hypervisors in Abiquo as cloud nodes.

Abiquo only supports hypervisors installed and configured as described in the corresponding documentation.

If you are integrating existing hypervisors, check this section to ensure they are compatible and properly configured.

Remember to consider the configuration limits of your hypervisors. Documentation is available for most hypervisors, for example, VMware Maximum Configurations.

Cloud Nodes

A cloud node is a server configured in Abiquo where the virtual resources assigned to each user are deployed.

Depending on the underlying virtualization technology, the Cloud node will require additional components to interoperate with Abiquo:

  • KVM requires the Abiquo AIM agent in each KVM host.
  • Docker requires the Abiquo Pilot agent in each Docker host.

VMWareHyper-V and XenServer do not require additional software to be installed.

Features Summary Table

The following table summarizes the hypervisor features available in the Abiquo platform.

Customers should always check the specific hypervisor features tables for further information.


 Virtualization technology
FeaturesvCenter/
vSphere ESXi
Hyper-V R2KVMOracle VMXenServerDocker
 General InformationVersion

5.x, 6.0

R2

KVM 0.12 

3.4

6.2.0

Docker 1.9

 Operating System or Profilen/a

Server 2012
Core 2012

CentOS 7x86 onlyn/aUbuntu
 VirtualizationVLAN Support for
virtualizing DHCP
(tick)-(tick)-(tick)-
Sub HypervisorNameESXi--Oracle VM/XenXen-
Manager HypervisorNamevCenterHyper-V Manager-OVM ManagerXenServer-
 Direct Integration(tick)--(tick)(tick)-
 Compatibility(tick)--Check(tick)-
StorageDisk controllers

IDE, SCSI

IDE, SCSIIDE, SCSI, VIRTIOIDE, SCSIIDE, SCSI-
 DatastoresAlllocal disk,
SMB
All NFS

LVM, EXT3, NFS,

iSCSI, HBA

-
External StorageiSCSI storage

(tick) with iSCSI adapter or NFS

(tick)(tick)(tick)(tick)
(error) NFS/CIFS
(tick)
 LUN LimitiSCSI 256 LUNs per cluster--1000 LUNs
per Oracle VM
--
 

Secondary disks
on Datastore

(tick)(tick)(tick)(tick)(tick)-
Storage ResizePrimary disk resize

(tick) thin-provisioned
on
SCSI controller only

(tick)

(tick)
(error) VMDK sparse
(error) VHD

(tick)(tick)-
 Secondary disk resize

(tick) thin-provisioned
on
SCSI controller only

(tick)(tick)(tick)(tick)-
 Volume resize(tick)(tick)(tick)(tick)(tick)
Apps LibraryPersistent virtual machines(tick)

(tick) VHD
(error) VHDX

(tick)(tick)(tick)-
 Instance(tick)(tick)(tick)(tick)(tick)(tick)
MoveVM Migration(tick)(tick) set more frequent
VSM polling
(tick)-(tick)-
 Storage Migration(tick)(warning) with vMotion
of VM
(tick)

(tick)
(error) QEMU
-(tick)-
HA (choose one)Hypervisor(tick) With vCenter(tick) Failover Clustering-(tick)(tick)-
 Abiquo

(tick) Without vCenter

  • Experimental support
    for Abiquo HA with vCenter
    but without DVS. 
    This configuration is
    not recommended
(tick)(tick)(error)(error)-
Monitoring
and Metrics
Hypervisor(tick) With vCenter(tick)  -(tick)(tick)

VM movement support

Abiquo supports the following hypervisor VM movement functionality. Note that target datastore must always be enabled in Abiquo for detection to work as expected.

Hypervisor

Move Technology

Notes

ESX/ESXi

vMotion

See How to make VMware vMotion work with Abiquo. Abiquo does not support vMotion between machines with different network service types

Hyper-VVM MoveAbiquo uses Msvm_MigrationJob to detect moved VMs. These jobs only exist for 5 minutes, so ensure the abiquo.vsm.pollingfrequency.hyperv_301 is configured to a low value. The default value of 5000 milliseconds is appropriate.

KVM

Live Migration

Not supported on virtualized hypervisors (QEMU). See How to configure KVM for live migration under Abiquo

XenServerXenMotion 

 

Hypervisor HA Support

Abiquo supports the following High Availability functionality. If both Abiquo and hypervisor HA are supported, you should choose only ONE of these. Note that the shared datastore must always be enabled in Abiquo.

Hypervisor

Abiquo HA

Hypervisor HA

ESX/ESXi

(tick) without vCenter

  • Each rack should only contain hypervisors of the same major version
  • Experimental support has been introduced for Abiquo HA with vCenter but without DVS. This configuration is not recommended
(tick) with vCenter
Hyper-V(tick)(tick) Failover Clusters

KVM

(tick)

-
Oracle(error)(tick)
XenServer(error)(tick)

See Configuring High Availability of VMs

Virtual machine templates

See Template Compatibility TableAdd VM Templates to the Apps Library and Importing Templates into the Appliance Library

Remote Access Support

Abiquo enables remote access to VMs through the eye icon. Abiquo includes the default noVNC program for VNC connections. The noVNC client interface can be branded. The Abiquo noVNC installation requires the websockify proxy. See Configure Remote Access to Virtual Machines