The Broker onboards and synchronizes virtual datacenter names as follows:
If the Broker onboards each of the VMs in a vCloud VDC into its own virtual appliance in the Broker, then the Broker will use the VM Label as the name of the virtual appliance.
When you onboard a VM, the Broker creates a placeholder template. In the Apps library, this template will be marked as Unavailable because it cannot be used to create a VM. Before you undeploy the VM you MUST create an Instance template, which will clone the VM disks. Otherwise, you will not be able to recreate the VM. When you undeploy an onboarded VM, the Broker will destroy the VM and the placeholder template.
of an onboarded VM, the platform will update the VM template in the Apps library to point to this template and put it in the Available state. The Broker will save a multi-disk template correctly to the vCloud registry, but it will also appear to have a single disk in the Broker. If you undeploy a VM with a saved instance template, when you deploy the VM again, the platform will use the saved instance template. Remember to check your configurationAfter you create an instance template
When the platform onboards a template from vCloud, it caches the template details in the Apps library as a template, and points to the vCloud template. When you modify the template in the Broker, this sets the default configuration of VMs deployed in the Broker using the template. It does not modify the vCloud template. After you create a VM, you can change its resources by editing the VM configuration.
If you deploy a VM and then add or remove disks in vCloud, when you redeploy the VM, the platform will use the template disks.
Users can modify cores per socket values in their VMs. The cores per socket must always be a divisor of the CPU.