5.1 V2C Self-Service
The V2C self-service reference implementation consists of deploying vCloud Connector 2.7.1 so that it can be used to migrate a workload from a vSphere environment to a vCloud Director environment. This consists of deploying the vCloud Connector Server and two vCloud Connector nodes, one in the customer’s data center where source VMs in vSphere exist and one in the target vCloud Director Organization where they will be migrated. After the appliances are deployed using OVF import (more information in the installation and configuration guide), you can reach the initial configuration screens on HTTP port 5480.
Figure 34. vCloud Connector Server on vSphere
The vCloud Connector Server must be registered with vSphere to appear in the C# vSphere client as a “Solution”.
Figure 35. vCloud Connector Node on vSphere
The customer then deploys and registers the same vSphere environment with their vCloud Connector node.
Figure 36. vCloud Director vCloud Connector Node
Within the vCloud Director environment, there must be another vCloud Connector node. In this reference implementation, the vCloud Connector node is placed inside the tenant (Org1).
Figure 37. vCloud Connector Node on vCloud Director
That node must be able to communicate with the vCloud Director URL.
Figure 38. Linking vCloud Connector Nodes to vCloud Connector Server
Finally, you must make both nodes available over the network to be registered in vCloud Connector Server.
Figure 39. vCloud Connector View in vSphere Client
Now you can migrate workloads from vSphere to vCloud Director leveraging vCloud Connector.
