Documentation

Skip to end of metadata
Go to start of metadata

To modify a virtual machine template, select the template and click on the control menu button in the top-right corner and select Edit.

Datacenter templates

The virtual machine template fields you can modify are described in the table below.

Standard templates

The Edit template dialog has the following:

  • General Information
  • Disks
  • Variables
  • Advanced

General information tab

The General information tab contains the basic template details.

 

Field

Value

Name

A short name to identify the virtual machine template. If the template is Chef enabled, the name should indicate this

Description

A description of the services and applications installed on the virtual machine template

Category

Logical grouping of virtual machine templates to enable you to organize them. "Others" is a default category which cannot be deleted

CPU

Number of CPUs assigned to this template

RAM

RAM memory size assigned for this template in MB or GB

Min CPU

 

v3.8.5+. Minimum CPU. If 0 or empty, then there is no constraint. The platform stores 0 as an empty value, so if you enter "0", it will disappear! You cannot set a minimum below the current template value. Changes apply to new VMs, they are not retroactive. However, if users edit existing VMs that already had out-of-range values, the platform displays a warning but does not enforce the range

Min RAM

v3.8.5+. Minimum RAM. If 0 or empty, then there is no constraint. The platform stores 0 as an empty value, so if you enter "0", it will disappear! You cannot set a minimum below the current template value. Changes apply to new VMs, they are not retroactive. However, if users edit existing VMs that already had out-of-range values, the platform displays a warning but does not enforce the range

Max CPU

v3.8.5+. Maximum CPU. If 0 or empty, then there is no constraint. The platform stores 0 as an empty value, so if you enter "0", it will disappear! Changes apply to new VMs, they are not retroactive. However, if users edit existing VMs that already had out-of-range values, the platform displays a warning but does not enforce the range

Max RAMv3.8.5+. Maximum RAM. If 0 or empty, then there is no constraint. The platform stores 0 as an empty value, so if you enter "0", it will disappear! Changes apply to new VMs, they are not retroactive. However, if users edit existing VMs that already had out-of-range values, the platform displays a warning but does not enforce the range

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 be the URL of the Abiquo Server. A default icon is assigned if the template does not have one. See Abqiuo VM Template Guide and How to Manage VM Templates and Icons in Abiquo

Shared Template

If you have the Administer all enterprises privilege, tick this checkbox to allow all enterprises to use this virtual machine template. In Appliance Library view, shared templates are marked with the orange user icon. Shared Chef-enabled virtual machine templates will be available to all enterprises.

Disks tab

The Disks tab contains details of disks and SCSI/IDE information. It shows the disks currently attached to the machine and enables the user to edit and add new disks, as well as download disks to their local file system, depending on the user's privileges. 


Disks table 

Field

Value

Sequence

The boot order of the disk. You can edit the disk sequence by clicking the pencil icon near the sequence number. There must always be a boot disk in the 0 position, and the boot disk cannot be an empty disk.

Type

Local file

Path

The relative path and filename on the NFS repository filesystem. You cannot edit this value

File sizeSize of the disk file on the disk
Capacity

Size of the deployed disk

State

Template disk state can be DONE, IN PROGRESS, ERROR or FAILED. See Template Disk States

Download symbolClick to download the template disk. Not applicable to empty disks
Disk Conversions

Abiquo should convert all of your templates to all of the available hypervisor formats. If no hypervisors have been added, Abiquo will convert to ALL possible hypervisor formats. 

To display the conversions for a disk, select that disk in the Disks table.

For each conversion, Abiquo will list the following details:

Field

Value

Target format

The format your disk has been converted into. See Template Compatibility Table

State

Conversion state can be ENQUEUED, FINISHED, FAILED. Abiquo will mark as Failed any template conversion disks that are missing in the NFS Repository. For example, if you delete a conversion disk from the filesystem.

Date

Time stamp of when the conversion was completed

Action

If a conversion Failed, the link to Restart conversion will be available. Click Restart conversion to launch the conversion again

If the expected conversions are not shown, you can Generate missing conversions. Click Generate missing conversions to launch conversions to new template formats if you have added any new hypervisor types after the initial conversion process ended. See V2V Conversion.

Add a disk to a template

To add a disk to a template, click the + button in the top right of the disk dialog and select one of the options: Disk from local file, Disk from iso file, Empty disk or Template disk.


 

Disk from local file

Enter the details of the local file.

When you upload a disk you can enter these disk options.

 

Field

Value

Type

The disk type of the template. You must enter the correct type (not Unknown) to be able to use the template in Abiquo. 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.

Capacity

Hard disk size required for this template in MB, GB or TB. It is important to enter a correct value. See Determining the size of a VM Disk File. This is a required field.

File nameClick Select file and use your browser to choose the file to upload.
Controller typeDepending on the hypervisor, Abiquo supports IDE, SCSI and VIRTIO. Abiquo supports VIRTIO drivers on KVM only. As a default value, Abiquo checks a property or uses the Abiquo default (SCSI except ESXi)
ControllerOn ESX you can enter a disk controller type as described in the the table below. The default value is the lsilogic controller.
NameDisk name in Abiquo
BootableIf selected, indicates that this is a system disk that can be used to boot the virtual machine

Disk from ISO file

Enter the details of the local ISO file.

 

Field

Value

Type

ISO

File name

Click Select file and use your browser to choose the file to upload

BootableIf selected, indicates that this is a system disk that can be used to boot the virtual machine
Create extra empty diskIf you enter a disk size, Abiquo will create this hard disk and use it to install the ISO

Empty disk

To add an empty disk to a virtual machine template, enter the size of the disk and the disk controller type and controller information.

Abiquo will store the disk definition in the template and when you deploy a virtual machine based on this template, Abiquo will create the disk on the hypervisor datastore.


Template disk

To add a template disk to a virtual machine template, 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. 

Edit a template disk

When you edit a disk you can modify the following values

Field

Value

Type

The disk type of the template. You must enter the correct type (not Unknown) to be able to use the template in Abiquo. 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.

Capacity

Hard disk size required for this template in MB, GB or TB. It is important to enter a correct value. See Determining the size of a VM Disk File. This is a required field.

File nameCannot be modified. Click Download to download the virtual disk file
Datastore tierSet the storage service level for the template disk by selecting a datastore tier. The user can modify this value after a virtual machine is created and before it is deployed. Click the x to remove the datastore tier for the template disk
Controller typeIf you change the controller type your virtual machine may not boot. The user can modify this value after a virtual machine is created and before it is deployed. If the disk controller type is empty, Abiquo will use the disk controller from the hypervisor, which is IDE on ESXi and KVM. Click the x to remove the controller type for the template disk
Controller

On ESXi

  • You can select multiple controllers on a virtual machine and the controller can be changed, even after deploy
  • If no value is entered, the platform will use the default value of lsilogic or the value set by the system administrator
NameTemplate name in Abiquo
BootableIf selected, indicates that this is a system disk that can be used to boot the virtual machine


ESXi disk controller table

On ESXi, the values entered in the Controller field are interpreted according to the following table.

ResourceSubType value
diskController saved in template and created on VMware
contains "paravirtual"ParaVirtualSCSIController
contains "bus"VirtualBusLogicController
contains "sas"VirtualLsiLogicSASController
other (default value)VirtualLsiLogicController
Delete a template disk

To delete a template disk, click the delete icon.

Cannot delete disks in templates that are in use

You cannot delete a disk of a template that is in use. A template is in use if it has deployed virtual machines or dependent instances.

Variables tab

To add variables to a virtual machine 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 virtual machines. Users can edit the variables when configuring the virtual machine.


Advanced tab

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

Field

Value

Chef Enabled

Tick this checkbox to mark a Chef-enabled template. In private cloud this means that the Abiquo Chef Agent is installed on the template. In Appliance Library view, a small version of the Chef logo will be superimposed on a Chef-enabled template

Cost codePricing cost code for this template. See Pricing View
Operating system

Sets the VMware guest operating system type. Select from the pull-down list. See Examples of Operating system and OS version below (and Extended OVF Support and Template Definition) for further details. This element offers compatibility with the jclouds compute service implementation, to enable users to search for templates (e.g. Ubuntu 64-bit template).

Os Version

OS version is used to:

  • add operating systems not included in the list of codes
  • provide details of operating systems
  • set the VMware guest operating system type

See Operating system and OS version below (and Extended OVF Support and Template Definition) for further details. 

User

Default user for a virtual machine created from this template for ssh access. Enter a valid user name for this template. Users should change their password immediately after first login.

PasswordDefault password for the default User of a virtual machine created from this template. Enter a valid user password. Users should change their password immediately after first login.

NIC driver

  • Abiquo always supports E1000 drivers
  • On ESXi, Abiquo also supports PCNet32 and VMXNET3
  • From version 3.2.1 on KVM, Abiquo supports VIRTIO drivers
Enable hot-add/reconfigure in VM

Supported hypervisors only on supported guest operating systems.
See VMware documentation: https://www.vmware.com/resources/compatibility/search.php?deviceCategory=software

After you hot-add or hot-reconfigure, remember to update your guest system as required

CPU hot-add

Abiquo 3.8: Enable users to hot add CPUs in the hypervisor
Abiquo 3.8.1+: Enable users to add CPUs in the platform while the VM is powered on

RAM hot-add

Abiquo 3.8: Enable users to hot add RAM directly in the hypervisor
Abiquo 3.8.1+: Enable users to add RAM in the platform while the VM is powered on

Disks hot-reconfigure

Abiquo 3.8.1+: 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

  • IDE disks are not supported
  • Abiquo 3.8.1 will save other changes to the boot sequence but it will not implement them in the hypervisor. To implement these changes, power off the virtual machine and make another configuration change that will trigger a reconfigure
NICs hot-reconfigureAbiquo 3.8.1+: Enable users to modify NICs in the platform while the VM is powered on
Remote access hot-reconfigureAbiquo 3.8.1+: Enable users to reset remote access in the platform while the VM is powered on

Creation user

SYSTEM - the template was generated by Abiquo from an OVF file in the NFS repository. You cannot edit this value. When you select a template to create a virtual machine, this value will display for each instance in the list of instances for that template to help you select the appropriate instance.

Creation date

Date and time when the template was created. You cannot edit this value. When you select a template to create a virtual machine, this value will display for each instance in the list of instances for that template to help you select the appropriate instance.

Operating system and OS version

The following table gives Operating system and OS version values. If you select a generic operating system type, Abiquo will use the latest version of the same type. For example, if you select WINDOWS, Abiquo will deploy the template with windows8Guest. 

 Click here to show/hide the Operating System table

Abiquo Operating system / osType

Abiquo OS version / osVersion

vSphere GuestOsIdentifier
vSphere 5.0+

vSphere GuestOsIdentifier
vSphere 5.5+
vSphere GuestOsIdentifier
vSphere 6.0
Select this value in the UI or enter with APIEnter this version To deploy with this guest OS
in ESX 5.X
To deploy with this guest OS
in ESX 5.5+
To deploy with this guest OS
in ESX 6.X

MACOS

("10.6" & "64")

darwin10_64Guest

  

MACOS

("10.6")

darwin10Guest

  

MACOS

("10.7" & "64")

darwin11_64Guest

  

MACOS

("10.7")

darwin11Guest

  

MACOS

("64")

darwin64Guest

  

MACOS

 

darwinGuest

  
MACOSstarts with "12" darwin12_64Guest 
MACOSstarts with "13" darwin13_64Guest 
MACOSstarts with "14"   darwin14_64Guest

SOLARIS

starts with "6"

solaris6Guest

  

SOLARIS

starts with "7"

solaris7Guest

  

SOLARIS

starts with "8"

solaris8Guest

  

SOLARIS

starts with "9"

solaris9Guest

  

SOLARIS

starts with "10"

solaris10Guest

  

SOLARIS

("Sun Java Desktop System")

sjdsGuest

  

SOLARIS

 

solaris10Guest

  

SOLARIS_64

starts with "10"

solaris10_64Guest

  

SOLARIS_64

 

solaris11_64Guest

  

RHEL

starts with "2"

rhel2Guest

  

RHEL

starts with "3"

rhel3Guest

  

RHEL

starts with "4"

rhel4Guest

  

RHEL

starts with "5"

rhel5Guest

  

RHEL

starts with "6"

rhel6Guest

  

RHEL

 

redhatGuest

  

RHEL_64

starts with "3"

rhel3_64Guest

  

RHEL_64

starts with "4"

rhel4_64Guest

  

RHEL_64

starts with "5"

rhel5_64Guest

  

RHEL_64

 

rhel6_64Guest

  
RHELstarts with "7" ("64") rhel7_64Guest 
RHELstarts with "7" rhel7 

SUSE

("Open")

opensuseGuest

  

SUSE

 

suseGuest (warning)

  

SUSE_64

("Open")

opensuse64Guest (warning)

  

SUSE_64

 

suse64Guest

  

SLES

starts with "10"

sles10Guest

  

SLES

starts with "11"

sles11Guest

  

SLES

 

slesGuest

  

SLES_64

starts with "10"

sles10_64Guest

  

SLES_64

starts with "11"

sles11_64Guest

  

SLES_64

 

sles64Guest

  
SLESstarts with "12" ("64") sles12_64Guest 
SLESstarts with "12" sles12 

NOVELL_OES

 

oesGuest

  

NOVELL_OES

starts with "9"

nld9Guest

  

NOVELL_OES

("NetWare 4")

netware4Guest

  

NOVELL_OES

("NetWare 5")

netware5Guest

  

NOVELL_OES

("NetWare 6")

netware6Guest

  

MANDRIVA

 

mandrivaGuest

  

MANDRIVA_64

 

mandriva64Guest

  

TURBOLINUX

 

turboLinuxGuest

  

TURBOLINUX_64

 

turboLinux64Guest

  

UBUNTU

 

ubuntuGuest

  

UBUNTU_64

 

ubuntu64Guest

  

DEBIAN

starts with "4"

debian4Guest

  

DEBIAN

starts with "5"

debian5Guest

  

DEBIAN

 

debian6Guest

  
DEBIANstarts with "7" debian7 
DEBIANstarts with "8"  debian8

DEBIAN_64

starts with "4"

debian4_64Guest

  

DEBIAN_64

starts with "5"

debian5_64Guest

  

DEBIAN_64

 

debian6_64Guest

  
DEBIANstarts with "7" ("64") debian7_64Guest 
DEBIANstarts with "8" ("64")  debian8_64Guest

FREEBSD

 

freebsdGuest

  

FREEBSD_64

 

freebsd64Guest

  

WINDOWS_SERVER_2008

 

windows7Server64Guest

  

WINDOWS_SERVER_2008_64

 

windows7Server64Guest

  

WINDOWS_SERVER_2008_R2

 

windows7Server64Guest

  

WINDOWS_7

("Server")

windows7Server64Guest

  

WINDOWS_7

("64")

windows7_64Guest

  

WINDOWS_7

 

windows7Guest

  

WINDOWS_8

 

windows8Guest

  

WINDOWS (star)

 

windows8Guest

  

WINDOWS (star)

("64")

windows8_64Guest

  

WINDOWS_8_64

 

windows8Server64Guest

  

WINDOWS (star)

starts with "8" ("Server")

windows8Server64Guest

  
WINDOWS("Hyper") ("hyper") windowsHyperVGuest 
WINDOWSstarts with "9" or starts with "10" ("server") ("Server")  windows9Server64Guest
WINDOWSstarts with "9" or starts with "10" ("64")  windows9_64Guest
WINDOWSstarts with "9"  windows9

WINDOWS_SERVER_2003

("Web")

winNetWebGuest

  

WINDOWS_SERVER_2003

("Business")

winNetBusinessGuest

  

WINDOWS_SERVER_2003

("Enterprise")

winNetEnterpriseGuest

  

WINDOWS_SERVER_2003

("Datacenter")

winNetDatacenterGuest

  

WINDOWS_SERVER_2003

 

winNetStandardGuest

  

WINDOWS_SERVER_2003_64

("Enterprise")

winNetEnterprise64Guest

  

WINDOWS_SERVER_2003_64

("Datacenter")

winNetDatacenter64Guest

  

WINDOWS_SERVER_2003_64

 

winNetStandard64Guest

  

WINDOWS (star)

starts with "3.1"

win31Guest

  

WINDOWS (star)

starts with "95"

win95Guest

  

WINDOWS (star)

starts with "98"

win98Guest

  

WINDOWS (star)

("ME" OR "Millenium")

winMeGuest

  

WINDOWS (star)

starts with "NT"

winNTGuest

  

WINDOWS (star)

starts with "2000" ("Pro")

win2000ProGuest

  

WINDOWS (star)

starts with "2000" ("Avd")

win2000AdvServGuest

  

WINDOWS (star)

starts with "2000"

win2000ServGuest

  

WINDOWS (star)

starts with "XP" ("Home")

winXPHomeGuest

  

WINDOWS (star)

starts with "XP" ("64")

winXPPro64Guest

  

WINDOWS (star)

starts with "XP"

winXPProGuest

  

WINDOWS (star)

starts with "Longhorn" ("64")

winLonghorn64Guest

  

WINDOWS (star)

starts with "Longhorn"

winLonghornGuest

  

WINDOWS (star)

starts with "Vista" ("64")

winVista64Guest

  

WINDOWS (star)

starts with "Vista"

winVistaGuest

  

ESXI

starts with "4"

vmkernelGuest

  

ESXI

 

vmkernel5Guest

  

ESXI

starts with "6"

 

 vmkernel6Guest

LINUX_2_4

 

other24xLinuxGuest

  

LINUX_2_4_64

 

other24xLinux64Guest

  

LINUX_2_6

 

other26xLinuxGuest

  

LINUX_2_6_64

 

other26xLinux64Guest

  

LINUX

("Fedora")

fedoraGuest(warning)

  

LINUX

 

otherLinuxGuest

  

LINUX_64

("Fedora")

fedora64Guest (warning)

  

LINUX

 

otherLinux64Guest

  
LINUX("generic") genericLinuxGuest 
LINUX("3x") ("64") other3xLinuxGuest 
LINUX("3x") other3xLinux 
LINUX("core") ("Core")  coreos64Guest

CENTOS

 

centosGuest

  

CENTOS_64

 

centos64Guest

  

ORACLE_ENTERPRISE_LINUX

 

oracleLinuxGuest

  

ORACLE_ENTERPRISE_LINUX_64

 

oracleLinux64Guest

  

ECOMSTATION_32

starts with "1"

eComStationGuest

  

ECOMSTATION_32

 

eComStation2Guest

  

OTHER_64

 

otherGuest64

  

NETBSD, OPENBSD, NOT_APPLICABLE,
OTHER, UNRECOGNIZED

 

otherGuest

  

 

Key

New operating system types and versions in Abiquo 3.8.3:

 vSphere 5.5
 vSphere 6.0

(warning) = This operating might not be supported by all versions of VMware; please check the documentation for your version. If it is not available, a similar operating system will be used

(star) = Enter the Windows operating system without specifying the type to set the type to the latest version of Windows

Notes
  • Values are given in quotation marks. Enter these values without quotation marks
  • Ampersand (&) means that the osversion must contain both values to use this template 
    • e.g. OS type ID = 2, OS version = 10.6_64 will translate to darwin10_64Guest
  • An OR means that one value only is required 
    • e.g. OS type ID = 67, OS version = ME will translate to winMeGuest

Share VM templates

When editing a template, click Shared template to make this template available to all users.

Shared templates can be seen by all enterprises and are marked with the  shared template symbol.

Only users with the Administer all enterprises privilege can enable and manage shared templates. By default the only user with this privilege is the Cloud Admin.

Instances of virtual machines created with the shared template only belong to the enterprise that created them and are not automatically shared.

You cannot delete the shared template if there are any instances of the template, in your enterprise or other enterprises. 

You cannot make the shared template private if there are instances of the template in other enterprises.

If you make a shared template unavailable, when you refresh your Apps Library, it will be marked as unavailable in the Apps Library of all enterprises. In the time between when you make the template unavailable and when you refresh the Apps Library, users will not be able to deploy with the template, but it will not be marked as unavailable for users of other enterprises.

View hard disk size

Hard Disk Size Parameter Disabled

The Hard Disk size parameter has been disabled to prevent problems caused by changing the size of the hard disk. You can resize the system disk of a deployed virtual machine.

The Hard Disk size of the deployed virtual machine is determined by the physical size of the template disk after deployment, also called the provisioned size. However, the size is also recorded in the template's OVF description/definition. If these two sizes are not the same, deployment may fail with a message such as "is not a virtual disk". If you receive this type of error message, edit the Hard Disk in the OVF description and change it to match the physical size. See Determining the size of a Virtual Machine Disk File. for information on how to obtain the physical size.

Select and view cost code for VM template

If you have the Add a cost code in VM Template edition privilege, then you will be able to select a cost code for a VM template when editing the template on the Advanced tab. The cost code field only appears when editing, not when creating, the virtual machine template. Users without the privilege will not see the cost code field. The default value for the cost code field is "None". You can add a new cost code to the system in Pricing View, thus incorporating the template into a pricing model for an enterprise.

Generate missing conversions

Click Generate missing conversions to launch conversions to new template formats if you have added any new hypervisor types after the initial conversion process ended. See V2V Conversion.

Abiquo will mark as Failed any template conversion disks that are missing in the NFS Repository. For example, if you delete a conversion disk from the filesystem.

Click Restart conversion to launch one of these conversions again.

Template disk states

Template disks can be:

  • In progress
  • Done
  • Failed
  • Unavailable

The unavailable state means that the template definition is in the appliance library but the disk is not present in the NFS repository.

Template states

The possible template states are the same as the template disk states. The template states are determined from the states of the disks in the template. If any of the disks is in an error state (failed or unavailable), the template will also be in an error state. You can delete individual disks that are in an error state, but a template must always have one disk, even if it is in an error state. The priority of the disk state in determining the template state is as follows:

  • In progress
  • Failed
  • Unavailable
  • Done

For example, if a template has any failed disks, the template is also in the failed state, even if any of its other disks are unavailable or done.

Public cloud region

The fields you can modify are described in the table below.

General information


 

FieldValue
NameA short name to identify the virtual machine template. If the template is Chef enabled, the name should indicate this. Required field
DescriptionA description of the services and applications installed on the virtual machine template. Required field
CategorySelect a category to organize your templates of this type together. "Others" is a default category that cannot be deleted. You can manage categories in the main Apps Library view
IconEnter 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 be the URL of the Abiquo Server. A default icon is assigned if the template does not have one. See Abqiuo VM Template Guide and How to Manage VM Templates and Icons in Abiquo v2.x
Shared templateTick this checkbox to mark a Shared template. In the Apps library view, the shared template logo will appear on the template. The template will be visible to other enterprises.

Disks table


 

Field

Value

Sequence

The disk sequence number

Type

Defines the disk type of the template. You cannot edit this field. For public cloud templates the value is "Local file". See the template compatibility table for details

NameNot defined in public cloud
Provider IDTemplate ID in the public cloud provider
Controller typeNot defined in public cloud
TierNot defined in public cloud
File sizeNot defined in public cloud

Capacity

The size of the deployed disk

StateIn public cloud, the state of the disk is "DONE". When creating an instance from a VM in public cloud you may see the state "IN PROGRESS".

Variables

To add variables to a virtual machine 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 virtual machines. Users can edit the variables when configuring the virtual machine.

Advanced

 

FieldValue
Chef EnabledTick this checkbox to mark a Chef-enabled template. In Appliance Library view, a small version of the Chef logo will be superimposed on a Chef-enabled template. See AWS Chef
Cost codePricing cost code for this template. See #Select and view a cost code for a virtual machine template and Pricing View
Operating systemSets the VMware guest operating system type. Select from the pull-down list. See Examples of Operating system and OS version below and Extended OVF Support and Template Definition for further details. This element offers compatibility with the jclouds compute service implementation, to enable users to search for templates (e.g. Ubuntu 64-bit template).
Os VersionOS version is used to:
  • add operating systems not included in the list of codes
  • provide details of operating systems
  • set the VMware guest operating system type
See Operating system and OS version below and Extended OVF Support and Template Definition for further details. 
UserDefault user for a virtual machine created from this template for SSH access. Enter a valid user name for this template. Users should change their password immediately after first login.
PasswordDefault password for the default User of a virtual machine created from this template. Enter a valid user password. Users should change their password immediately after first login.
NIC driverIn public cloud you cannot set this value.
Hot add and hot reconfigureIn public cloud you cannot set these values.
Creation userIn AWS this is the user identifier. You cannot edit this value. When you select a template to create a virtual machine, this value will display for each instance in the list of instances for that template to help you select the appropriate instance.
Creation dateDate and time when the template was created. You cannot edit this value. When you select a template to create a virtual machine, this value will display for each instance in the list of instances for that template to help you select the appropriate instance.
Hardware profilesSelect the hardware profiles recommended for your users from the hardware profiles available in the public cloud provider and loaded into your system. See Control hardware profiles in public cloud

 

Recommend hardware profiles

To guide users to the most effective hardware profile for each template, select the recommended hardware profiles.

Abiquo uses information provided by AWS to predefine the recommended profiles for AWS templates (see http://aws.amazon.com/amazon-linux-ami/instance-type-matrix/). These values can then be edited.

This feature is independent of the feature that enables you to Modify an Amazon Virtual Machine Template

When a user deploys a virtual machine they can select from the pulldown list of hardware profiles which will now also highlight recommended profiles with “(recommended)”.

Share virtual machine templates

When editing a template, click Shared template to make this template available to all users.

Shared templates can be seen by all enterprises and are marked with the  shared template symbol.

Only users with the Administer all enterprises privilege can enable and manage shared templates. By default the only user with this privilege is the Cloud Admin.

Instances of virtual machines created with the shared template only belong to the enterprise that created them and are not automatically shared.

You cannot delete the shared template if there are any instances of the template, in your enterprise or other enterprises. 

You cannot make the shared template private if there are instances of the template in other enterprises.

If you make a shared template unavailable, when you refresh your Apps Library, it will be marked as unavailable in the Apps Library of all enterprises. In the time between when you make the template unavailable and when you refresh the Apps Library, users will not be able to deploy with the template, but it will not be marked as unavailable for users of other enterprises.

Select and view a cost code for a virtual machine template

If you have the Add a cost code in VM Template edition privilege, then you will be able to select a cost code for a VM template when editing the template. The cost code field only appears when editing, not when creating, the virtual machine template. Users without the privilege will not see the cost code field. The default value for the cost code field is "None". You can add a new cost code to the system in Pricing View, thus incorporating the template into a pricing model for an enterprise.