To make new virtual machine templates available in Abiquo, you must add them into your appliance library. You can download templates from a remote template repository or upload from a local filesystem.
When you add a template to the appliance library, it will be converted to the format of each hypervisor in the platform. If you do not have any hypervisors in Abiquo, it will be converted to all possible hypervisor formats.
Before you add templates to your appliance library, add your physical machines with your hypervisors so as to optimize your NFS repository space. See V2V Conversion.
Click thebutton in the appliance library view to add a new template.
If you have the Manage repository privilege then you can download template definitions from a remote template repository to the Appliance Library.
Select the download from remote template repository option to open the following screen.
Select the datacenter in the first column on the left, then categories and template definitions available will be updated. After that, select a category or "all available categories" in the second row. The third row will show the template definitions available to be downloaded to your Datacenter for deployment. An icon, title and brief description is provided for each.
If a template belongs to a category in the remote template repository and the category does not exist in the appliance library, this new global category will be created when it is downloaded.
The user interface also provides some other operations on this screen.
Default repository space
When an enterprise repository is created, a default template repository is provided with this URL http://abiquo-repository.abiquo.com/ovfindex.xml
Abiquo 2.6 supports browser upload of files larger than 2 GB
You can upload a custom template with your own configuration of resources, disk file, etc. The Abiquo GUI upload works with a multi-part upload over an HTTP connection from your browser to the Apps Library.
You must enter the number of CPUs, RAM and Hard disk of the virtual machine. These fields are required and if you do not enter correct values, you may not be able to deploy. If you do not know these values, you can: upload the file to the TemplateRepository, which automatically detects the values, and then download it to Abiquo; or, determine an accurate value for the Hard disk, then enter best-guess values for # CPU and RAM (e.g. 1 x CPU and 512 MB of RAM). These values can be modified after the image is uploaded.
Complete this form to create a new virtual machine template in the appliance library.
* Hard Disk
You must enter a correct value for Hard Disk - see Determining the size of a VM Disk File. Otherwise, deployment may fail with a message such as "is not a virtual disk". The hard disk size of a deployed virtual machine is the physical size of the template disk for fixed formats, and the provisioning size for sparse formats and compressed formats, e.g. stream-optimized. The Hard disk size entered in this field is recorded in the template definition (a short version of an OVF description) and used to create the disk on deployment.
Click Next to upload the template file. Click Browse to look for the disk file on the local file system.
Abiquo will check that this template upload will not exceed the repository limits for your enterprise or your enterprise in the datacenter.
Downloading virtual machine templates
Downloading to client requires access to the Appliance Manager IP address configured for the current datacenter.
Incompatible Virtual Machine Templates
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#Manually Upload a VM Template to the NFS Repository
See the Abiquo VM Template Guide.