This page describes how to edit a VM template in the public cloud catalogue.
To add VM templates from the provider or the local system to the catalogue, see Add VM templates to the catalogue
To modify VM templates in private cloud, see Modify a VM template
Before you begin:
Log in or switch enterprises to the tenant that owns the template
To modify a VM template:
Select the template and click on the control menu button in the top-right corner and select Edit
Privileges: Manage VM templates from Catalogue
Edit the general information of a template in public cloud
Enter the general details of the VM template:
Edit a Name to identify the template. The platform will assign this name to VMs that users create from this template. Check your cloud provider naming requirements!
Optionally, select a Category. The platform will display the templates to users by category
For the Icon, enter a URL with a public IP address, not localhost or 127.0.0.1. It may contain the IP address of the API server. For more details, see the template icons expanding section below.
If your cloud provider supports hardware profiles and CPU/RAM values to configure VMs, you can configure CPU and RAM for the template. For more details, see the private cloud documentation at Modify a VM template.
The Creation date is the timestamp of when you onboarded the template from the cloud provider.
Edit virtual machine template disk in public cloud
To edit VM template disk in public cloud providers:
The Capacity is the hard disk space to deploy this disk. Check your cloud provider's minimum capacity requirements for your operating system
When you import a VM template from Azure, the Capacity will be set to 0 and this means the platform will use the default size of the template in the provider
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
Edit VM template variables
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.
After the VM deploys, users can then access variables in the guest.
For example, AWS stores the variables in the ~/vm-variables.rc file. Cloud-init may use variables.
Scopes tab for sharing VM templates
To share a template with the enterprises in one or more scopes, select template scopes.
To remove enterprise access to a template, remove the scope containing the enterprise.
You cannot remove a scope from the template if an enterprise in the scope is using the template, for example, if it has deployed VMs or instances of VMs.
To make a template private to the owner enterprise, unselect all scopes.
Edit template advanced tab in public cloud
Field | Value |
---|---|
Guest setup | In public cloud, by default the Guest setup option is automatically set to Cloud-init even if you do not select this option. |
Guest initial password | For Windows, select Guest initial password to request an initial password that will be sent by email or SMS. |
Cost codes | The cost codes for extra charges for this template are now on a separate tab. See Add cost codes for extra charges for a VM template in Modify a VM template |
Operating system | Select the operating system type. To use the latest version of an operating system, select a generic type, e.g. WINDOWS, and do not enter the version. The platform uses the operating system to:
For more details of VMware guest operating system types, see Guest operating system definition for VMware and Extended OVF support and template definition. |
OS version | OS version is used to:
|
User | Default user for a VM created from this template for Linux SSH access and Windows RDP access
|
Password | Default password for the default User of a VM created from this template for Windows systems only |
NIC driver | Abiquo always supports E1000 drivers, and other drivers may be available depending on the cloud provider |
Enable UEFI boot | When selected, disable BIOS boot and enable UEFI boot.
For VMs, the uefiEnabled attribute is read-only and it is available via the API. |
Enable hot add / reconfigure in VM | See separate section
|
Creation user | SYSTEM means that the platform created the template |
Creation date | Date and time when the template was created. |
Enable hot add and hot reconfigure for VM templates
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 hot-reconfigure in VM is valid for supported providers only with supported guest operating systems.
Check that the Operating system and OS version are correctly set for your system.
Option | Description |
---|---|
CPU hot-add | Enable users to add CPUs in the platform while the VM is powered on |
RAM hot-add | Enable users to add RAM in the platform while the VM is powered on |
Disks hot-reconfigure | Enable users to remove disks from the boot sequence and add 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. Not used in public cloud |
Add cost codes for extra charges for a VM template
See “Add cost codes for extra charges for a VM template” in Modify a VM template.
Manage VM templates with the API
API Documentation
For the Abiquo API documentation of this feature, see Abiquo API Resources and the page for this resource VirtualMachineTemplatesResource.
Pages related to VM templates
Main page with links to related pages: Catalogue view