Extended OVF support and template definition
- MS (Unlicensed)
Introduction to extended OVF support and template definition
The Abiquo template definition and OVF support include the optional parameters that are summarized in the following table.
OVF: see OVF reference for detailed OVF information
API: see TemplateDefinitionsResource and VirtualMachineTemplatesResource
UI: see Modify a VM template
Abiquo API parameter | Section of .ovf file | OVF format | Description | Default |
|---|---|---|---|---|
loginUser | Product section | Property with ovf:key="user" | To access a deployed VM using SSH. | null |
loginPassword | Product section | Property with ovf:key="password" | To access a deployed VM using SSH. Remember to change the password immediately after your first login. | null |
osType | OperatingSystemSection | 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 required to deploy VMs. Abiquo uses it to:
You can also set it using the UI and API. | UNRECOGNIZED |
osVersion | OperatingSystemSection | Free text field. Used to set VMware virtual machine guest OS. "ovf:version="<Version No or Text>" | You can use the osVersion field to:
Abiquo uses the OVF value directly as the osVersion in the VM template. | null |
ethernetDriverType | RASD items | RASD item code is 10 for ethernet driver | Abiquo always supports E1000 drivers. On ESXi, Abiquo also supports PCNet32 and VMXNET3. 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. | Abiquo uses it to set VMware SCSI disk controller type. Abiquo uses the OVF value to set the diskController in the VM template. | On VMware Abiquo creates selected SCSI controller or default |
Example OVF parameters in template definition format
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 VM 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.
Disk controller
In Abiquo on VMware, the platform default SCSI controller for guest systems is VirtualLsiLogicController.
To change the system default SCSI controller:
Set the following property in the abiquo.properties file on the Remote Services server. For more details, see Abiquo configuration properties#esxi.
abiquo.esxi.scsicontroller
To set a disk controller for a VM template in the OVF file and override the defaults:
Create a RASD section in your OVF file for a SCSI controller with ResourceType with a value of 6. This will use the default VirtualLsiLogicController
<rasd:ResourceType>6</rasd:ResourceType> Add a ResourceSubType free text field to specify the controller type.
For example, for a VirtualLsiLogicSASController as found in Windows 2012:
<rasd:ResourceSubType>lsilogicsas</rasd:ResourceSubType>You can use the following values:
SCSI disk controller type field text | diskController saved in template and created on VMware |
|---|---|
contains "paravirtual" | ParaVirtualSCSIController |
contains "bus" | VirtualBusLogicController |
contains "sas" | VirtualLsiLogicSASController |
other (default value) | VirtualLsiLogicController |
To set a disk controller for a VM template, see Modify a VM template.
To set a disk controller for a VM, see Modify VM hard disks and Modify VM volumes
Guest operating system definition
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 VM 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 VM template after you deploy a VM, the changes will not be made to the VM.
In general, if you do not supply an osVersion, Abiquo will use the latest version of the VMware guest operating system.
See Modify a VM template and Set the guest operating system for VMware
What if my operating system is not supported?
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.
Copyright © 2006-2024, Abiquo Holdings SL. All rights reserved