First, there’s no official automated procedure for the migration yet. Here is a method to get some of your vCD-managed VMs into vCAC.
- Because vCD names the actual VM with an ugly UID, we want to clone the VM to a “nice” name with vSphere. As always, make sure you have sufficient room on your storage. The destination cluster for the clone should already be included as a compute resource in vCAC/IaaS.
- In the vSphere Web Client, edit the clone VM, navigate to the “vApp Options” tab and uncheck “Enable vApp Options”. This removes the vCloud Director properties from the VM.
- Request (or wait for) an inventory data collection to run against the compute resource in vCAC.
- Login to vCAC as a Fabric Admin, navigate to Infrastructure|Infrastructure Organizer|Infrastructure Organizer.
- Click “Next” on step 1 of the Infrastructure Organizer wizard
- On step 2, check the box beside the Compute Resource that contains the clone VM, click “Next”.
- On step 3, ensure your compute resource is assigned to a Fabric Group and, optionally, a Cost Profile, click “Next” to continue.
- In step 4, you’ll be presented with a list of the VMs in the compute cluster that are not managed by vCAC. For each VM to be imported, click the pencil to edit it and assign to a Business Group. Any VMs you do not want to import, just do not assign to a Business Group. Click “Next” when done.
- In step 5, you’ll edit your selected VMs to assigning them to an existing Blueprint, Reservation and Owner. This is done so that vCAC knows how to handle the VM’s lease, resource allocation and who has access. Next!
- Last Step, verify how many machines will be registered. Click Finish to complete the import.
- Once the VMs are imported, the owner or appropriate Business Group Manager can logon to vCAC, find the VM under his or her items and power it on from there.
- Lastly, once the VM’s operation is verified, the original VM in vCloud Director should be backed up and removed.
This is not intended to import a vApp into a multiple-machine blueprint or similar. This is just for importing individual VMs into a Business Group.
I used vCloud Director v18.104.22.168 and vCloud Automation Center v22.214.171.124.