When you move a VM from a private datacenter to a public vCloud with the Stretch Deploy command, vCloud Connector stretches its network to the public vCloud, then copies and deploys it.

From a private vCloud Director cloud, you can only move a VM that is contained in a vApp. You cannot move an entire vApp.

The destination location must be a public vCloud.

In addition to the prerequisites listed, the VM that you stretch deploy must meet the following requirements.

The VM must be powered off.

The VM's parent vApp must be powered on.

If the VM has already been moved, you cannot stretch deploy it again.

If the VM is currently being moved, you cannot stretch deploy it again.

You cannot stretch deploy a vShield Edge VM.

1

In the Browser panel on the left, expand the Clouds tree and select a private vCloud.

2

In the Inventory panel, click the Virtual Machines tab.

3

Select the VM that you want to move to the public vCloud.

Available action buttons appear at the top of the panel.

4

If the VM is powered on or suspended, click the Power Off icon at the top of the panel to power it off.

Note

The VM that you want to move must be powered off but its parent vApp must be powered on.

5

Click the Stretch Deploy icon.

If the Stretch Deploy icon is disabled, point to the icon to view tooltip information on why the action is unavailable. For more information, see the Prerequisites listed above.

The Stretch Deploy wizard appears.

6

Select a catalog in the source cloud for vCloud Connector to store a temporary vApp template.

vCloud Connector needs to create a temporary vApp template while moving a VM to a vCloud; this is a vCloud Director requirement. The temporary vApp template will be deleted after the VM is deployed in the public vCloud.

7

Select an external IP address in the source cloud for vCloud Connector to create SNAT or Firewall rules, if required.

This field only appears if the routed vApp that contains the VM is connected to a Routed Org VDC network. It does not appear if the routed vApp is connected to a Direct Org VDC network.

If no IP addresses are displayed, check if you have configured external IP addresses in the Edge gateway sub-allocation pool for your Organization VDC. See How to Configure External IP Addresses in the Edge Gateway in vCloud Director.

8

Click Next.

9

Select the public vCloud to which you want to move the VM.

Note

You can only move a VM to a public vCloud; you cannot move it to a vSphere cloud.

10

Specify a name for the stretched vApp in the public vCloud. vCloud Connector adds a Stretched_ prefix to the name.

11

Select a catalog in the public vCloud in which to store the vApp template for the VM. All the catalogs available to your organization are listed.

vCloud Connector will upload the VM to the public vCloud as a vApp template; this is a vCloud Director requirement. It will then create a vApp for the VM.

12

Click Next.

13

In the Select Resources page, select a virtual datacenter in which to store the VM. All the virtual datacenters in your organization are listed.

14

Select an Org VDC network from the list of Routed Org VDC networks and Direct Org VDC networks that belong to the Organization VDC you selected.

vCloud Connector will create a routed vApp network for the VM in your Organization VDC in the public vCloud and will connect it to the Org VDC network that you select here.

15

If you selected a Routed Org VDC network, you must also select an External IP address. All available, valid IP addresses configured in the Edge gateway are listed.

vCloud Connector uses this IP address to create a DNAT entry and a firewall rule in the Edge gateway of the Routed Org VDC network that you selected. This is required to create the SSL VPN tunnel.

Note

The DNAT entry is created for port 443. Select an IP address that is not used for port 443.

If no IP addresses are displayed, check if you have configured external IP addresses in the Edge gateway sub-allocation pool for your Organization virtual datacenter. See How to Configure External IP Addresses in the Edge Gateway in vCloud Director.

16

The Public IP field is required when the IP addresses configured in the External Network in the public vCloud are not public IPs. vCloud Connector needs a designated public IP address in the public vCloud that can be reached from the source network that you want to stretch, to establish the SSL tunnel.

This public IP address must not be used by any other service using port 443.

Set this field regardless of the Org VDC network that you selected.

For example, if you have selected a Direct Org VDC network and the gateway IP of that network is not a public IP (that is, it cannot be reached from the source network that you want to stretch), then enter a public IP address in this field. Also ensure that the gateway IP of the Direct Org VDC network can be reached from the public IP that you enter in this field.

If you have selected a Routed Org VDC network, then ensure that the public IP that you enter in this field can be reached by the External IP that you selected for DNAT and Firewall configuration in the previous step.

17

Click Next.

18

If the network that you want to stretch goes through an HTTPS proxy server to reach the Internet, select Use a proxy server and specify the HTTPS proxy server information in the Proxy page.

Option

Description

HTTPS Proxy Server (FQDN or IP address)

The IP address or fully qualified domain name (FQDN) of the proxy server.

Note

If you specify an FQDN, ensure that the corresponding DNS server is configured in the vShield edge of your source network. You do this in vShield Manager. See How to Configure a DNS Server in vShield Manager.

Proxy Port

The port that the proxy server uses

Proxy Username

(Optional) The user name for the proxy server

Proxy Password

(Optional) The password for the proxy server

19

Click Next.

20

If you want to power on the VM after moving it to the public vCloud, select Power on deployed entity.

21

Click Next, review your selections, then click Finish.

vCloud Connector creates a routed vApp network in your organization in the public vCloud, creates a Layer 2 SSL VPN tunnel between the private network and the routed vApp network in the public cloud, and copies and deploys the VM in the new vApp in the public cloud.

The VM continues to be part of the private network. Its IP address and MAC address remain the same. You can continue to use it as if it were still in your private datacenter.

You can track the progress of the Stretch Deploy command in the Tasks panel. See Track the Progress of the Stretch Deploy Command for more information.

Note

If the source VM's IP allocation mode was Manual Static, after the Stretch Deploy command is successfully completed, you must delete a NAT entry that was created for the VM in the public vCloud. Log in to the public cloud and double-click on the stretched vApp. If the VM in the stretched vApp has a Manual Static IP mode, go to the vApp network and delete the NAT entry created for the VM manually.

Note

After you move a VM to a public vCloud with the Stretch Deploy command, do not power on or delete the VM in its original location.

Note

In the public vCloud, do not modify the vApp network created by vCloud Connector. Specifically, do not change any network configuration settings (such as DHCP, NAT, or firewall settings) on the vShield Edge of the vApp network.