The Abiquo template definition and OVF support include the optional parameters that are summarized in the following table.
Abiquo OVF support and the template definition are compatible with the jclouds Compute service. All of the jclouds providers use the operating system codes to enable users to search for a Windows template, or search for a Ubuntu 64 bit template, and so on.
|Abiquo API Parameter|
in Template Definition
|Section of .ovf file||OVF Format||Description||Default|
|loginUser||Product section||Property with ovf:key="user"||The user and password parameters enable you to access a deployed machine using ssh. This functionality is also available through jclouds. Abiquo recommends that you change the password immediately after your first login.||null|
|loginPassword||Product section||Property with ovf:key="password"||The user and password parameters enable you to access a deployed machine using ssh. This functionality is also available through jclouds. Abiquo recommends that you change the password immediately after your first login.||null|
OVF numeric code that represents the operating system type and number of bits. Used to set VMware virtual machine guest OS. ovf:id="<CIM_NO>"
The osType is used, as shown in the table below, to:
The osType can be edited in the UI and through the API. It offers compatibility with the jclouds compute service implementation, to enable users to search for templates (e.g. Ubuntu 64-bit template).
Free text field. Used to set VMware virtual machine guest OS. "ovf:version="<Version No or Text>"
The osVersion field can be used, as shown in the table below, to:
The OVF value is transferred directly to the osVersion in the VM template.
|ethernetDriverType||RASD items||RASD item code is 10 for ethernet driver||Abiquo always supports E1000 drivers. On ESXi, Abiquo also supports PCNet32 and VMXNET3. From version 3.2.1 on KVM, Abiquo also supports VIRTIO drivers.||Abiquo creates an E1000|
|diskControllerType||RASD items||RASD ResourceType item code is 5 for IDE controller and 6 for SCSI controller||Depending on the hypervisor, Abiquo supports IDE and SCSI. On KVM Abiquo supports VIRTIO drivers.||If the disk controller type is empty in the template, Abiquo will use the disk controller from the hypervisor, which is IDE on ESXi and KVM.|
|diskController||RASD items||RASD ResourceSubType free text field. Used to set VMware SCSI disk controller type. Introduced to support Windows 8 disk controllers||The OVF value is transferred to the diskController according to the table below.||On VMware Abiquo creates selected SCSI controller or default|
These parameters are accessible through the Abiquo API and UI. If you create a template definition using the API or include these parameters in .ovf files, Abiquo will incorporate them into the virtual machine template definition. This means that you can retrieve template definitions using the API and search for those of a particular type based on these fields. Note that the osType code in the .ovf file becomes the readable osType in the template definition.
You can set a default SCSI controller for all virtual machines in the abiquo.properties file. See Abiquo Configuration Properties#esxi. The default SCSI controller set in the abiquo.properties will be used if no SCSI controller is set in the virtual machine OVF, virtual machine template, or virtual machine configuration prior to first deploy. Users can change the SCSI controller in a virtual machine, even after deploy.
Abiquo will read a RASD section from the OVF. For example, the following section will support Windows 2012:
In general, Abiquo will determine that the resource type is a SCSI controller and create the standard SCSI controller.
ResourceType = 6 = Parallel_SCSI_HBA (from CIMResourceTypeEnum) -> diskControllerType = SCSI
The default controller is a VirtualLsiLogicController.
Now Abiquo will also read the ResourceSubType (free text field) from the OVF and save the corresponding diskController in the TemplateDefinition data model. Then Abiquo will add this information to the diskController optional attribute in the virtual machine template.
|ResourceSubType value||diskController saved in template and created on VMware|
|other (default value)||VirtualLsiLogicController|
You can also change the diskControllerType and diskController using the API and the UI for the virtual machine template and virtual machine.
Abiquo can create more than one diskController, but only one diskController of each kind. You can change a controller in a virtual machine, even after deploy.
All SCSI disks are attached to the diskController selected at deploy time based on the following priority:
1. a single value set in the virtual machine template for any of the virtual machine disks
2. for SCSI diskControllerType, the default diskController set in abiquo.properties
3. for SCSI diskControllerType, the platform predefined default of lsilogic
Abiquo reads the CIM OperatingSystem code in OVF files to create the template definition according to the conversion table.
For VMware ESXi, Abiquo also converts the Abiquo osType and osVersion to the vSphere GuestOSIdentifier.
This information is stored in the Abiquo template only, not the VM. Abiquo reads the template to create the VM but does not store the information in the VM definition itself. Therefore, if you change a template after you deploy a virtual machine, the changes will not be made to the virtual machine.
In general, if you do not supply an osVersion, Abiquo will use the latest version of the VMware guest operating system.
For example, for new versions of Windows, Abiquo supports a generic WINDOWS type. If you wish to use this type, complete the osVersion field with a full description.
if your template contains the standard DMTF description for the template, this will be stored in the osVersion field in the template definition.
If you select a generic template, Abiquo will use the latest type of the generic template.