4.3.2 vCloud Connector Data Flow
The data flow in the following figure indicates the vCloud Connector Server is located on the customer premises. As shown in the bottom right hand corner of
Figure 14, there is a second vCloud Connector Server deployed by the VMware Cloud Provider in the case of ODT.
Figure 16. vCloud Connector Ports and Data Flow
As shown in the previous figure:
1. The customer premises vCloud Connector Server is responsible for presenting the vCloud Connector client interface for the initial migration.
2. The customer premises vCloud Connector Node is instructed to begin an export of the vApp.
3. That export is invoked from vSphere with the VIM API.
4. On the vSphere datastores, parallel operations are started with regard to the activities of streaming data from the datastores through the on-premises vCloud Connector Node. These operations occur over the VMkernel port.
5. More activities are used to pass data over to the VMware Cloud Provider Program based vCloud Connector Node using MIME multipart type transfer over HTTP(S) to allow for check pointing of progress.
6. After the transfer is complete, the vCloud Connector Node in the tenant Org signals the vCloud Director APIs to perform an import.
7. The workload is transferred to vCloud Director transfer server storage.
8. vCloud Director then instructs the vCenter Server to import the vApp.
9. After making the vApp available in the datastore, the vApp appears in the vCloud Director Organization Catalog where it can be imported, further configured, and powered on.
