VMware CLOUD DIRECTOR 1.0 Instrukcja Użytkownika Pobierz pdf (Strona 16)

PERFORMANCE STUDY /16

VMware vCloud Director 1.0 Performance and Best Practices

Clone vApps across vCenter Server Instances

In vCloud Director 1.0, a VM clone operation is triggered when a vApp is instantiated from a vApp template.

When the underlying organization vDC does not have access to the source datastore on which the vApp

template resides, the same mechanism used to upload an OVF package is used to create the vApp. A unique

feature is implemented in the vCloud Director 1.0 release to improve the latency. This feature works when the

underlying organization vDC has access to the source datastore of the vApp template. The following section

provides more details on this topic.

Experimental Setup

The test bed consisted of two vCenter Server 4.1 instances. Each vCenter Server instance had two ESX 4.1 hosts in

a cluster.

Figure 11. Testbed Setup for Inter-vCenter Clone Experiments

Two provider vDCs were created based on the two clusters from these two vCenter Server instances.

Corresponding organization vDCs were derived from the two provider vDCs. These two organization vDCs were

presented in the same organization. We then studied three datastore configurations to show the latency of the

cloning operation. Our tests show that datastore accessibility plays a very important role in terms of latency.

VMware vCloud Director 1.0

VMware vSphere 4.0

vCenter Server 1

and its Database

2 Classic ESX

4.1 Hosts

vCloud Director Cell

vCloud Director

Web Interface

vCloud Director

Database

HTTPS

vCenter Server 2

and its Database

2 Classic ESX

4.1 Hosts

1 2 ... 11 12 13 14 15 16 17 18 19 20 21 ... 31 32

Brak uwag

VMware CLOUD DIRECTOR 1.0 Instrukcja Użytkownika Strona 16