Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 6.2.0

...

Info

This document refers to VMware hypervisors including vCenter clusters and vCenter hosts in private cloud datacenters.

...

Abiquo can also work with NSX-T to create network configurations such as firewalls, load balancers, and NAT.

Warning
  • Abiquo does not support ESXi hosts without vCenter

  • Abiquo does not support VSAN datastores

...

Supported versions

Abiquo has been tested with the following latest versions.

...

Feature

Description

Datastores

VMFS, NFS, vVol.
Abiquo does not support VSAN datastores.
You can use any storage protocol, such as iSCSI, NFS, FC, FCoE, or direct attached.

VM disk controller types

  • IDE (default for compatibility reasons),

  • SCSI

  • SATA

VM SCSI controllers

  • VirtualLsiLogicController (default) 

  • ParaVirtualSCSIController

  • VirtualBusLogicController

  • VirtualLsiLogicSASController

VM system disks

By default, for VMs deployed on ESX/ESXi hypervisors:

  • If disks are deployed from VMDK Sparse templates, they will be in Sparse format

  • If disks are deployed from VMDK templates or conversions from formats other than VMDK Sparse, they will be in flat/fixed formats with thin provisioning enabled

Disk resize

(tick) (warning) System disk resize
(tick) (warning) Hard disk resize

See Configure VM disks for VMware

Storage live migration

For vCenter hosts, Abiquo detects storage vMotion on all datastores

...

If your host has already been configured with another vSwitch, you may need to delete the port group before adding a host to Abiquo.

...

Host datastores

Abiquo will deploy VMs to datastores that you register in the platform.

For vCenter clusters, you should use shared datastores, so when VMs move, they will always be accessible to all hosts.

For vCenter hosts, when you use a shared datastore, the platform Abiquo creates a different datastore on each physical machine that is using the datastore. This means that a shared datastore can be enabled on one host and disabled on another, either as a result of user configuration or an issue (e.g. an NFS communication error on one host).

...

Abiquo should discover and list all of the datastores that you will use for deploying VMs. When you add your vCenters, you will select datastores from this list to use in Abiquo.

Abiquo expects to be able to identify each datastore with a UUID, so it will initially try to create a UUID folder on each datastore.

By default, Abiquo retrieves a datastore if it is accessible and not in maintenance mode on all the hosts in the cluster that mount it.

So by default, if there is a host that has all the datastores mounted, but Abiquo cannot access them (e.g. because the host is down), Abiquo will not return any datastores. You can configure Abiquo to avoid this situation.

Allow datastores mounted on at least one host

You can configure Abiquo to retrieve a datastore if it is mounted, not in maintenance mode, and accessible on at least one host in the cluster.

To allow datastores if they are return a datastore mounted on at least one host:

...

.

...

Code Block
com.abiquo.esxi.clusterdatastore.atleastone=true

...

To activate the properties, restart the tomcat service of the Remote Services

Ignore datastores by name

You can also configure Abiquo to ignore datastores by name when you add a host or on an existing host, so that Abiquo will not check or use the datastores. You can still use these datastores outside of the platform. To ignore datastores by name:

...

name

...

.

...

...

To activate the properties, restart the tomcat service of the Remote Services

Ignore datastores that are not writeable

To configure Abiquo to Abiquo will automatically ignore datastores that are not writeable:

  1. On the Remote Services server, in the abiquo.properties file, set the following property.

    Code Block
    com.abiquo.esxi.experimental.unsafe.ignorebaddatastore=true
  2. To activate the properties, restart the tomcat service of the Remote Services

Note

If you activate this property, the platform may remove inaccessible datastores during an infrastructure check

accessible.

See Configure datastore discovery for VMware

...

Datastore checks

As part of the infrastructure check, Abiquo will check datastores to ensure that it can deploy VMs.

...

If you activated a datastore, but it fails the datastore check, then Abiquo will automatically deactivate it. If it passes a check in the future check, then Abiquo will automatically activate it again. If a deactivated datastore fails the datastore check, then Abiquo will ignore it!

...

Manage datastores in Abiquo

...

To delete a datastore, make sure it is empty and not attached to the host.

The datastore refresh will handle inaccessible datastores as follows.

  • Remove inaccessible datastores if they are not used by any managed VMs

  • Disable inaccessible datastores if they are used by any managed VMs.

...

Configuration of VM disks

Abiquo supports thin provisioning, and IDE, SCSI, and SATA disk controllers, and you can configure defaults for the platform.

See https://abiquo.atlassian.net/wiki/spaces/doc/pages/560988173/Configure+VM+disks+on+VMware and for more options, such as ISO disks, see Configure SATA for VMware hypervisors.

...

VM templates

You can upload OVA and disk files to the Catalogue so users can create VMs from VM templates by self-service.

See Template compatibility tableAdd VM templates to the catalogue  and Importing templates into the catalogue

...

VM snapshots

Abiquo enables users to manage VM snapshots in the user interface. For a full feature description and configuration details, see Abiquo and VM snapshots for VMware.

...

The platform supports remote access through to vCenter VMs with WebMKS using a WebMKS proxy.

...

For a list of properties filtered from the main table for of Abiquo 6.1.2, see VMware vCenter host and cluster properties table.

...