ESXi 5.5 with known issues:
To connect to vCenter, Abiquo will require valid administration credentials and the port if you are not using the default of TCP 443.
Configure the port in the /opt/abiquo/config/abiquo.properties file on the Remote Services appliances if you are not using the default one:
Configure the firewall to allow access from the Remote Services appliance to the appropriate port.
For the VNC connection to VMs through the "eye icon", add a custom firewall rule to define the ports that will be available to users.
You will also need to define the same range of VNC ports for Abiquo, so that it will allocate available ports. Define these ports with Abiquo Configuration Properties#vncport properties.
You cannot add a VNC firewall rule through the VMware console. Follow the steps below to add the firewall rule with the CLI (using SSH).
The following example shows how to add a custom firewall rule under ESXi 5 for ports 5900 to 5964.
(Credit vInfrastructure Blog)
1. Log in to the CLI for the ESXi as root user
2. Create the XML file
3. Add these lines (copy/paste) to the VI and save the file.
4. Refresh the rules and check it has been added;
5. Optional step - Add a specific IP address to the rule for added security;
Set the status of the allowedAll flag to false
Add the list of allowed IP addresses
On the ESXi host, the vNICs must be attached to a vSwitch, which may be a DVS. Abiquo will automatically create a port group for the host.
Reconfigure an Existing ESX or ESXi Installation
If your host has already been configured with another vSwitch, you may need to delete the port group before adding the host in Abiquo.
It is possible to configure NFS Datastores on ESXi hypervisors. However, to allow access to persistent virtual machines and external storage volumes, you should configure the abiquo.esxi.datastoreRdm property to use iSCSI.
Set this property to the name of a VMFS datastore configured for RDM on the ESXi hypervisor, for example on an iSCSI LUN. If you create a persistent VM or add an additional iSCSI disk, ESXi will use the configured RDM datastore to map into the iSCSI LUN. If you create an auxiliary disk, ESXi will store it on the hypervisor's NFS datastore.
Configure the property with the name of the datastore in ESXi. For example, if the hypervisor has an NFS datastore named "datastore1" and an RDM datastore named "datastore2", configure it as:
All the ESXi hypervisors monitored by the same Abiquo Remote Services will use the same RDM datastore, so all of them should have the same datastore configured with the same name.
Note that ESXi datastores can only be configured with the datastore name – you cannot enter a directory as part of the datastore configuration.
If you are deploying only virtual machines that only have persistent disks (volumes on external storage devices, not the hypervisor datastore) then you must set the datastoreVmFile property.
Abiquo uses thin provisioning on ESXi. It is enabled for all VMs deployed using Abiquo, which will all be deployed with thin disks. If the disks are attached to an IDE controller, you can resize these disks outside Abiquo, using VMWare tools such as vCenter. Within Abiquo you can only resize disks attached to a SCSI controller, due to an ESXi limitation.
Abiquo avoids performing a full HBA rescan of storage on ESX or ESXi for performance reasons. Instead it checks for a raw device mapping for a given IQN and LUN. However, if a volume has been removed or replaced in the storage device, Abiquo may try to attach a volume that does not exist or is completely different to the one previously configured.
This situation may occur with: managed storage volumes, generic iSCSI volumes and persistent virtual machines. It can be resolved by manually performing a full HBA rescan of all ESX or ESXi hosts that had raw device mappings for the devices involved.
When the platform registers hypervisor datastores, it creates a datastore UUID folder. To ignore datastores that the platform does not have write access to, set the following property in the abiquo.properties file on the Remote Services server.
If you enable this property, the platform may remove datastores during an infrastructure check
You should check that the appropriate iSCSI adapters were enabled as part of the ESXi installation process. See How to enable iSCSI Initiator on ESXi
Abiquo recommends that you install the drivers for the appropriate SCSI controllers when preparing virtual machine templates that will be uploaded to the Abiquo platform.
Users can set the SCSI disk controller type and controller for ESXi. The supported disk controllers are listed in the following table.
|ResourceSubType value||diskController saved in template and created on VMware|
|other (default value)||VirtualLsiLogicController|
If the user does not set a controller, the defaults are:
The default configuration set by the administrator in the abiquo.properties file
LSI Logic Parallel SCSI controller
If the user does not set the controller before deployment, Abiquo attaches SCSI disks to the default controller.
Disk controller user information
Users can now set disk controller and disk controller type
You can set multiple controllers but only ONE of each type (e.g. you cannot set two LSI Logic controllers)
To resize disks of virtual machines running on ESXi using Abiquo, the disks must be:
You cannot resize the primary disk of a virtual machine that is not allocated (not deployed)
Abiquo supports vMotion. See How to make VMware vMotion work with Abiquo for configuration information.
Log in to the Abiquo Remote Services machine (or if you performed a Monolithic installation log in to the Abiquo Server) and set the appropriate properties for your system to appropriate values in the /opt/abiquo/config/abiquo.properties file:
Log in to the Abiquo Server and add the properties that apply to your system to the abiquo.properties file:
This page describes the VMware ESXi features supported by Abiquo. You can manage VMware technology at the following levels: vCenter, ESXi, vCloud Director: ESXI feature support
Detect all HostProxySwitch as DVS without requiring a naming convention
Add vCenter as a master hypervisor with the appropriate credentials, and then add individual hypervisors
Abiquo will use the vCenter credentials. User must have access to vCenter. Configure optional "dvs" properties as required.
|Fault Tolerance||Abiquo does not support fault tolerance because it requires two VMs with the same name to be present in a cluster at the same time|
|Clusters||The platform automatically detects clusters and displays them on the racks with the physical machines. Compute load level rules can be set at the cluster level|
|VM Live Migration|
Abiquo supports vMotion of virtual machines, including those between hosts with different versions of ESXi
|Storage Live Migration|
VMDK fixed ( default format)
The DVD feature was replaced by the ISO feature but CD-ROM configurations may be supported on imported VMs
VNC - can be enabled/disabled through Abiquo including with hot-configure
|CPU hot-add |
With supported guest operating system. The user can mark supported templates and perform hot-add
|With supported guest operating system. The user can mark supported templates and perform hot-reconfigure|
|SDN using NSX||Abiquo supports SDN using NSX in gateway and ECMP configurations. See Configure the NSX integration|
For all virtual machines deployed on ESX/ESXi hypervisors:
|Persistent Virtual |
By default persistent virtual machine disks are mounted on IDE controllers
System disk resize
Disks must be:
|Storage Live Migration|