[
https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320405#comment-16320405
]
ASF GitHub Bot commented on CLOUDSTACK-4757:
--------------------------------------------
rhtyd commented on issue #2146: CLOUDSTACK-4757: Support OVA files with
multiple disks for templates
URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356568169
Manual QA:
test_deploy_vm_root_resize.py:
```
Test deploy virtual machine with root resize ... === TestName:
test_00_deploy_vm_root_resize | Status : SUCCESS ===
ok
Test proper failure to deploy virtual machine with rootdisksize of 0 ... ===
TestName: test_01_deploy_vm_root_resize | Status : SUCCESS ===
ok
Test proper failure to deploy virtual machine with rootdisksize less than
template size ... === TestName: test_02_deploy_vm_root_resize | Status :
SUCCESS ===
ok
Ran 3 tests in 120.118s
OK
```
test_deploy_vgpu_enabled_vm.py:
```
Test 3D GPU support ... === TestName: test_3d_gpu_support | Status : SUCCESS
===
ok
Test Deploy Virtual Machine ... SKIP: This test case is written specifically
for XenServer hypervisor
Ran 2 tests in 265.680s
OK (SKIP=1)
```
test_volumes.py:
```
Test Volume creation for all Disk Offerings (incl. custom) ... === TestName:
test_01_create_volume | Status : SUCCESS ===
ok
Attach a created Volume to a Running VM ... === TestName:
test_02_attach_volume | Status : SUCCESS ===
ok
Download a Volume attached to a VM ... === TestName:
test_03_download_attached_volume | Status : SUCCESS ===
ok
Delete a Volume attached to a VM ... === TestName:
test_04_delete_attached_volume | Status : SUCCESS ===
ok
Detach a Volume attached to a VM ... === TestName: test_05_detach_volume |
Status : SUCCESS ===
ok
Download a Volume unattached to an VM ... === TestName:
test_06_download_detached_volume | Status : SUCCESS ===
ok
Test resize (negative) non-existent volume ... SKIP: Resize Volume is
unsupported on VmWare and Hyper-V
Test resize a volume ... SKIP: Resize Volume is unsupported on VmWare and
Hyper-V
Delete a Volume unattached to an VM ... === TestName:
test_09_delete_detached_volume | Status : SUCCESS ===
ok
test_10_list_volumes (tests.smoke.test_volumes.TestVolumes) ... ===
TestName: test_10_list_volumes | Status : SUCCESS ===
ok
Ran 10 tests in 1336.573s
OK (SKIP=2)
```
test_ssvm.py:
```
Test List secondary storage VMs ... === TestName:
test_01_list_sec_storage_vm | Status : SUCCESS ===
ok
Test List console proxy VMs ... === TestName: test_02_list_cpvm_vm | Status
: SUCCESS ===
ok
Test SSVM Internals ... === TestName: test_03_ssvm_internals | Status :
SUCCESS ===
ok
Test CPVM Internals ... === TestName: test_04_cpvm_internals | Status :
SUCCESS ===
ok
Test stop SSVM ... === TestName: test_05_stop_ssvm | Status : SUCCESS ===
ok
Test stop CPVM ... === TestName: test_06_stop_cpvm | Status : SUCCESS ===
ok
Test reboot SSVM ... === TestName: test_07_reboot_ssvm | Status : SUCCESS ===
ok
Test reboot CPVM ... === TestName: test_08_reboot_cpvm | Status : SUCCESS ===
ok
Test destroy SSVM ... === TestName: test_09_destroy_ssvm | Status : SUCCESS
===
ok
Test destroy CPVM ... === TestName: test_10_destroy_cpvm | Status : SUCCESS
===
ok
Test NFS Version on Secondary Storage mounted properly on SSVM ... SKIP: No
NFS version provided in test data
Ran 11 tests in 456.800s
OK (SKIP=1)
```
test_templates.py (previously failed at skipping tests, now skips without
error)
```
Register a template using Direct Download flag ... SKIP: Skipping test
because unsupported hypervisor vmware
Deploy a VM from a Direct Download registered template ... SKIP: Skipping
test because unsupported hypervisor vmware
Deploy a VM from a Direct Download registered template with wrong checksum
... SKIP: Skipping test because unsupported hypervisor vmware
Ran 3 tests in 0.008s
OK (SKIP=3)
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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: 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)
