[jira] [Updated] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates

2018-01-10 Thread Rohit Yadav (JIRA)

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

Rohit Yadav updated CLOUDSTACK-4757:

Fix Version/s: (was: Future)
   4.11.0.0

> Support OVA files with multiple disks for templates
> ---
>
> 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
>Reporter: Likitha Shetty
>Assignee: Nicolas Vazquez
>Priority: Minor
> Fix For: 4.11.0.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.4.14#64029)


[jira] [Updated] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates

2017-09-26 Thread JIRA

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

Rafael Weingärtner updated CLOUDSTACK-4757:
---
Affects Version/s: (was: 4.3.0)
 Priority: Minor  (was: Major)

> Support OVA files with multiple disks for templates
> ---
>
> 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
>Reporter: Likitha Shetty
>Priority: Minor
> Fix For: Future
>
>
> 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.4.14#64029)


[jira] [Updated] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates

2014-06-07 Thread Likitha Shetty (JIRA)

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

Likitha Shetty updated CLOUDSTACK-4757:
---

Fix Version/s: (was: 4.4.0)
   4.5.0

 Support OVA files with multiple disks for templates
 ---

 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.5.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)


[jira] [Updated] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates

2014-05-02 Thread Likitha Shetty (JIRA)

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

Likitha Shetty updated CLOUDSTACK-4757:
---

Summary: Support OVA files with multiple disks for templates  (was: 
[VMware] Support OVA files with multiple disks for templates and uploaded 
volumes)

 Support OVA files with multiple disks for templates
 ---

 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)