GUI Edit template General information
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 |
|
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 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 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 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
- 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
Copyright © 2006-2022, Abiquo Holdings SL. All rights reserved