VMware CLOUD DIRECTOR 1.0 Bedienungsanleitung PDF herunterladen (Seite 10)

PERFORMANCE STUDY /10

VMware vCloud Director 1.0 Performance and Best Practices

OVF File Upload

The Open Virtualization Format (OVF) is an open, portable, efficient, and extensible format for packaging and

distributing virtual systems. OVF was developed by the Distributed Management Task Force (DMTF), a

not‐for‐profit association of industry members dedicated to promoting enterprise and systems management and

interoperability. The vCloud API supports Version 1 of the OVF standard. For more information, refer to

Open

Virtualization Format Specification

[1] and

Open Virtualization Format White Paper

[2].

Because it is a widely-accepted standard format, OVF provides considerable flexibility in accommodating the

needs of a diverse collection of virtualization technologies. While this flexibility entails more complexity than a

vendor‐specific format might require, it also provides many advantages.

•

Virtual machines and appliances are distributed as OVF packages by many vendors.

•

Many vendors, including VMware, offer tools that simplify creating and customizing OVF virtual machines,

support converting virtual machines on existing virtualization platforms to OVF, or both.

•

OVF has the power to express the complex relationships between virtual appliances in enterprise

applications. Most of the complexity can be handled by the author of the appliance rather than the user

deploying it.

•

OVF is extensible, allowing new policies and requirements to be inserted by independent software vendors

and implemented by the virtualization platforms that support them without requiring changes to other

clients, other platforms, or the vCloud API itself.

Applications can be deployed in the vCloud infrastructure using vApps, which are made available for download

and distribution as OVF packages. A vApp contains one or more VM elements, which represent individual virtual

machines. vApps also include information that defines operational details for the vApp and the virtual machines it

contains. After an OVF package is uploaded to a vDC, a vApp template is created. A vApp template specifies a

set of files (such as virtual disks) that the vApp requires and a set of abstract resources (such as CPU, memory,

and network connections) that must be allocated to the vApp by the vDC in which the template is deployed.

Instantiation creates a vApp from the files specified in the template, and allocates vDC‐specific bindings for

networks and other resources. Figure 5 shows the state transitions from an OVF package to a vApp template and

a vApp to be deployed. For more information, refer to

vCloud API Programming Guide

[7].

Figure 5. vApp State Transitions

As shown in Figure 6, an OVF file resides in a client machine. Before it can be uploaded into the cloud, the OVF

file needs to be transferred to the vCloud Director cell. This transfer could very likely happen in a WAN

environment where the bandwidth and speed of the network are limited. The performance also changes when

there are concurrent file transfers within one cell. The following sections describe all of these aspects in more

detail.

OVF Package

descriptor.ovf

disk0.vmdk

vApp Template

<VApp

Template...status=”8”

href=”http://.../vapp

Template-3”>

...

</VApp Template>

vApp

<VApp...status=”8”

deployed=“false”

href=”http://.../vapp-

9”>

...

...

</VApp>

upload

instantiate

1 2 ... 5 6 7 8 9 10 11 12 13 14 15 ... 31 32

Kommentare zu diesen Handbüchern

Keine Kommentare

VMware CLOUD DIRECTOR 1.0 Bedienungsanleitung Seite 10

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Datenbanksoftware VMware CLOUD DIRECTOR 1.0