Admin Guide 1. Abiquo: HA for VMs
Abiquo High Availability (HA) is a vendor-neutral automatic VM restart capability that allows enterprises deploying multi-hypervisor datacenters to have a cost-effective high availability mechanism. Abiquo High Availability is based on Abiquo's virtual machine management features and is designed to complement hypervisor HA.
No vCenter Support
Abiquo High Availability is not compatible with VMware vCenter. Use VMware High Availability with vCenter.
Abiquo High Availability does not support XenServer.
Abiquo High Availability does not support vCenter. Use VMware High Availability with vCenter
Abiquo HA will not failover a VM from an ESX 4.x to ESX 5 host, or from an ESX 5 to ESX 4.x host. Abiquo will failover between two hosts of the same major version and in order to use Abiquo HA, all the hosts on the same rack should be of the same major version.
The basic functionality is that when a hypervisor failure is detected in a rack with HA enabled, the VMs created in Abiquo and running in that hypervisor from a shared datastore are restarted in another host in the same rack. High Availability will function with external storage and persistent virtual machines.
Although some of the HA configuration is performed within the Abiquo GUI, the system administrator should understand the overall configuration of the HA system as described in the outline below.
Enable High Availability in the Abiquo GUI when Creating Racks.
Physical machines on a standard rack enabled for HA must have IPMI configured. Physical machines on managed racks do not require IPMI because they will be controlled using the managed rack API (UCS racks only).
Configure IPMI in the Abiquo GUI when Creating Physical Machines. You will need to enter the IP address, Port (optional), User and Password.
In order for High Availability to function in a rack, there must be more than one hypervisor of the same type in the rack. Abiquo supports High Availability on standard hypervisors (see Compatibility Tables) except XenServer because of restricted datastore access. Abiquo does not support High Availability operations between different versions of VMware (e.g. v4.x and v5.0).
Abiquo 2.6 introduced support for High Availability of captured virtual machines.
Abiquo supports High Availability of virtual machines created and deployed in Abiquo. It also supports High Availability of captured Virtual Machines.
Abiquo High Availability will not function with imported Virtual Machines.
The Virtual Machines must be deployed but they can be in any of the deployment sub-states (on, off, paused or rebooted). The HA hypervisors must all have access to a shared datastore to allow them to restart the same virtual machines. The hypervisors may mount the same datastore with different names and using different technologies (e.g. NFS or CIFS). Abiquo uses a UUID folder to identify the datastore and this folder must not be deleted. If an HA hypervisor has more than one shared datastore, Abiquo will deploy using the standard datastore scheduler. Abiquo HA will restart VMs that are deployed on the shared datastore.
Enable the same shared datastore on each hypervisor on the HA Rack in the Abiquo client when Creating Physical Machines.
Abiquo uses ping to periodically check the hypervisors in the physical machines in the Rack. If a hypervisor does not respond to one check, it is marked. If it does not respond to the following check, the HA process starts.
Changes to HA Properties in Abiquo 2.4
The properties for configuring HA checks have changed in Abiquo 2.4.
The frequency with which the system should check the status of the hypervisor hosts is configurable in abiquo.properties file (See Abiquo Configuration properties).
When High Availability is enabled on a Rack, Abiquo periodically checks the hypervisors in the physical machines of the Rack (default 5 minutes).
If a hypervisor does not respond after the number of checks configured (default 2), Abiquo:
If there are no suitable hypervisors available (e.g. the whole Rack is affected by the system failure), the HA process will not run. If there are not enough resources on the available hypervisors, the virtual machines will not be restarted on a new hypervisor and will remain unchanged on the failed hypervisor.
You must manually restart a hypervisor that failed and was shut down by Abiquo using IPMI or the managed rack API.
Attention: Restarting an ESX or ESXi host disabled by HA
Before manually enabling an ESXi host in Abiquo, first check the hypervisor configuration using vSphere Client to ensure that the datastores are active. Perform a rescan if necessary. Then check for virtual machines with no name that are in the UNKNOWN (INVALID) state. Delete these machines in the hypervisor. Do not delete machines with proper names because Abiquo will manage these machines.
The hypervisor will have a state of DISABLED_BY_HA in the Abiquo GUI. The Cloud Administrator must then start up, perform checks and manually enable the physical machine in Abiquo. This machine will then be shown as MANAGED by Abiquo. Abiquo will reactivate any virtual machines previously deployed on it that could not be moved. The machine will also be available for new deployments.