5. Creating and Managing vApps : 5.1 Migrating Workloads to a vCloud : 5.1.3 vApp Migration
5.1.3 vApp Migration
In conjunction with vCloud Connector, a hybrid vCloud enables vApps to move between public and private vCloud services. Prior to vCloud Director 5.1, some configurable vApp elements are not transported with the migration process. Keep track of what is and is not transported as you might need to reconfigure the vApp after the migration so that it functions properly. You can view the configuration parameters from two perspectives—from the point of view of the vApp itself or of the virtual machines contained within the vApp. With vCloud Director 5.1, lossless OVF export is provided to enable greater portability between vCloud environments.
NoteMetadata defined on vCloud entities is not transported during the migration process. Migration Process
To move a vApp from vCloud A to vCloud B with the vCloud Connector:
1. Export the virtual machines in the vApp from vCloud A to an OVF.
5. Stage them on the vCloud Connector appliance with the vCloud API. The data is transferred to the vCloud Connector appliance over HTTPS.
2. Use the HTTPS upload command to upload the staged OVF to vCloud B.
3. Import the OVF into vCloud B’s catalog or directly to an organization datacenter.
The migration process can be carried out manually with the upload and download capabilities of the vCloud Director user interface or by programming the vCloud API. vCloud Connector simplifies vApp migrations, but is not required. vApp Power Action Configuration
When a vApp is migrated, the vApp itself defines the virtual machine start and stop settings within the vApp. The parameters encapsulated within the vApp are:
*Start/Stop Order.
*Start Action.
*Start Delay.
*Stop Action.
*Stop Delay.
All of these parameters are transferred with the vApp from one vCloud to another. The configuration in vCloud A remains consistent in vCloud B. vApp Network Configuration
Configuration parameters are associated with virtual machines in the migrated vApp, including network segments (vApp networks) that are private to the vApp itself in the source vCloud. Some of these configuration items are maintained during a migration, while others require reconfiguration by the vApp user after migration.
vApp networks are not maintained across a vCloud migration—vApp networks that are defined in a vApp in vCloud A are not created and mapped to the virtual machines within the vApp in vCloud B. Assuming that vCloud A and vCloud B use the same network topology, after moving the application to vCloud B, the end user must complete the configuration process by recreating the vApp networks as they were defined in vCloud A. Hardware Configuration
Hard disk configuration and disk bus type are maintained across a vCloud migration. If a specific disk bus type is selected for a virtual machine’s disk, this setting is maintained when the virtual machine migrates from vCloud A to vCloud B.
Prior to vCloud Director 5.1, network interface assignments, configuration types, and network adapter types are not maintained across a vCloud migration. When the vApp is transferred, the virtual machine network interfaces revert to the default adapter type, flexible. With vCloud Director 5.1, the lossless OVF export capability preserves these settings.
IP addresses are not held across a vApp migration and must be reconfigured to the new vCloud IP addressing scheme. The end user must reconfigure all virtual machine network adapter settings for a migrated vApp. Guest OS Customization
Even if Enable Guest Customization is not selected in vCloud A, it is enabled in vCloud B when the vApp is migrated, regardless of whether the virtual machine has an installed operating system and VMware Tools™.
Most password reset parameters are maintained. When the password reset parameters are configured for the virtual machine, the settings are transferred from vCloud A to vCloud B. However, if the virtual machine configuration specifies a default local administrator password, this information is not transferred to vCloud B. The end user must re-enter the default password for the virtual machine. Resource Allocation
Resource allocation controls set on the individual virtual machines in a vApp are maintained across a migration from vCloud A to vCloud B. However, for the settings to be used, the vApp must be deployed to a virtual datacenter that uses a Reservation Pool allocation model. Datacenters that use the Allocation Pool or Pay As You Go model do not support resource allocation controls.
The following table summarizes vApp parameters and indicates whether they are maintained across a migration.
Table 2. vApp Parameters
Configuration Item
Start/Stop Order
Start Action
Stop Action
Start/Stop Delay
vApp Networks
Networks and associated configurations are lost. Networks must be redefined and NICs attached.
NIC Assignment
(non-vApp network)
NICs must be reassigned.
Guest Customization Enabled
Checkbox is selected in target vCloud.
CPU Hot Add
Memory Hot Add
Synchronize Virtual Machine Time
Password Reset
Default Password
Defaults to blank field in UI.
Disk Bus Type
Network Adapter Type
Defaults to flexible.
Resource Allocation
When vApp is deployed to Reservation Pool virtual datacenter.
OVF Properties
Accessed through VMware Tools and used for scripting, fetching, and for post-configuration and provisioning.