Response:
200 OK
View the OVF Descriptor of a vApp Template
The representation of a resolved vApp template includes a link to its OVF descriptor.
<Link rel="ovf" type="text/xml"
A GET request specifying the URL in the href value of this Link returns the descriptor, as shown in
Example
4‐9. Only resolved VAppTemplate elements include this link. To get the OVF descriptor that defines
a vApp or virtual machine, you must start with the template from which it was created.
When you view the OVF descriptor of a vApp template, it includes deployment‐specific information.
Example 4-9. View the OVF Descriptor of a vApp Template
Request:
GET http://vcloud.example.com/api/v1.0/vAppTemplate/vappTemplate-268/ovf
Response:
200 OK
Content-Type text/xml
...
<Envelope ...>
<DiskSection>
<Info>Virtual disk information</Info>
<Disk ovf:capacity="100" ovf:capacityAllocationUnits="byte * 2^20" ovf:diskId="vmdisk1"
</DiskSection>
<VirtualSystem ... ovf:id="Ubuntu Template">
...
</VirtualSystem>
</Envelope>
N
The OVF descriptor does not include any File references. These are removed by the server after the
OTE
template is resolved and recreated when the template is enabled for download.
Download a vApp Template as OVF
A vAppTemplate can be downloaded as an OVF package. After locating the template by browsing a catalog
or vDC, a client can request that the template be enabled for download. This operation constructs a download
URL for the template's OVF descriptor file and adds it to the template. A client can download the descriptor
from this URL, examine it to discover the download URLs of the files it references, then make a series of GET
requests that download the files themselves.
When you download a vApp template as OVF, all deployment‐specific information is removed from the OVF.
VMware, Inc.
href="http://vcloud.example.com/api/v1.0/vAppTemplate/vappTemplate-268/ovf"/>
ovf:fileRef="file1"
ovf:format="http://www.vmware.com/interfaces/specifications/
vmdk.html#streamOptimized"/>
Chapter 4 Provisioning
47