Abiquo 4.0 introduces initial support for vCloud Director as a public cloud provider. Abiquo works with vCloud organizations as Abiquo public cloud regions.
For a list of features supported by Abiquo, see vCloud Director features table
Before you add vCloud Director to Abiquo, you must register a Cloud Provider Proxy remote service so Abiquo can use it to retrieve the organization.
When creating a public cloud region, enter organization administrator credentials to retrieve the organization. The identity is in the format user@org. Later, you will need to edit the Abiquo enterprise credentials, select vCloud Director and enter the identity and credential again to work with the region.
Abiquo imports and synchronizes virtual datacenters and networks from a vCloud Director organization. The integration does not support the creation of virtual datacenters or networks in vCloud Director, and Abiquo displays direct external networks as private networks.
The vCloud Director integration enables the user to create firewall policies and load balancer policies with vCloud Director. The firewalls support TCP and UDP protocols, and with a source or destination that can be an IP, a range of IPs, or “internal”. The integration supports load balancers on internal networks.
Users can deploy virtual machines using templates from the vCloud catalog. In contrast to other public cloud providers that work with hardware profiles, vCloud Director works with CPU and RAM values. For vCloud Director, administrators can activate Abiquo hardware profiles as in private cloud. When users create virtual machines, they can modify the CPU and RAM values, or select hardware profiles.
Users can add IPs and select firewalls and load balancers for their virtual machines. When Abiquo creates virtual machines in vCloud Director, and it creates a vCloud virtual appliance for each virtual machine. The integration does not support the creation of instance templates from virtual machines.