Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.


Abiquo 5.0

Skip to end of metadata
Go to start of metadata

Before you begin:

  1. Log in or switch enterprises to the tenant that owns the template

To modify a VM template:

  1. Select the template and click on the control menu button in the top-right corner and select Edit

Privilege: Manage VM templates from Apps library

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.

Edit template

Basic template details


Field

Value

Name

A short name to identify the VM template. This will be the default name of a VM created from this template.

Description

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

Category

Logical grouping of VM templates to enable you to organize them

Icon

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

CPU and RAM values

When you are not using hardware profiles, you can set values for template CPU and RAM as follows

Field

Value

CPU

When you create a VM from the template, it will have this template CPU value

RAM

When you create a VM from the template, it will have this RAM memory size

RAM unitsMB or GB

Min CPU and
Min RAM

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
Max RAM 

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 socketThe 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

  • The platform stores 0 as an empty value, so if you enter "0", it will disappear!
  • If users edit existing VMs that already had out-of-range values, the platform displays a warning but does not enforce the range.
  • Changes can affect recommended hardware profiles on the Advanced tab, so you may need to review them
  • Users with the Override VM constraints privilege can enter values outside this range
 

  • No labels