Page History

...

Datadisk templates will provide flexibility to orchestrate, deploy and manage additional disks present in an OVA like any other Datadisk in CloudStack.

Architecture

Work flow changes

Template registration

...

• Not supported for Datadisk Templates
• By default the Datadisk templates will be private and non-featured

CloudStack will check the OVA template being registered if there exists multiple disks in the container. This task is part of template registration itself. Unless the OVA has custom property "cloud.ova.bootdisk" set, the first disk in the OVA container is registered as vm template and remaining disks would be registered as data disk templates. The value of parameter “cloud.ova.bootdisk” should be in format ”<controllertype><controllerId>:<devicenumber_on_this_controller>” to VM before exporting that as OVA. Possible values for <controllertype> are "ide" or "scsi". Possible values for <controllerId> are 0, 1, 2, 3. Possible values for <devicenumber_on_this_controller> are 0 to 15. Ex: “cloud.ova.bootdisk”=”scsi0:2”. Custom property can be added to VM before creating OVA from the VM per VMware documentation http://pubs.vmware.com/vsphere-50/topic/com.vmware.vsphere.vm_admin.doc_50/GUID-88C8B72F-5753-4A2A-94B5-40EA1046C4D9.html

Change in the existing behavior

...