Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 37 Next »



 

Upload VM Templates to Datacenter Apps Library

You can upload VM templates from a local filesystem in OVA format (multiple disks) or as a single disk.

Privilege: Upload virtual machine template


Before you begin:

  1. Check that your template disks are in a compatible format for the platform.
  2. Check that you have the template details ready to enter, or that your file meets the requirements, depending on your upload:
    1. Local file: number of CPUs, RAM and the Capacity, which is the deployed size of the VM hard disk. See Determine the size of a VM Disk File.
    2. ISO file: number of CPUs and RAM for the VM
    3. OVA file: Abiquo reads OVA files such as those created with VMware. The name of the OVA file must end in the extension ".ova". You can upload a multi-disk template for a single VM. The OVA file must contain an OVF description file for the template. The platform uses the Name tag in the VirtualSystem as the template name. If the Name is not set, Abiquo falls back to the ID. See OVF Reference.  
  3. You can upload a template with a multi-part upload over an HTTP connection from your browser to the Apps library. The platform supports browser upload of files larger than 2 GB but for very large files, it may be convenient to use another method.
  4. 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 Apps library, add one physical machine of each hypervisor type that you will require conversions for, in order to reduce unnecessary use of the NFS repository space. See V2V Conversion.

To add a new template:

  1. In the Apps library view, select the datacenter and click the add button
  2. Select one of the upload or download options and enter the appropriate data




Upload an OVA file

To upload an OVA file: 

  1. Select Create from OVA file, and select the file.
  2. Abiquo will display the filename. Click Save. Abiquo will upload the file and create the template.

When the template has been uploaded, Abiquo will open the Edit template dialog. From here the administrator can change template values or a share the template with other tenants. See Modify a VM Template. Check or edit the template details and click Save.

 Click here to expand...




Upload from local or ISO file

To create a template by uploading from the local filesystem, first enter template details. Then on the Disks tab, select the appropriate disk option.

* Capacity of the Hard Disk

You must enter a correct value for the Capacity of the hard disk, otherwise, your deploy may fail with a message such as "is not a virtual disk".


Unable to render {include} The included page could not be found.

Disk from local file

Unable to render {include} The included page could not be found.

Disk from ISO file

Unable to render {include} The included page could not be found.

Modify the template after you upload the disk

If your disk is not a bootable system disk, when you add a bootable system disk, move the disk to a different position in the boot sequence. You can edit the uploaded disk but you cannot delete it before you save the template.

After you upload the disk, you can edit the Variables and Advanced template options. See Modify a VM Template.

To share a template with another enterprise, see Modify a VM Template#ScopestabforsharingVMtemplates




Troubleshooting VM template uploads

The GUI upload process is handled by the browser and there are some limitations. If a file is not compatible with GUI upload, you can upload it manually. Manual upload requires access to the filesystem, so it should be done by a system administrator. See Importing Templates into the Appliance Library.

For more Information about VM Templates, see Virtual Machine Template Guide

Note that downloading templates to the client requires access to the Appliance Manager IP address configured for the current datacenter. 


Unable to render {include} The included page could not be found.




Download templates from the Docker registry


 Click here to show/hide Docker information

Unable to render {include} The included page could not be found.





Unable to render {include} The included page could not be found.




Pages related to VM templates 


  • No labels