...
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 return a datastore mounted on at least one host in the cluster.
To allow datastores if they are mounted on at least one host:
On the Remote Services server, edit the abiquo.properties file and add the following property
...
.
...
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
...
and
...
| Code Block |
|---|
com.abiquo.esxi.discovery.datastore.ignorebyname=Backup_.* |
...
To activate the properties, restart the tomcat service of the Remote Services
Ignore datastores that are not writeable
To configure Abiquo to ignore datastores that are not writeable:
On the Remote Services server, in the
abiquo.propertiesfile, set the following property.Code Block com.abiquo.esxi.experimental.unsafe.ignorebaddatastore=trueTo 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 |
.
See Configure datastore discovery on 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
...
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 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.
...
For a list of properties filtered from the main table for of Abiquo 6.1.2, see VMware vCenter host and cluster properties table.
...