Only certain types of networks on a vCloud Director cloud can be extended to a public vCloud. The virtual machines that you want to move with the Stretch Deploy command must belong to a supported network on the private vCloud Director cloud.

Stretch Deploy is only supported for VMs deployed in a routed vApp. The routed vApp can be connected to a Direct Org VDC or a Routed Org VDC network.

The routed vApp must be deployed in the following way.

A vApp network must be created in the routed vApp.

All the VMs in the vApp must be connected to this vApp network.

The external network in the vCloud Director cloud must be associated with a port group created in a 5.1 vSphere Distributed Switch (VDS).

The IP allocation type in the vApp network must be set to either DHCP or Manual Static. A Static Pool IP allocation type is not supported.

If the vApp network is connected to a Routed Org VDC network, external IP addresses must be configured in the Edge gateway sub-allocation pool for the Org VDC. See How to Configure External IP Addresses in the Edge Gateway in vCloud Director.

The vApp network cannot be connected to an Isolated Organization network.

If your private cloud uses an HTTPS proxy server that is configured with a fully qualified domain name (FQDN) to reach the Internet, then the corresponding DNS server must be specified in the vShield Edge of the vApp network that you want to stretch. Specify the DNS server settings in the vShield Manager that is associated with the cloud. See How to Configure a DNS Server in vShield Manager.

The only network that is currently supported for Stretch Deploy in a private vCloud Director cloud is a routed vApp network.

The routed vApp can be connected to a

Direct Org VDC network

Routed Org VDC network

Stretch Deploy is not supported for VMs deployed in a

Direct vApp

Fenced vApp

Isolated vApp

Stretch Deploy is not supported for VMs deployed in a routed vApp that is associated with an Isolated Org VDC Network.

Stretch Deploy is not supported for an entire vApp.