Abiquo 5.1

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 55 Next »

Upload Templates from the Local Filesystem

To make new VM templates available in the platform, add them to your Apps library (also called the Appliance library). 

In private cloud 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:

  • For very large files, it may be convenient to use another method of adding templates
  • 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, check that there is 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.

OVAThe platform reads OVA files such as those created with VMware. The file name 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, the platform falls back to the ID. See OVF Reference.  
Local file

Check for a compatible format of the template disk. You will need to enter 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.

ISO file

You will need to enter the number of CPUs and RAM for the VM. You can also specify the size of an empty disk that the platform will create, for example, to install software
(error) If you mount an ISO as an IDE drive, you cannot make changes to the drive in the platform
(warning) In order to be able to remove an ISO drive after you use it, you must specify that an empty disk is required. Users can change the size of the disk before they deploy a VM

To add a new template:

  1. Go to Apps library
  2. Select the datacenter and click the add button
  3. 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 File name. Click Save. Abiquo will upload the file and create the template.
  3. When the template has been uploaded, Abiquo will open the Edit template dialog. Check the template details and click Save.

 Click here to expand...

Upload from local or ISO file

Complete this form to create a new VM template in the appliance library.




A short name to identify the VM template.


A description of the services and applications installed on the VM template


A logical group for organizing the templates. There is a default category ('Other') that cannot be deleted. See Manage VM Templates#OrganizeVMtemplatesintocategories.


Number of CPUs to assign to this template. It is important to enter a correct value, or a sensible best-guess value because you can edit the template later


RAM assigned for this template in MB, GB, or TB. It is important to enter a correct value, or a sensible best-guess value because you can edit the template later

Cores per socketMust be a divisor of CPUs


Enter the URL for the template's icon in PNG, JPG or GIF format. It must be a complete URL with an IP address that is not localhost or It may be a URL on the platform server. Recommendation: use square images with a size of 128x128 pixels. A transparent background looks nice. If the template is shared, the same icon will display for all users.

Disk from local file

When you upload a disk you can enter these disk options.




The disk Type of the Template. You must enter the correct type (not Unknown) to be able to use the template in the platform. See Disk Format Information. The V2V conversion process will generate the different conversions for each hypervisor installed or for all hypervisors if you have not added any hypervisors yet.


The hard disk size required for the deployed disk in MB, GB, or TB. It is important to enter a correct value. See Determine the size of a VM Disk File. This is a required field.

File nameClick Select file and use your browser to choose the file to upload.
Require datastore tierSelect Datastore tier will be required when creating a virtual machine to ensure that the user will select a datastore tier
Controller type

Select a controller type. Depending on the hypervisor, the platform supports: IDE, SCSI, SATA (ESXi), and VIRTIO (KVM)

ControllerOn ESXi you can enter a SCSI controller type. The default value is the lsilogic controller.
NameDisk Name in the platform
BootableSelect this checkbox to indicate that this is a system disk that can be used to boot the VM

Capacity of the Hard Disk

The Capacity is the deployed size of the hard disk. It is used to create the disk when you deploy your VM. With an incorrect value, your deploy may fail with a message such as "is not a virtual disk". For fixed formats, the capacity is the same as the physical size of the template disk, and for sparse formats and compressed formats, such as stream-optimized, it is the provisioning size.

Disk from ISO file






File name

Click Select file and use your browser to choose the file to upload

Datastore tier will be required while creating a virtual machineOptionally select this checkbox to require the user to select a datastore tier. To create a VM, the user will require the privilege to Manage virtual machine hard disks
NameFriendly name of the disk in the platform
BootableSelect this checkbox to indicate that this is a system disk that can be used to boot the VM
Add an extra empty diskIf you enter a disk size, the platform will create this hard disk and use it to install the ISO.
To be able to remove the ISO from the VM, you must specify this disk for the template. Users can change the size of the disk before they deploy a VM

Disks tab

The disk you upload is saved as disk 0 in the boot sequence. Abiquo will send this disk to the hypervisor as the boot disk. If your disk is not a bootable system disk, then move the disk to a different position in the boot sequence when you add a bootable system disk.

You can edit the uploaded disk but you cannot delete it before you save the template.

You cannot resize the primary disk before you deploy the VM.

Variables tab

To add variables to a VM template, enter the Key and Value, then click Add

To edit an existing value, click the pencil icon, enter the new Value, then click ok. To save your changes to the template, click Save.

The variables will be added automatically to new VMs. Users can edit the variables when configuring the VM.

Advanced tab



Operating System

For VMware, select a value to set the VMware guest operating system type for the platform. The platform also uses this value to display an icon, which you can customize.
See Guest operating system definition for VMware and Extended OVF Support and Template Definition for further details.

OS version

For VMware, enter an OS version, which can be an OS not included in the above list of codes. If you do not enter a value, the latest version supported by the hypervisor is used.

See Guest operating system definition for VMware and Extended OVF Support and Template Definition for further details. 


Default user for a VM created from this template to access a deployed machine using SSH.


Default password for a VM created from this template

NIC driver

The platform always supports E1000 drivers. On ESXi and vCloud, Abiquo also supports PCNet32 and VMXNET3. On KVM, Abiquo also supports VIRTIO drivers

Click Save to upload the template file. 

After you save the template, you can edit the template and add more disks, edit, reorder and delete disks. You can also add a cost code.

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#Manual Upload.

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. 

In private cloud, to create VM templates from a remote repository, do these steps:

Privilege: Download template from remote repository

  1. Select a Repository → select a Category or All categories. 
    The Packages pane will display the available template definitions with an icon, title and brief description
  2. Optionally, click on Show disks
  3. For each VM template to download, select the checkbox next to the template definition
  4. To start the download, click the Download button at the top of the dialog
    1. The platform will check that this template download will not exceed the repository limits for your enterprise or your enterprise in the datacenter.
    2. A status bar will appear next to the selected packages showing the download state.

If a template belongs to a Category in the remote template repository but the Category does not exist in the Apps library, the platform will create it for the download.

 Click here to show/hide the screenshot

Screenshot: Create template from remote template repository

You can now work with the new VM template.

Add public cloud templates to the Apps library

To import a template from a public cloud region into the platform's template cache, do the following steps:

  1. Go to Apps library → Public → select the public cloud region
  2. Then click the Import template button at the bottom of the screen
  3. The Import template popup will open

  4. Enter the search criteria for your template.

    1. In the ID field, this can be an ID, such as an AMI ID, or in the Name field it can be text to search for in the name 
    2. Private templates are images that are only available to your user account in the public cloud provider. In vCloud Director this option displays templates in the same organization as your user

    Then click Search to perform the search. The search can take some time and return several pages of templates

  5. To import a template, click the import symbol in the top right-hand corner of the template

    1. If your Azure template has terms of use, then you will need to accept these now or when you first create a VM from the template. 
      1. Accepting the terms of use requires the privilege to Manage virtual machine template terms of use and it enables programmatic deployment of the template for your Azure subscription. If you then disable programmatic deployment in the portal but you would like to deploy the template, you will need to delete it from the platform and import it again.
      2. If you share the template with another enterprise, then a user of that enterprise will need to accept the terms of use before they can create a VM

    When a template has been imported, the color of the import symbol will change to gray

  6. When you have finished importing templates click Close

Download templates from the Docker registry

 Click here to show/hide Docker information

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

Pages related to VM templates 

  • No labels