Abiquo 5.0

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


SEO Metadata
keywordsVMware, vCloud, Director, manage, synchronize, user, interface
titleManage vCloud Director in Abiquo hybrid cloud

Abiquo manages vCloud Director as part of the hybrid cloud platform, and this page describes the features and management model

Abiquo supports vCloud API version 9.0. 

For configuration and a list of features supported by Abiquo, see vCloud Director

Abiquo supports vCloud Director (vCD) as a private cloud provider using the public cloud interface. vCD is a self-contained cloud with an endpoint for access and an API to manage it, so although vCD can be a private or public cloud, it best fits the public cloud model in Abiquo, so we manage it as a public cloud.

Abiquo works with vCD organization virtual datacenters as Abiquo public cloud regions.

Include Page
vCloud Director supported versions table
vCloud Director supported versions table

Credentials models for vCloud Director


Administrators can select hot-reconfigure options for their templates if the vCD operating system and template supports these options. They can also select the network driver, which by default is now VMXNET3.



manages VDCs and networks

Abiquo onboards and synchronizes the virtual datacenters and networks of a vCD organization.


Users in Abiquo can work with vCloud networks as follows:

  • Manage private networks
    • vApp networks, which may be isolated or have an external connection
  • Synchronize these external networks:
    • External networks outside the Org VDC but connected to the Edge, for use by load balancers but not VM vNICs

    • External networks outside the Org VDC with a direct connection to OrgVDC as OrgVDCNetwork

    • Isolated Org VDC networks, for use by VM vNICs but not load balancers

  • Synchronize and create and delete these external networks in the Virtual datacenters view
    • OrgVDC networks inside the OrgVDC and routed through the Edge

Administrators can create NAT networks for public cloud regions and users can manage NAT rules for their VMs.

The platform does not onboard or manage static routes for vCloud networks.

Screenshot: Selecting a vCD virtual appliance to onboard as an Abiquo virtual datacenter.   


The integration manages firewalls on private and external networks.

NAT networks and rules

The administrator can create a NAT network using an external network that is connected to the orgVdc Edge gateway or a subnet of this network. Note that the platform does not detect NAT configurations in vCloud so the administrator must provide appropriate values to prevent errors in the virtual datacenters.

Image Added

You can then obtain NAT IPs for your virtual datacenters and create NAT rules for your VMs. The platform will automatically create a firewall rule for each NAT rule. To display this rule, the user will need to synchronize the classic firewall. The platform does not create a default SNAT rule for the virtual datacenter as in the NSX NAT integration so users should create SNAT rules in their VMs.

Image Added

VM firewall policies

When the virtual datacenter (vCloud vApp) has an external (fenced) connection through an Edge gateway, users can create firewall policies in their virtual datacenter and assign them to their VMs. 

Users onboard and create load balancers

The user can onboard and create load balancer policies. In vCloud Director, load balancers can span vApps, so to access all load balancers in the platform, select All VDCs and then select the vCloud region.


The integration creates load balancers on external networks. 

See vCloud Director load balancers table and Manage Load Balancers

For OrgVDC networks created using Abiquo, an initial limitation is that you can only use the gateway address for load balancers.

Onboard VMs into Abiquo

When you onboard VMs, the platform creates a placeholder template for each VM, but this template is unavailable, which means that the user cannot undeploy and deploy the VM again from it.


Users can add IPs and select firewalls and load balancers for their VMs.

Users can create additional disks and attach and detach additional disks from their VMs, and for SCSI disks they can do this with hot reconfigure. Users can resize disks if their organization virtual datacenter is not using the fast provisioning. Users cannot change the boot sequence or the bus/unit number, but the platform will recognize changes made directly in vCD. Hard disks belong to one VM only and you cannot reuse them in another VM.


Abiquo can provide internet access or external access from private networks through an external network.

Users can create Abiquo instance templates from VMsVM disks.

The user can request a remote console, and the platform will open it using WebMKS. See Branding WMKS.