Versions Compared

Old Version 92

changes.mady.by.user MS

Saved on

compared with

New Version Current

changes.mady.by.user MS

Saved on

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 manage VMware hypervisors in your multi-cloud platform with VMware hosts at different levels as:

  • vCenter server hosts

  • vCenter clusters (as hosts)

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

vCenter server

(tick) Add vCenter as a master hypervisor manager, then add hypervisors or clusters as hosts

dvSwitch

(tick) Abiquo will use the vCenter credentials. Detect all HostProxySwitch as DVS

High availability

(tick) Abiquo supports vSphere HA

Fault tolerance

(error) 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.

Replication

(tick) Abiquo supports replication with Zerto. Replicated VMs must be a in a separate cluster.

Clusters

(tick) For vCenter hosts, the platform automatically detects clusters and displays them. You can also set compute load level rules at the Cluster level
(tick) For vCenter clusters as hosts, set the compute load level rules at the Server level

VM live migration

(tick) For vCenter clusters as hosts, live migrations are transparent to Abiquo
(tick) For vCenter hosts, Abiquo supports vMotion of VMs, including those between hosts with different versions of ESXi. Abiquo supports vMotion between machines with different network service types if they are connected to a dvSwitch

Templates

(tick) VMDK fixed ((star) default format)
(tick) VMDK sparse
(tick) VMDK stream optimized (deployed directly)

DVD

The ISO feature supports DVDs, and you can import CD-ROM configurations on VMs with IDE and SATA controllers

Remote access

(tick) WebMKS - configure the WebMKS proxy. WebMKS will always be available.

Network drivers

E1000, PCNet32, VMXNET3

Boot

(tick) BIOS
(tick) UEFI with supported guest operating system and firmware, for virtual hardware versions 13 or later. The administrator must select UEFI on VM templates

CPU hot-add 
RAM hot-add 

(tick) With supported guest operating system. The user can mark supported templates and perform hot-add

Hot-reconfigure of NICs, disks 

(tick) With supported guest operating system. The user can mark supported templates and perform hot-reconfigure

SDN - NSX

Abiquo supports SDN using NSX-V with gateway, ECMP, and NAT configurations.

SDN - NSX-T

Abiquo supports SDN using NSX-T. See Configure the Abiquo NSX-T integration

Snapshots

Abiquo lets users obtain a snapshot of their VM through the UI.
See Abiquo and VM snapshots for VMware

GuestOS

Support in VM template for latest GuestOsIdentifier from vSphere. See Modify a VM template and Set the guest operating system for VMware

DRS rules

  • Rules for anti-affinity layers to deploy VMs separately

  • Abiquo can deploy VMs to separate clusters by operating system. See DRS rules for license affinity

Metrics

Customize the built-in metrics to obtain from ESXi

Hardware version

Property to specify downgrade of hardwareVersion for new VMs

...

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

...

You can add VMware vCenter clusters directly as hosts, so Abiquo will use vCenter clusters instead of individual vCenter servers. When you create a physical machine/hypervisor host in Abiquo for a cluster, select VMware vCenter cluster.

...

For vCenter clusters, you must use dvSwitches (VMware distributed virtual switches or VDSs). Abiquo will retrieve the dVSwitches from the cluster itself, not from the individual hosts.

Optionally, configure the properties for the dVSwitches (see Abiquo configuration properties and search for .dvs.).

...

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:

On the Remote Services server, edit the abiquo.properties file and add the following property

...

.

...

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

...

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

...

To configure Abiquo to 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.

...

  • datastore is accessible

  • datastore is mounted as read/write on all hosts in the cluster or the current host

  • datastore is not in maintenance mode

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 add, update, and delete datastores, refresh the datastores on the host in Abiquo:

  1. Edit the physical machine, and go to the Datastores

...

  1.  tab

  2. Click the round arrow refresh button. 

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 table , Add 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.

...

Log in to the Abiquo Remote Services server (or for a Monolithic installation, log in to the Abiquo Server) and set the appropriate properties for your system to appropriate values in the the /opt/abiquo/config/abiquo.properties file.

...

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

...