...
- The first disk is considered to be the boot disk, if it is an iso instead the VM creation will fail. If not it can result in boot issues.
- All standard parmeters like size should be in there for all the vmdks and ISOs contained in OVA
- An ovf file is considered to be in proper format and with valid information.
- It is also assumed that the imported OVA file is compatible with vCenter
- Multi-disk OVA file that bundles a single VM with multiple disks and an optional ISO
- The disks should be bundled in the OVA with only relative paths in the OVF file (href attribute)
- There will not be any empty disk in the OVF file, all disks will point to a valid File resource
- Since Cloudstack treats each disk and iso file as separate unit, the specifications contained in InstallSection or StartupSections of OVF are ignored.
- Cloudstack has its own mapping for operating systems and the information contained in OperatingSystemSection of OVF is ignored
- The files are in uncompressed format, 'ovf:compression' attribute on File will be ignored
- Files are not chunked and 'ovf:chunkSize' attribute is ignored
- Any manifest and certificate files will be ignored
- Disk format vmdk for data disk
- Essentially we will only be looking at disk information in the ovf and other spec will be ignored
- If there is a ISO in the ovf package then it will be mounted as CD-ROM
- The network section is ignored and network is instrumented by Cloudstack.
...
{"serverDuration": 124, "requestCorrelationId": "1b15ec7d0fc47d24"}