To modify a VM template:
In private cloud datacenters, standard templates have disks that will deploy to the hypervisor datastore, in contrast to persistent templates that have disks on external storage volumes. This documentation describes standard templates.
A short name to identify the VM template. This will be the default name of a VM created from this template.
A description of the services and applications installed on the VM template
Logical grouping of VM templates to enable you to organize them
Enter the URL for the template's icon. This must be a URL with a public IP address, not localhost or 127.0.0.1. It may contain the IP address of the API server.
If you do not assign an icon, the platform will assign a default icon. Square icon images with a size of 128x128 pixels and a transparent background look best. The compatible image formats are PNG, JPG, and GIF.
If an administrator shares the template with other tenants, then all users will see this icon. If you change the icon of a template with instances, when you create the next instance, it will have the new icon
When you create a VM from the template, it will have this template CPU value
When you create a VM from the template, it will have this RAM memory size
|RAM units||MB or GB|
Min CPU and
In private cloud, the minimum value of CPU or RAM. If 0 or empty, then there is no constraint. You cannot set a minimum below the current template value. Changes apply to new VMs, not existing VMs
|Max CPU and|
In private cloud, maximum value of CPU or RAM. If 0 or empty, then there is no constraint. Changes apply to new VMs, not existing VMs
|Cores per socket||The number of cores per socket. The number of CPUs must be divisible by the number of cores per socket. The maximum value is 32|
Troubleshooting minimum and maximum CPU and RAM values
To change the boot order of a disk
To download a disk
To add a disk:
Select one of the options: Disk from local file, Disk from iso file, Empty disk or Template disk.
Enter the Details of the disk as described here.
Disk from local file
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 name||Click Select file and use your browser to choose the file to upload.|
|Require datastore tier||Select Datastore tier will be required when creating a virtual machine to ensure that the user will select a datastore tier|
|Controller type||Depending on the hypervisor, the platform supports IDE, SCSI, and on KVM, it also supports VIRTIO.|
|Controller||On ESXi you can enter a SCSI controller type. The default value is the lsilogic controller.|
|Name||Disk name in the platform|
|Bootable||Select this checkbox to indicate that this is a system disk that can be used to boot the VM|
Disk from ISO file
Click Select file and use your browser to choose the file to upload
|Datastore tier will be required while creating a virtual machine||Optionally 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|
|Name||Friendly name of the disk in the platform|
|Bootable||Select this checkbox to indicate that this is a system disk that can be used to boot the VM|
|Add an extra empty disk||If 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
Enter the Capacity (or size) of the deployed disk and the disk Controller type and for SCSI disks, the Controller information.
The deployed size of the hard disk and units
|Datastore tier||Only available for existing disks|
|Datastore tier will be required while creating a virtual machine||Optionally select. The user will require the privilege to manage hard disks in order to create a VM|
|Allocation type||Optional. Allocation type of the disk.|
The controller type of disk
Optional. On supported hypervisors (ESXi), to force the creation of a new controller of the same type as an existing one, assign a new bus value. Access ESXi to confirm bus values.
Optional. Select an existing an existing bus number or to create a new controller, specify a new bus number. The user requests a bus number but the platform will use the bus number assigned by ESXi. When there is more than one controller, to identify the controller and bus number, the platform displays the bus number as a suffix to the controller. Access ESXi to confirm bus numbers that are not displayed
The name of the hard disk
When you deploy the VM, the platform will create the empty disk on the hypervisor datastore.
Select a template from the Apps library and then select a disk from the template.
Abiquo will select the original disk, not the conversions. If you require other formats, generate conversions for these formats.
To manually launch conversions to template formats:
To restart a failed conversion:
To edit a disk:
The disk type of the template. If the type is incorrect or UNKNOWN, you cannot deploy a VM with the disk. See Disk Format Information.
The hard disk space that is required to deploy this disk. See Determining the size of a VM Disk File.
|Capacity units||MB, GB, or TB|
|File name||To download the disk, click Download beside the file name|
|Datastore tier||To set the storage service level of the template disk, select a Datastore tier. You can modify this value in a VM before you deploy it|
|Datastore tier will be required while creating a virtual machine||Optional. The user will require privileges to select a datastore tier in order to create a VM|
|Allocation type||The user with appropriate privileges can modify this value in a VM before they deploy it|
|Controller type||If you change the controller type your VM may not boot. The user can modify this value after they create a VM and before they deploy it.|
On ESXi for SCSI
|Name||Hard disk name|
|Bootable||Select this checkbox to indicate that this is a system disk that can boot the VM|
Delete a template disk
Before you begin, check that the template is not in use. A template is in use if it has deployed VMs or dependent instances.
To delete a template disk:
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.
The variables will be added automatically to new VMs. Users can edit the variables when configuring the VM. Users can then access variables in the guest, for example, in AWS, the variables are stored in the ~/vm-variables.rc file. Variables may be used by cloud-init.
To remove enterprise access to a template, remove the scope containing the enterprise.
To make a template private to the owner enterprise, unselect all scopes.
The Administrator can edit recommended hardware profiles and datastore tiers
|Enable only recommended HPs||Select this checkbox to allow the user to select from recommended hardware profiles only.|
|Hardware profiles - Recommended||Select the hardware profiles to recommend for this template. The platform will display these profiles in the selection list with "(Recommended)" beside them. Remember that the administrator must allow the user's tenant to access the hardware profiles.|
|Enable only recommended DS Tiers||In private cloud, select this checkbox to allow the user to select from recommended datastore tiers only.|
|Datastore tiers - Recommended||In private cloud, select the datastore tiers to recommend for this template. The platform will display these tiers in the selection list with "(Recommended)" beside them. Remember that the administrator must allow the user's tenant to access the datastore tiers.|
The Administrator can edit advanced template elements. These values can also be specified through the OVF and the API. See Extended OVF Support and Template Definition
|Guest setup||Select guest setup option of Cloud-init or Hypervisor tools.|
|Guest initial password||If Guest setup is selected, select this option to request an initial password|
|Cost code||Pricing cost code for this template. Requires the "Add a cost code in VM Template edition" privilege. See Pricing View|
Sets the VMware guest operating system type. Select from the pull-down list. For more details, see Guest operating system definition for VMware vSphere 5 and 6 and Extended OVF Support and Template Definition. This attribute also enables users to search for templates in public cloud (e.g. Ubuntu 64-bit template). To use the latest version of an operating system, select a generic type, e.g. WINDOWS, and do not enter the version.
OS version is used to:
See Guest operating system definition for VMware vSphere 5 and 6 and Extended OVF Support and Template Definition for further details.
Default user for a VM created from this template for SSH access.
|Password||Default password for the default User of a VM created from this template.|
|Enable hot add / reconfigure in VM||See separate section|
SYSTEM means that the platform created the template, for example, from an OVF file in the NFS repository.
Date and time when the template was created.
To allow users to reconfigure their VMs without powering off, set these values as described on the Advanced tab of the VM edit dialog.
Enable hot-add or
Supported providers only with supported guest operating systems.
Enable users to add CPUs in the platform while the VM is powered on
Enable users to add RAM in the platform while the VM is powered on
Enable users to remove SCSI disks from the boot sequence and add SCSI disks to the end of the boot sequence while the VM is powered on
|NICs hot-reconfigure||Enable users to add and remove NICs in the platform while the VM is powered on|
|Remote access hot-reconfigure||Enable users to reset remote access in the platform while the VM is powered on|