Versions Compared

Version Old Version 8 New Version 9
Changes made by

MS

MS

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. The platform reads OVA files such as those created with VMware . and from the VM marketplace

  2. The file name must end in have the extension .ova.  extension

  3. You can upload a multi-disk template for a single VM (virtual system)

  4. The OVA file must contain an OVF description file for the template. 

  5. The platform uses the Name tag in the VirtualSystem as the template name. If the Name is not set, the platform falls back to the ID. See OVF reference.  

Note

  • For very large files, it may be convenient to use another method of adding templates. For example, see Appliance manager template API upload and download

  • If you do not have any hypervisors, the platform will convert the template into ALL possible hypervisor formats. So before you add templates to your Catalogue, add one physical machine of each hypervisor type that you will require conversions for. This will reduce unnecessary use of the NFS repository space. For more details, see Modify VM template disks in the section on Manage VM template disk conversions.

...