Hybrid Cloud Using VMware vCloud Connector

VMware vCloud® Director™ (vCloud Director) orchestrates the provisioning of software-defined data-center services to deliver complete virtual data-centers for easy consumption in minutes. It serves as an umbrella for vCloud Connector and vCenter Orchestrator Plug-ins.

vCloud Connector is an enterprise product that provides a single UI for overseeing multiple public and private clouds and transfer cloud content from one cloud to another. It enables connecting multiple clouds, both internal and external, in a single user interface.

Value Proposition:
  • Flexible Business Operations – Use the cost-effective public cloud for non-sensitive operations and on the private cloud for critical and sensitive operations.
  • Enhanced Agility – Hybrid cloud offers options for scaling into public cloud if on-premise resources are exhausted
  • Cost versus Flexibility – Hybrid clouds provide ways to balance cost and infrastructure flexibility thus allowing optimal ROI


Calsoft’s Expertise:

With our expertise in VMware products, we help our customers orchestrate their storage and virtualization infrastructure by way of:

VMware vCloud Connector Components

Component Details
vCloud Connector UI vCloud Connector UI is the user interface that the vCloud Connector server produces. It can be surfaced in vSphere Client. You decide where to display the UI during the configuration process.
vCloud Connector Server            The vCloud Connector server is a virtual appliance that coordinates the activity of vCloud Connector, controls vCloud Connector nodes, and produces the vCloud Connector UI. Only one vCloud Connector server is needed.
vCloud Connector Nodes vCloud Connector nodes are virtual appliances that handle transferring content from one cloud to another. A vCloud Connector node must be installed in every vSphere or vCloud Director-based cloud that vCloud Connector oversees.

Hybrid Cloud in Action – Copying a VM from vSphere Cloud to vCloud Director

  • Assuming vCC Server isn’t running SSL, vCC UI (vSphere Client or vcloud.vmware.com) will send copy request to vCC Server on TCP port 80.
  • vCC Server will forward the request on TCP port 443 to vCC Node (since SSL is enabled by default in vCC Node).
  • vCC Node will send request to vCenter Server (using REST API on TCP port 443) to initiate “Export OVF Template” operation for the source VM.
  • Accordingly, vCenter Server will locate the VM, start export task, and direct ESXi Server (hosting the VM) that template should be exported in vCC-Node (the path will be vCC-Node transfer storage).
  • The initial copy request sent from vCC-Server to vCC-Node includes copying the OVA template after export to destination vCC-Node transfer storage. Copying between vCC-Nodes uses checkpoint-restart. This is good to resume copying in case transfer fails instead of zero-restart.
  • Once copy is completed, the destination vCC-Node will connect to vCD Server using REST API to start importing OVA template as vApp Template in Org Catalog. Next will be importing vApp from vApp Template. Both actions will require communication in the background between vCD Server and associated vCenter Server which we have seen in vSphere Client Snapshot above.

Contact Calsoft today to accelerate your Offshore Product Engineering initiatives.