Chip, In Cloudstack, for Xen and KVM hypervisors since the files used for templates and volumes are virtual disks (VHD, QCOW2) the current CS assumption of template and volumes containing a single virtual disk seems fine. But since for VMware the files used for templates and volumes are in OVA format which is an archive that can contain multiple VMDKs this improvement seems appropriate only for VMware? Thanks, Likitha
>-----Original Message----- >From: Chip Childers [mailto:chip.child...@sungard.com] >Sent: Monday, September 30, 2013 7:42 PM >To: dev@cloudstack.apache.org >Subject: Re: [PROPOSAL] Support OVA files with multiple disks for templates and >uploaded volumes in VMWare > >On Mon, Sep 30, 2013 at 05:54:55AM +0000, Likitha Shetty wrote: >> Hi, >> >> 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 templates and uploaded volumes. For e.g. 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, volumes should be created based on other VMDK >disks in the OVA file and should be attached to the instance. >> > >+1, but question. Why VMware only? > >> I will soon propose a Functional Spec for this improvement. >> >> The corresponding JIRA ticket can be found at >https://issues.apache.org/jira/browse/CLOUDSTACK-4757 . >> >> Thanks, >> Likitha >>
