Abiquo 4.0 introduces support for vCloud Director as a public cloud provider. Abiquo works with vCloud “Organizations” as Abiquo public cloud regions.
Before you add a vCloud Director to Abiquo, you must register a Cloud Provider Proxy remote service in Abiquo.
When creating a public cloud region, enter the identity in the format user@org to retrieve the organization. Later, you will need to edit the Abiquo enterprise, select vCloud Director and enter the identity and credential again as enterprise credentials to synchronize virtual resources.
In this initial version, Abiquo imports virtual datacenters and networks from a vCloud Director organization. Abiquo also synchronizes these elements. But you cannot use Abiquo to create virtual datacenters or networks in vCloud Director. In the initial version, all networks are currently displayed as private networks, even direct external 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 templates have CPU and RAM values, but the user cannot edit these values in the virtual machine.
When adding IPs to a virtual machine, the user can identify networks in Abiquo by ???.
When Abiquo creates virtual machines in vCloud Director, it creates a vCloud virtual appliance for each virtual machine.
The user can create firewalls, with TCP and UDP protocols, and with a source or destination that can be an IP, a range of IPs, or “internal”. The user can create load balancers, with either internal or external IPs ???. The external network for load balancers will be defined by a property in Abiquo. ???
In this initial version, you cannot create instance templates of virtual machines. In future versions, support could be provided for extra hard disks and ISOs.