4. Automated Import of Virtual Machines to vCloud Director : 4.4 Choose Virtual Machines to Import : 4.4.1 Workflow Inputs and Outputs
4.4.1 Workflow Inputs and Outputs
The Import a resource pool VMs to a virtual data center and Import a folder virtual machines to a virtual data center workflows have nearly identical inputs. The destination and options sections are identical, and the source section varies based upon the selected workflow, as follows:
*Virtual Machine folder or Resource pool – The vCenter container for the virtual machines to be imported (mandatory input).
*Include sub folders or Include VMs from child Resource pools – Include virtual machines in sub-containers recursively.
*Virtual Data Center – The created vApp is placed in this datacenter (mandatory input)
*Storage Profile – If set, the vApp is placed on the datastores defined in the specified storage profile.
*Import VMs with networks that cannot be reconnected – If set to no the virtual machines that have networks that do not have an organization virtual datacenter network mapping to an external network are not imported. If set to yes these virtual machines are imported and have network cards that are not connected to any network.
*Deploy the vApp – Configure the virtual machines to be powered on.
*Power On the vApp – Start the virtual machines in the vApp.
*Move VMs – Migrate virtual machines instead of making a copy. Setting this option to yes dramatically reduces the duration of the import when the virtual machine is not moving to a new datastore. Setting this option to no makes a copy of the original virtual machine, thus allowing you to revert back using the original virtual machine in case there is an issue using the imported one.
*Number of concurrent imports – The number of imports started from vCloud Director in parallel. Because vCenter is able to run a number of tasks issued from different imports this can speed up the overall import process. If the value is set too high it can either slow down disk accesses or does not make any changes because vCenter queues the additional operations.
The workflow outputs are vApps – The vCloud vApps resulting from the import of the vCenter virtual machines.