Abiquo 4.6.1 introduces the following improvements to the vCloud Director integration.

Cores per socket

Abiquo 4.6.1 supports cores per socket in vCloud Director.

The platform onboards the cores per socket value of vCloud Director templates and the administrator can modify this value for use in Abiquo.

When users edit their VM configuration, they can also modify the cores per socket.

Remember that the number of CPUs must always be divisible by the number of cores per socket. After the upgrade to Abiquo 4.6.1, the platform will automatically update the cores per socket of VMs but not templates. To ensure that templates reflect the actual values in vCloud, the administrator must import templates again to update them.

Multi-disk templates and VMs

In Abiquo 4.6.1, the platform has improved management of VMs and templates with multiple disks in vCloud Director. The platform is now able to: detect all the disks of a VM and update disk info as part of the periodic check; take instances of all disks in a VM; and use multi-disk templates.

When the user creates a VM with a multi-disk template, the platform will display one disk only. Then when the user deploys the VM, the synchronization will recognize all the disks with the correct capacity, sequence, and controller.

To display the disks, in VApp view, the user can select the VM and go to VM details → Storage.

The platform also imports multi-disk VMs and recognizes when the user has made changes to storage in vCloud. The platform detects the following storage changes during the periodic VM check or VDC synchronization:

add a new disk
remove an existing disk
resize a disk
change controller or bus/unit

When the user edits the VM, the Edit virtual machine dialog has no Storage tab because you cannot reconfigure vCloud storage within the platform.

When the user makes an instance of a VM with multiple disks, the platform will display the disk selection dialog with all disks, and the instance template will contain all of the VM disks.