[jira] [Commented] (CLOUDSTACK-4757) [VMware] Support OVA files with multiple disks for templates and uploaded volumes

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931711#comment-13931711 ] 

ASF subversion and git services commented on CLOUDSTACK-4757:
-------------------------------------------------------------

Commit 99eb63ed854eea722b02dee68bb9d0bf5a892dc2 in cloudstack's branch refs/heads/ova-multiple-disks from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=99eb63e ]

CLOUDSTACK-4757 Support OVA with multiple volumes

Get bootdevice from extra config option in ova template.

Signed-off-by: Sateesh Chodapuneedi <sa...@apache.org>


> [VMware] Support OVA files with multiple disks for templates and uploaded volumes
> ---------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4757
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4757
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller
>    Affects Versions: 4.3.0
>            Reporter: Likitha Shetty
>            Assignee: Likitha Shetty
>             Fix For: 4.4.0
>
>
> CloudStack volumes and templates are one single virtual disk in case of XenServer/XCP and KVM hypervisors since the files used for templates and volumes are virtual disks (VHD, QCOW2). However, VMware volumes and templates are in OVA format, which are archives that can contain a complete VM including multiple VMDKs and other files such as ISOs. And currently, Cloudstack only supports Template creation based on OVA files containing a single disk. If a user creates a template from a OVA file containing more than 1 disk and launches an instance using this template, only the first disk is attached to the new instance and other disks are ignored.
> Similarly with uploaded volumes, attaching an uploaded volume that contains multiple disks to a VM will result in only one VMDK to being attached to the VM.
> This behavior needs to be improved in VMWare to support OVA files with multiple disks for both uploaded volumes and templates. i.e. If a user creates a template from a OVA file containing more than 1 disk and launches an instance using this template, the first disk should be attached to the new instance as the ROOT disk and volumes should be created based on other VMDK disks in the OVA file and should be attached to the instance.



--
This message was sent by Atlassian JIRA
(v6.2#6252)