cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Animesh Chaturvedi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-1872) Do not accept OVAs with multiple VMDKs for uploaded volumes or templates
Date Thu, 07 Nov 2013 22:23:18 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Animesh Chaturvedi updated CLOUDSTACK-1872:
-------------------------------------------

    Assignee:     (was: Venkata Siva Vijayendra Bhamidipati)

> Do not accept OVAs with multiple VMDKs for uploaded volumes or templates
> ------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1872
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1872
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, Template, VMware, Volumes
>    Affects Versions: 4.0.1
>            Reporter: Kirk Kosinski
>
> CloudStack volumes and templates are meant to be one single virtual disk. This is always
the case with KVM and XenServer/XCP since the files used for volumes and templates are virtual
disks (QCOW2, VHD). 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. 
> Currently, CloudStack will accept an OVA with an invalid configuration, extract it to
secondary storage, and allow end-users to use it. This can cause unintended behavior or possibly
failures when an end-user does try to use it. At the very least, it wastes space on secondary
and possibly primary storage. For example, here is a uploaded volume that contained two VMDKs
on secondary storage:
> # ll /mnt/secondary/volumes/12/
> total 332
> -rw-rw-rw- 1 root root 146944 Apr  1 16:38 3ab61094-8170-3139-a6b4-8edd2b4942ef.ova
> -rw-r--r-- 1 root root  68608 Apr  1 16:35 blankvm2-disk1.vmdk
> -rw-r--r-- 1 root root  68608 Apr  1 16:35 blankvm2-disk2.vmdk
> -rw-r--r-- 1 root root    200 Apr  1 16:35 blankvm2.mf
> -rw-r--r-- 1 root root   5930 Apr  1 16:35 blankvm2.ovf
> -rw-rw-rw- 1 root root    328 Apr  1 16:38 volume.properties
> Attaching this volume to a VM will result in both VMDKs being copied to primary storage,
but only one will be attached to the VM.
> CloudStack should verify whether or not an OVA contains a supported configuration, and
should give an error and reject the OVA if it is not supported. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message