[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320571#comment-16320571 ] 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-356658740 Tests LGTM, merging this based on code reviews and test results. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320559#comment-16320559
]
ASF GitHub Bot commented on CLOUDSTACK-4757:
rhtyd commented on a change in pull request #2146: CLOUDSTACK-4757: Support OVA
files with multiple disks for templates
URL: https://github.com/apache/cloudstack/pull/2146#discussion_r160731088
##
File path: api/src/com/cloud/agent/api/storage/OVFHelper.java
##
@@ -0,0 +1,333 @@
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements. See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership. The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License. You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied. See the License for the
+// specific language governing permissions and limitations
+// under the License.
+package com.cloud.agent.api.storage;
+
+import java.io.File;
+import java.io.IOException;
+import java.io.PrintWriter;
+import java.io.StringWriter;
+import java.util.ArrayList;
+import java.util.List;
+
+import javax.xml.parsers.DocumentBuilderFactory;
+import javax.xml.parsers.ParserConfigurationException;
+import javax.xml.transform.Transformer;
+import javax.xml.transform.TransformerException;
+import javax.xml.transform.TransformerFactory;
+import javax.xml.transform.dom.DOMSource;
+import javax.xml.transform.stream.StreamResult;
+
+import org.apache.log4j.Logger;
+import org.w3c.dom.Document;
+import org.w3c.dom.Element;
+import org.w3c.dom.NodeList;
+import org.xml.sax.SAXException;
+
+import com.cloud.agent.api.to.DatadiskTO;
+import com.cloud.utils.exception.CloudRuntimeException;
+
+public class OVFHelper {
+private static final Logger s_logger = Logger.getLogger(OVFHelper.class);
+
+public List getOVFVolumeInfo(final String ovfFilePath) {
+if (ovfFilePath == null || ovfFilePath.isEmpty()) {
+return null;
+}
+ArrayList vf = new ArrayList();
+ArrayList vd = new ArrayList();
+
+File ovfFile = new File(ovfFilePath);
+try {
+final Document doc =
DocumentBuilderFactory.newInstance().newDocumentBuilder().parse(new
File(ovfFilePath));
+NodeList disks = doc.getElementsByTagName("Disk");
+NodeList files = doc.getElementsByTagName("File");
+NodeList items = doc.getElementsByTagName("Item");
+boolean toggle = true;
+for (int j = 0; j < files.getLength(); j++) {
+Element file = (Element)files.item(j);
+OVFFile of = new OVFFile();
+of._href = file.getAttribute("ovf:href");
+if (of._href.endsWith("vmdk") || of._href.endsWith("iso")) {
+s_logger.info("MDOVA getOVFVolumeInfo File href = " +
of._href);
+of._id = file.getAttribute("ovf:id");
+s_logger.info("MDOVA getOVFVolumeInfo File Id = " +
of._id);
+String size = file.getAttribute("ovf:size");
+if (size != null && !size.isEmpty()) {
+of._size = Long.parseLong(size);
+} else {
+String dataDiskPath = ovfFile.getParent() +
File.separator + of._href;
+File this_file = new File(dataDiskPath);
+of._size = this_file.length();
+}
+of._iso = of._href.endsWith("iso");
+if (toggle && !of._iso) {
+of._bootable = true;
+toggle = !toggle;
+}
+vf.add(of);
+}
+}
+for (int i = 0; i < disks.getLength(); i++) {
+Element disk = (Element)disks.item(i);
+OVFDisk od = new OVFDisk();
+String virtualSize = disk.getAttribute("ovf:capacity");
+if (virtualSize == null || virtualSize.isEmpty()) {
+od._capacity = 0L;
+} else {
+od._capacity = Long.parseLong(virtualSize);
+}
+String allocationUnits =
disk.getAttribute("ovf:capacityAllocationUnits");
+od._diskId = disk.getAttribute("ovf:diskId");
+s_logger.info("MDOVA getOVFVolumeInfo Disk ovf:diskId = " +
od._diskId);
+od._fileRef = disk.getAttribute("ovf:fileRef");
+
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320537#comment-16320537 ] 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 confirmed all failing tests pass now. test_vm_life_cycle.py: ``` Test migrate VM ... === TestName: test_08_migrate_vm | Status : SUCCESS === ok -- Ran 1 test in 429.193s OK ``` 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: us...@infra.apache.org > Support OVA files with multiple disks for templates > --- > > Key: CLOUDSTACK-4757 > URL:
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320454#comment-16320454 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356639535 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1639 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320422#comment-16320422 ] 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-356536693 Kicking packaging as master has changed, will re-run failed tests. @blueorangutan package 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320423#comment-16320423 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356536795 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320407#comment-16320407 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356591469 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1638 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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: us...@infra.apache.org > 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
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320186#comment-16320186 ] 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_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: us...@infra.apache.org > 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
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320173#comment-16320173 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356591469 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1638 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320169#comment-16320169 ] 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_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: us...@infra.apache.org > 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
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320152#comment-16320152 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356543503 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1637 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320146#comment-16320146 ] 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_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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320145#comment-16320145 ] 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_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 (failed at skipping tests) ``` 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320060#comment-16320060 ] 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_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) ``` 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319934#comment-16319934 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356543503 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1637 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319904#comment-16319904 ] 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-356536693 Kicking packaging as master has changed, will re-run failed tests. @blueorangutan package 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319905#comment-16319905 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356536795 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319614#comment-16319614 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356483559 Trillian test result (tid-2098) Environment: vmware-55u3 (x2), Advanced Networking with Mgmt server 7 Total time taken: 53879 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t2098-vmware-55u3.zip Intermitten failure detected: /marvin/tests/smoke/test_deploy_vgpu_enabled_vm.py Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_root_resize.py Intermitten failure detected: /marvin/tests/smoke/test_ssvm.py Intermitten failure detected: /marvin/tests/smoke/test_templates.py Intermitten failure detected: /marvin/tests/smoke/test_vm_life_cycle.py Smoke tests completed. 62 look OK, 5 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- test_3d_gpu_support | `Failure` | 459.60 | test_deploy_vgpu_enabled_vm.py test_00_deploy_vm_root_resize | `Error` | 0.22 | test_deploy_vm_root_resize.py test_05_stop_ssvm | `Error` | 1008.31 | test_ssvm.py test_08_reboot_cpvm | `Error` | 912.60 | test_ssvm.py ContextSuite context=TestCreateTemplateWithDirectDownload>:setup | `Error` | 5.26 | test_templates.py test_08_migrate_vm | `Error` | 42.75 | test_vm_life_cycle.py 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318200#comment-16318200 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356241633 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1634 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318148#comment-16318148 ] 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-355812751 @blueorangutan package 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318150#comment-16318150 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355812800 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318152#comment-16318152 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355814305 @rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been kicked to run smoke tests 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318151#comment-16318151 ] 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-355814287 @blueorangutan test centos7 vmware-55u3 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318155#comment-16318155 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356234565 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318149#comment-16318149 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355814247 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1611 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318154#comment-16318154 ] 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-356234536 @blueorangutan package 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318088#comment-16318088 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356223098 @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been kicked to run smoke tests 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318085#comment-16318085 ] ASF GitHub Bot commented on CLOUDSTACK-4757: borisstoyanov commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356222856 @blueorangutan test centos7 vmware-55u3 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318060#comment-16318060 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356219053 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1630 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317980#comment-16317980 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355910381 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317982#comment-16317982 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355916182 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1617 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317979#comment-16317979 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356205310 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317981#comment-16317981 ] 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-355910344 @blueorangutan package 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317978#comment-16317978 ] 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-356205253 @blueorangutan package 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317930#comment-16317930 ] 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-356205253 @blueorangutan package 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317931#comment-16317931 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-356205310 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315892#comment-16315892
]
ASF GitHub Bot commented on CLOUDSTACK-4757:
rhtyd commented on a change in pull request #2146: CLOUDSTACK-4757: Support OVA
files with multiple disks for templates
URL: https://github.com/apache/cloudstack/pull/2146#discussion_r160093366
##
File path:
engine/storage/image/src/org/apache/cloudstack/storage/image/TemplateServiceImpl.java
##
@@ -691,6 +723,151 @@ protected Void
createTemplateCallback(AsyncCallbackDispatcher dataDiskTemplates = new ArrayList();
+ImageStoreEntity tmpltStore =
(ImageStoreEntity)parentTemplate.getDataStore();
+dataDiskTemplates = tmpltStore.getDataDiskTemplates(parentTemplate);
+s_logger.error("MDOVA createDataDiskTemplates Found " +
dataDiskTemplates.size() + " Datadisk template(s) for template: " +
parentTemplate.getId());
+int diskCount = 0;
+VMTemplateVO templateVO =
_templateDao.findById(parentTemplate.getId());
+DataStore imageStore = parentTemplate.getDataStore();
+Map details = new HashMap();
+for (DatadiskTO diskTemplate : dataDiskTemplates) {
+if (!diskTemplate.isBootable()) {
+createChildDataDiskTemplate(diskTemplate, templateVO,
parentTemplate, imageStore, diskCount++);
+if (!diskTemplate.isIso() &&
details.get(VmDetailConstants.DATA_DISK_CONTROLLER) == null){
+details.put(VmDetailConstants.DATA_DISK_CONTROLLER,
getDiskControllerDetails(diskTemplate));
+details.put(VmDetailConstants.DATA_DISK_CONTROLLER +
diskTemplate.getDiskId(), getDiskControllerDetails(diskTemplate));
+}
+} else {
+finalizeParentTemplate(diskTemplate, templateVO,
parentTemplate, imageStore, diskCount++);
+details.put(VmDetailConstants.ROOT_DISK_CONTROLLER,
getDiskControllerDetails(diskTemplate));
+}
+}
+templateVO.setDetails(details);
+_templateDao.saveDetails(templateVO);
+return true;
+}
+
+private boolean createChildDataDiskTemplate(DatadiskTO dataDiskTemplate,
VMTemplateVO template, TemplateInfo parentTemplate, DataStore imageStore, int
diskCount) {
+// Make an entry in vm_template table
+Storage.ImageFormat format = dataDiskTemplate.isIso() ?
Storage.ImageFormat.ISO : template.getFormat();
+String suffix = dataDiskTemplate.isIso() ? "-IsoDiskTemplate-" :
"-DataDiskTemplate-";
+TemplateType ttype = dataDiskTemplate.isIso() ? TemplateType.ISODISK :
TemplateType.DATADISK;
+final long templateId = _templateDao.getNextInSequence(Long.class,
"id");
+long guestOsId = dataDiskTemplate.isIso() ? 1 : 0;
+String templateName = dataDiskTemplate.isIso() ?
dataDiskTemplate.getPath().substring(dataDiskTemplate.getPath().lastIndexOf(File.separator)
+ 1) : template.getName() + suffix + diskCount;
+VMTemplateVO templateVO = new VMTemplateVO(templateId, templateName,
format, false, false, false, ttype, template.getUrl(),
+template.requiresHvm(), template.getBits(),
template.getAccountId(), null, templateName, false, guestOsId, false,
template.getHypervisorType(), null,
+null, false, false);
+if (dataDiskTemplate.isIso()){
+templateVO.setUniqueName(templateName);
+}
+templateVO.setParentTemplateId(template.getId());
+templateVO.setSize(dataDiskTemplate.getVirtualSize());
+templateVO = _templateDao.persist(templateVO);
+// Make sync call to create Datadisk templates in image store
+TemplateApiResult result = null;
+TemplateInfo dataDiskTemplateInfo =
imageFactory.getTemplate(templateVO.getId(), imageStore);
+AsyncCallFuture future =
createDatadiskTemplateAsync(parentTemplate, dataDiskTemplateInfo,
dataDiskTemplate.getPath(), dataDiskTemplate.getDiskId(),
+dataDiskTemplate.getFileSize(), dataDiskTemplate.isBootable());
+try {
+result = future.get();
+if (result.isSuccess()) {
+// Make an entry in template_zone_ref table
+if (imageStore.getScope().getScopeType() == ScopeType.REGION) {
+associateTemplateToZone(templateId, null);
+} else if (imageStore.getScope().getScopeType() ==
ScopeType.ZONE) {
+Long zoneId =
((ImageStoreEntity)imageStore).getDataCenterId();
+VMTemplateZoneVO templateZone = new
VMTemplateZoneVO(zoneId, templateId, new Date());
+_vmTemplateZoneDao.persist(templateZone);
+}
+
_resourceLimitMgr.incrementResourceCount(template.getAccountId(),
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315889#comment-16315889 ] 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-355901848 @blueorangutan package 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315891#comment-16315891 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355910381 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315888#comment-16315888 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355906217 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1615 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315933#comment-16315933 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355916182 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1617 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315887#comment-16315887 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355901892 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315890#comment-16315890 ] 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-355910344 @blueorangutan package 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315863#comment-16315863 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355906217 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1615 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315825#comment-16315825 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355901892 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315824#comment-16315824 ] 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-355901848 @blueorangutan package 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315561#comment-16315561 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355870139 Trillian test result (tid-2064) Environment: vmware-55u3 (x2), Advanced Networking with Mgmt server 7 Total time taken: 52205 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t2064-vmware-55u3.zip Intermitten failure detected: /marvin/tests/smoke/test_deploy_vgpu_enabled_vm.py Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_root_resize.py Intermitten failure detected: /marvin/tests/smoke/test_vm_life_cycle.py Intermitten failure detected: /marvin/tests/smoke/test_volumes.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py Smoke tests completed. 62 look OK, 5 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- test_3d_gpu_support | `Failure` | 431.76 | test_deploy_vgpu_enabled_vm.py test_00_deploy_vm_root_resize | `Error` | 0.17 | test_deploy_vm_root_resize.py test_08_migrate_vm | `Error` | 56.01 | test_vm_life_cycle.py test_01_create_volume | `Failure` | 202.18 | test_volumes.py test_02_redundant_VPC_default_routes | `Failure` | 1192.86 | test_vpc_redundant.py 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315466#comment-16315466
]
ASF GitHub Bot commented on CLOUDSTACK-4757:
rafaelweingartner commented on a change in pull request #2146: CLOUDSTACK-4757:
Support OVA files with multiple disks for templates
URL: https://github.com/apache/cloudstack/pull/2146#discussion_r160059612
##
File path: api/src/org/apache/cloudstack/api/command/user/vm/DeployVMCmd.java
##
@@ -443,6 +449,37 @@ public String getKeyboard() {
return dhcpOptionsMap;
}
+public Map getDataDiskTemplateToDiskOfferingMap() {
+if (diskOfferingId != null && dataDiskTemplateToDiskOfferingList !=
null) {
Review comment:
Actually, what I suggested is what is being done in the code now...
When I commented the code was different from its current state.
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:
us...@infra.apache.org
> 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315191#comment-16315191 ] 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-355814287 @blueorangutan test centos7 vmware-55u3 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315192#comment-16315192 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355814305 @rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been kicked to run smoke tests 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315189#comment-16315189 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355814247 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1611 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315157#comment-16315157 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355812800 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315155#comment-16315155 ] 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-355812751 @blueorangutan package 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315107#comment-16315107 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355807982 Trillian test result (tid-2049) Environment: vmware-55u3 (x2), Advanced Networking with Mgmt server 7 Total time taken: 53255 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t2049-vmware-55u3.zip Intermitten failure detected: /marvin/tests/smoke/test_deploy_vgpu_enabled_vm.py Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_root_resize.py Intermitten failure detected: /marvin/tests/smoke/test_volumes.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_vpn.py Smoke tests completed. 63 look OK, 4 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- test_3d_gpu_support | `Failure` | 404.84 | test_deploy_vgpu_enabled_vm.py test_00_deploy_vm_root_resize | `Error` | 0.17 | test_deploy_vm_root_resize.py test_01_create_volume | `Failure` | 189.95 | test_volumes.py test_05_rvpc_multi_tiers | `Failure` | 665.46 | test_vpc_redundant.py test_05_rvpc_multi_tiers | `Error` | 726.46 | test_vpc_redundant.py 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315051#comment-16315051 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355796093 Trillian test result (tid-2048) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 35579 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t2048-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py Smoke tests completed. 67 look OK, 0 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314748#comment-16314748 ] 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-355761689 @blueorangutan test centos7 vmware-55u3 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314749#comment-16314749 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355761735 @rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been kicked to run smoke tests 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314734#comment-16314734 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355758128 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1603 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314720#comment-16314720 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355756411 @DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314718#comment-16314718 ] ASF GitHub Bot commented on CLOUDSTACK-4757: DaanHoogland commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355756338 @blueorangutan package 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314692#comment-16314692
]
ASF GitHub Bot commented on CLOUDSTACK-4757:
DaanHoogland commented on a change in pull request #2146: CLOUDSTACK-4757:
Support OVA files with multiple disks for templates
URL: https://github.com/apache/cloudstack/pull/2146#discussion_r160027409
##
File path: api/src/org/apache/cloudstack/api/command/user/vm/DeployVMCmd.java
##
@@ -443,6 +449,37 @@ public String getKeyboard() {
return dhcpOptionsMap;
}
+public Map getDataDiskTemplateToDiskOfferingMap() {
+if (diskOfferingId != null && dataDiskTemplateToDiskOfferingList !=
null) {
Review comment:
@rafaelweingartner only the second part of the first if()s condition can be
removed and the semantics woud slightly change as an exception instead of an
empty map is really different.
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:
us...@infra.apache.org
> 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314674#comment-16314674 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355500725 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1590 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314673#comment-16314673 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355495497 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314668#comment-16314668 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355114589 Trillian test result (tid-1984) Environment: vmware-65 (x2), Advanced Networking with Mgmt server 7 Total time taken: 41901 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t1984-vmware-65.zip Intermitten failure detected: /marvin/tests/smoke/test_deploy_vgpu_enabled_vm.py Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_root_resize.py Intermitten failure detected: /marvin/tests/smoke/test_vm_life_cycle.py Intermitten failure detected: /marvin/tests/smoke/test_volumes.py Smoke tests completed. 62 look OK, 4 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- test_3d_gpu_support | `Failure` | 333.82 | test_deploy_vgpu_enabled_vm.py test_00_deploy_vm_root_resize | `Error` | 0.14 | test_deploy_vm_root_resize.py test_08_migrate_vm | `Error` | 106.20 | test_vm_life_cycle.py test_01_create_volume | `Failure` | 191.96 | test_volumes.py 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314672#comment-16314672 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355391105 Trillian test result (tid-2002) Environment: vmware-55u3 (x2), Advanced Networking with Mgmt server 7 Total time taken: 48665 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t2002-vmware-55u3.zip Intermitten failure detected: /marvin/tests/smoke/test_deploy_vgpu_enabled_vm.py Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_root_resize.py Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_vm_life_cycle.py Intermitten failure detected: /marvin/tests/smoke/test_volumes.py Smoke tests completed. 63 look OK, 4 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- test_3d_gpu_support | `Failure` | 333.10 | test_deploy_vgpu_enabled_vm.py test_00_deploy_vm_root_resize | `Error` | 0.09 | test_deploy_vm_root_resize.py test_08_migrate_vm | `Error` | 55.67 | test_vm_life_cycle.py test_01_create_volume | `Failure` | 197.30 | test_volumes.py 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314670#comment-16314670 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355211594 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1563 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314671#comment-16314671 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355212185 @rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been kicked to run smoke tests 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314669#comment-16314669 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-355203515 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314667#comment-16314667 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-354504434 Trillian test result (tid-1943) Environment: vmware-55u3 (x2), Advanced Networking with Mgmt server 7 Total time taken: 47457 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t1943-vmware-55u3.zip Intermitten failure detected: /marvin/tests/smoke/test_deploy_vgpu_enabled_vm.py Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_root_resize.py Intermitten failure detected: /marvin/tests/smoke/test_volumes.py Smoke tests completed. 63 look OK, 3 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- test_3d_gpu_support | `Failure` | 485.74 | test_deploy_vgpu_enabled_vm.py test_00_deploy_vm_root_resize | `Error` | 0.21 | test_deploy_vm_root_resize.py test_01_create_volume | `Failure` | 202.58 | test_volumes.py 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314661#comment-16314661 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-353660751 @nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314662#comment-16314662 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-353664586 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1464 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314663#comment-16314663 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-353667073 @nvazquez a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314664#comment-16314664 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-353707966 Trillian test result (tid-1878) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 33095 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t1878-kvm-centos7.zip Smoke tests completed. 61 look OK, 6 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- ContextSuite context=TestDeployVirtioSCSIVM>:setup | `Error` | 0.00 | test_deploy_virtio_scsi_vm.py test_01_add_primary_storage_disabled_host | `Error` | 41.49 | test_primary_storage.py test_01_vpc_privategw_acl | `Failure` | 56.66 | test_privategw_acl.py test_02_vpc_privategw_static_routes | `Failure` | 217.43 | test_privategw_acl.py test_03_vpc_privategw_restart_vpc_cleanup | `Failure` | 222.77 | test_privategw_acl.py test_04_rvpc_privategw_static_routes | `Failure` | 439.04 | test_privategw_acl.py test_02_create_template_with_checksum_sha1 | `Error` | 5.17 | test_templates.py test_03_create_template_with_checksum_sha256 | `Error` | 5.15 | test_templates.py test_04_create_template_with_checksum_md5 | `Error` | 5.17 | test_templates.py test_01_vpc_remote_access_vpn | `Failure` | 65.71 | test_vpc_vpn.py test_hostha_kvm_host_degraded | `Error` | 20.54 | test_hostha_kvm.py 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314656#comment-16314656 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-312609191 @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314660#comment-16314660 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-312972685 Trillian test result (tid-1183) Environment: xenserver-65sp1 (x2), Advanced Networking with Mgmt server 6 Total time taken: 49826 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t1183-xenserver-65sp1.zip Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_routers_network_ops.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py Test completed. 49 look ok, 2 have error(s) Test | Result | Time (s) | Test File --- | --- | --- | --- test_05_rvpc_multi_tiers | `Failure` | 459.38 | test_vpc_redundant.py test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | `Failure` | 441.70 | test_vpc_redundant.py test_04_rvpc_privategw_static_routes | `Failure` | 780.82 | test_privategw_acl.py test_01_vpc_site2site_vpn | Success | 275.79 | test_vpc_vpn.py test_01_vpc_remote_access_vpn | Success | 157.13 | test_vpc_vpn.py test_01_redundant_vpc_site2site_vpn | Success | 462.19 | test_vpc_vpn.py test_02_VPC_default_routes | Success | 340.83 | test_vpc_router_nics.py test_01_VPC_nics_after_destroy | Success | 640.80 | test_vpc_router_nics.py test_04_rvpc_network_garbage_collector_nics | Success | 1589.29 | test_vpc_redundant.py test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | Success | 775.08 | test_vpc_redundant.py test_02_redundant_VPC_default_routes | Success | 1046.98 | test_vpc_redundant.py test_09_delete_detached_volume | Success | 10.74 | test_volumes.py test_08_resize_volume | Success | 90.99 | test_volumes.py test_07_resize_fail | Success | 96.02 | test_volumes.py test_06_download_detached_volume | Success | 25.41 | test_volumes.py test_05_detach_volume | Success | 100.32 | test_volumes.py test_04_delete_attached_volume | Success | 10.23 | test_volumes.py test_03_download_attached_volume | Success | 15.35 | test_volumes.py test_02_attach_volume | Success | 11.11 | test_volumes.py test_01_create_volume | Success | 403.58 | test_volumes.py test_change_service_offering_for_vm_with_snapshots | Success | 584.25 | test_vm_snapshots.py test_03_delete_vm_snapshots | Success | 280.25 | test_vm_snapshots.py test_02_revert_vm_snapshots | Success | 219.95 | test_vm_snapshots.py test_01_create_vm_snapshots | Success | 132.70 | test_vm_snapshots.py test_deploy_vm_multiple | Success | 213.17 | test_vm_life_cycle.py test_deploy_vm | Success | 0.05 | test_vm_life_cycle.py test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py test_10_attachAndDetach_iso | Success | 32.66 | test_vm_life_cycle.py test_09_expunge_vm | Success | 125.18 | test_vm_life_cycle.py test_08_migrate_vm | Success | 66.34 | test_vm_life_cycle.py test_07_restore_vm | Success | 0.22 | test_vm_life_cycle.py test_06_destroy_vm | Success | 15.20 | test_vm_life_cycle.py test_03_reboot_vm | Success | 25.42 | test_vm_life_cycle.py test_02_start_vm | Success | 30.42 | test_vm_life_cycle.py test_01_stop_vm_forced | Success | 5.20 | test_vm_life_cycle.py test_01_stop_vm | Success | 35.44 | test_vm_life_cycle.py test_CreateTemplateWithDuplicateName | Success | 262.39 | test_templates.py test_08_list_system_templates | Success | 0.05 | test_templates.py test_07_list_public_templates | Success | 0.05 | test_templates.py test_05_template_permissions | Success | 0.10 | test_templates.py test_04_extract_template | Success | 5.29 | test_templates.py test_03_delete_template | Success | 5.39 | test_templates.py test_02_edit_template | Success | 90.09 | test_templates.py test_01_create_template | Success | 100.97 | test_templates.py test_10_destroy_cpvm | Success | 262.19 | test_ssvm.py test_09_destroy_ssvm | Success | 235.69 | test_ssvm.py test_08_reboot_cpvm | Success | 151.85 | test_ssvm.py test_07_reboot_ssvm | Success | 154.54 | test_ssvm.py test_06_stop_cpvm | Success | 172.06 | test_ssvm.py test_05_stop_ssvm | Success | 174.78 | test_ssvm.py test_04_cpvm_internals | Success | 1.32 | test_ssvm.py test_03_ssvm_internals | Success | 3.82 | test_ssvm.py test_02_list_cpvm_vm | Success | 0.15 | test_ssvm.py test_01_list_sec_storage_vm | Success | 0.12 | test_ssvm.py test_02_list_snapshots_with_removed_data_store | Success | 142.03 | test_snapshots.py test_01_snapshot_root_disk | Success | 22.04 | test_snapshots.py test_04_change_offering_small | Success | 114.15 |
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314658#comment-16314658 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-312851038 @borisstoyanov a Trillian-Jenkins matrix job (centos6 mgmt + xs65sp1, centos7 mgmt + vmware55u3, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314657#comment-16314657 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-312615078 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-787 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314659#comment-16314659 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-312953918 Trillian test result (tid-1184) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 35603 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t1184-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_password_server.py Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Test completed. 50 look ok, 1 have error(s) Test | Result | Time (s) | Test File --- | --- | --- | --- test_04_rvpc_privategw_static_routes | `Failure` | 503.39 | test_privategw_acl.py test_01_vpc_site2site_vpn | Success | 190.11 | test_vpc_vpn.py test_01_vpc_remote_access_vpn | Success | 81.31 | test_vpc_vpn.py test_01_redundant_vpc_site2site_vpn | Success | 291.03 | test_vpc_vpn.py test_02_VPC_default_routes | Success | 289.62 | test_vpc_router_nics.py test_01_VPC_nics_after_destroy | Success | 619.88 | test_vpc_router_nics.py test_05_rvpc_multi_tiers | Success | 589.33 | test_vpc_redundant.py test_04_rvpc_network_garbage_collector_nics | Success | 1466.81 | test_vpc_redundant.py test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | Success | 663.15 | test_vpc_redundant.py test_02_redundant_VPC_default_routes | Success | 825.08 | test_vpc_redundant.py test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1340.67 | test_vpc_redundant.py test_09_delete_detached_volume | Success | 156.67 | test_volumes.py test_08_resize_volume | Success | 156.47 | test_volumes.py test_07_resize_fail | Success | 161.85 | test_volumes.py test_06_download_detached_volume | Success | 156.50 | test_volumes.py test_05_detach_volume | Success | 150.86 | test_volumes.py test_04_delete_attached_volume | Success | 151.42 | test_volumes.py test_03_download_attached_volume | Success | 156.38 | test_volumes.py test_02_attach_volume | Success | 124.76 | test_volumes.py test_01_create_volume | Success | 712.76 | test_volumes.py test_03_delete_vm_snapshots | Success | 275.22 | test_vm_snapshots.py test_02_revert_vm_snapshots | Success | 101.17 | test_vm_snapshots.py test_01_create_vm_snapshots | Success | 170.33 | test_vm_snapshots.py test_deploy_vm_multiple | Success | 313.07 | test_vm_life_cycle.py test_deploy_vm | Success | 0.04 | test_vm_life_cycle.py test_advZoneVirtualRouter | Success | 0.03 | test_vm_life_cycle.py test_10_attachAndDetach_iso | Success | 26.86 | test_vm_life_cycle.py test_09_expunge_vm | Success | 125.27 | test_vm_life_cycle.py test_08_migrate_vm | Success | 30.92 | test_vm_life_cycle.py test_07_restore_vm | Success | 0.12 | test_vm_life_cycle.py test_06_destroy_vm | Success | 125.87 | test_vm_life_cycle.py test_03_reboot_vm | Success | 125.89 | test_vm_life_cycle.py test_02_start_vm | Success | 10.25 | test_vm_life_cycle.py test_01_stop_vm_forced | Success | 5.16 | test_vm_life_cycle.py test_01_stop_vm | Success | 35.35 | test_vm_life_cycle.py test_CreateTemplateWithDuplicateName | Success | 131.15 | test_templates.py test_08_list_system_templates | Success | 0.07 | test_templates.py test_07_list_public_templates | Success | 0.07 | test_templates.py test_05_template_permissions | Success | 0.15 | test_templates.py test_04_extract_template | Success | 5.22 | test_templates.py test_03_delete_template | Success | 5.11 | test_templates.py test_02_edit_template | Success | 90.18 | test_templates.py test_01_create_template | Success | 75.72 | test_templates.py test_10_destroy_cpvm | Success | 162.59 | test_ssvm.py test_09_destroy_ssvm | Success | 194.40 | test_ssvm.py test_08_reboot_cpvm | Success | 131.71 | test_ssvm.py test_07_reboot_ssvm | Success | 163.75 | test_ssvm.py test_06_stop_cpvm | Success | 131.89 | test_ssvm.py test_05_stop_ssvm | Success | 164.02 | test_ssvm.py test_04_cpvm_internals | Success | 1.37 | test_ssvm.py test_03_ssvm_internals | Success | 4.38 | test_ssvm.py test_02_list_cpvm_vm | Success | 0.13 | test_ssvm.py test_01_list_sec_storage_vm | Success | 0.13 | test_ssvm.py test_02_list_snapshots_with_removed_data_store | Success | 253.35 | test_snapshots.py test_01_snapshot_root_disk | Success | 86.94 | test_snapshots.py test_04_change_offering_small | Success | 239.90 | test_service_offerings.py test_03_delete_service_offering | Success | 0.04 | test_service_offerings.py test_02_edit_service_offering | Success | 0.06 |
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314653#comment-16314653 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-354762645 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314652#comment-16314652 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-354416142 @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been kicked to run smoke tests 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314654#comment-16314654 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-354779662 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1545 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314651#comment-16314651 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-354416037 @borisstoyanov unsupported parameters provided. Supported mgmt server os are: `centos6, centos7, ubuntu`. Supported hypervisors are: `kvm-centos6, kvm-centos7, kvm-ubuntu, xenserver-65sp1, xenserver-62sp1, vmware-60u2, vmware-55u3, vmware-51u1, vmware-50u1` 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314644#comment-16314644 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-353943835 @rhtyd a Trillian-Jenkins matrix job (centos6 mgmt + xs65sp1, centos7 mgmt + vmware55u3, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314645#comment-16314645 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-354012610 Trillian test result (tid-1925) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 35911 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t1925-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_loadbalance.py Intermitten failure detected: /marvin/tests/smoke/test_outofbandmanagement.py Intermitten failure detected: /marvin/tests/smoke/test_ssvm.py Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py Smoke tests completed. 66 look OK, 0 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314650#comment-16314650 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-354412746 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1525 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314646#comment-16314646 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-354013055 Trillian test result (tid-1921) Environment: xenserver-65sp1 (x2), Advanced Networking with Mgmt server 6 Total time taken: 42410 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t1921-xenserver-65sp1.zip Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_iso.py Smoke tests completed. 66 look OK, 0 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314643#comment-16314643 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-353942197 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1493 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314647#comment-16314647 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-354028655 Trillian test result (tid-1924) Environment: vmware-55u3 (x2), Advanced Networking with Mgmt server 7 Total time taken: 53733 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t1924-vmware-55u3.zip Intermitten failure detected: /marvin/tests/smoke/test_deploy_vgpu_enabled_vm.py Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_root_resize.py Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_vm_life_cycle.py Intermitten failure detected: /marvin/tests/smoke/test_volumes.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_router_nics.py Smoke tests completed. 59 look OK, 7 have error(s) Only failed tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- test_3d_gpu_support | `Failure` | 369.93 | test_deploy_vgpu_enabled_vm.py test_00_deploy_vm_root_resize | `Error` | 0.16 | test_deploy_vm_root_resize.py test_03_vpc_privategw_restart_vpc_cleanup | `Failure` | 399.85 | test_privategw_acl.py test_04_rvpc_privategw_static_routes | `Failure` | 702.43 | test_privategw_acl.py test_08_migrate_vm | `Error` | 66.31 | test_vm_life_cycle.py test_01_create_volume | `Failure` | 159.99 | test_volumes.py test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | `Failure` | 660.13 | test_vpc_redundant.py test_02_redundant_VPC_default_routes | `Failure` | 1150.15 | test_vpc_redundant.py test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | `Failure` | 333.25 | test_vpc_redundant.py test_05_rvpc_multi_tiers | `Failure` | 664.91 | test_vpc_redundant.py test_05_rvpc_multi_tiers | `Error` | 726.11 | test_vpc_redundant.py test_01_VPC_nics_after_destroy | `Failure` | 883.96 | test_vpc_router_nics.py 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314648#comment-16314648 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-354410361 @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314642#comment-16314642 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-353927772 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314641#comment-16314641
]
ASF GitHub Bot commented on CLOUDSTACK-4757:
DaanHoogland commented on a change in pull request #2146: CLOUDSTACK-4757:
Support OVA files with multiple disks for templates
URL: https://github.com/apache/cloudstack/pull/2146#discussion_r160026547
##
File path:
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
##
@@ -4146,12 +4127,12 @@ protected Answer execute(AttachIsoCommand cmd) {
if (cmd.isAttach()) {
vmMo.mountToolsInstaller();
} else {
-try{
+try {
if (!vmMo.unmountToolsInstaller()) {
return new Answer(cmd, false,
"Failed to unmount vmware-tools
installer ISO as the corresponding CDROM device is locked by VM. Please unmount
the CDROM device inside the VM and ret-try.");
}
-}catch(Throwable e){
+} catch (Throwable e) {
Review comment:
yeah :(
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:
us...@infra.apache.org
> 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314638#comment-16314638 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-311886883 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-785 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314634#comment-16314634 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-310425782 Trillian test result (tid-1180) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 31862 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t1180-kvm-centos7.zip Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Test completed. 50 look ok, 1 have error(s) Test | Result | Time (s) | Test File --- | --- | --- | --- test_04_rvpc_privategw_static_routes | `Failure` | 395.96 | test_privategw_acl.py test_01_vpc_site2site_vpn | Success | 164.84 | test_vpc_vpn.py test_01_vpc_remote_access_vpn | Success | 66.10 | test_vpc_vpn.py test_01_redundant_vpc_site2site_vpn | Success | 290.88 | test_vpc_vpn.py test_02_VPC_default_routes | Success | 274.56 | test_vpc_router_nics.py test_01_VPC_nics_after_destroy | Success | 525.28 | test_vpc_router_nics.py test_05_rvpc_multi_tiers | Success | 528.17 | test_vpc_redundant.py test_04_rvpc_network_garbage_collector_nics | Success | 1335.51 | test_vpc_redundant.py test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | Success | 563.04 | test_vpc_redundant.py test_02_redundant_VPC_default_routes | Success | 773.53 | test_vpc_redundant.py test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1323.88 | test_vpc_redundant.py test_09_delete_detached_volume | Success | 156.70 | test_volumes.py test_08_resize_volume | Success | 156.36 | test_volumes.py test_07_resize_fail | Success | 161.46 | test_volumes.py test_06_download_detached_volume | Success | 156.31 | test_volumes.py test_05_detach_volume | Success | 155.78 | test_volumes.py test_04_delete_attached_volume | Success | 146.13 | test_volumes.py test_03_download_attached_volume | Success | 151.27 | test_volumes.py test_02_attach_volume | Success | 125.31 | test_volumes.py test_01_create_volume | Success | 682.48 | test_volumes.py test_03_delete_vm_snapshots | Success | 275.19 | test_vm_snapshots.py test_02_revert_vm_snapshots | Success | 106.06 | test_vm_snapshots.py test_01_create_vm_snapshots | Success | 179.06 | test_vm_snapshots.py test_deploy_vm_multiple | Success | 242.47 | test_vm_life_cycle.py test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py test_10_attachAndDetach_iso | Success | 26.82 | test_vm_life_cycle.py test_09_expunge_vm | Success | 125.27 | test_vm_life_cycle.py test_08_migrate_vm | Success | 30.95 | test_vm_life_cycle.py test_07_restore_vm | Success | 0.12 | test_vm_life_cycle.py test_06_destroy_vm | Success | 125.78 | test_vm_life_cycle.py test_03_reboot_vm | Success | 125.81 | test_vm_life_cycle.py test_02_start_vm | Success | 10.16 | test_vm_life_cycle.py test_01_stop_vm_forced | Success | 5.14 | test_vm_life_cycle.py test_01_stop_vm | Success | 35.28 | test_vm_life_cycle.py test_CreateTemplateWithDuplicateName | Success | 95.72 | test_templates.py test_08_list_system_templates | Success | 0.03 | test_templates.py test_07_list_public_templates | Success | 0.04 | test_templates.py test_05_template_permissions | Success | 0.06 | test_templates.py test_04_extract_template | Success | 5.15 | test_templates.py test_03_delete_template | Success | 5.10 | test_templates.py test_02_edit_template | Success | 90.16 | test_templates.py test_01_create_template | Success | 80.62 | test_templates.py test_10_destroy_cpvm | Success | 161.63 | test_ssvm.py test_09_destroy_ssvm | Success | 163.55 | test_ssvm.py test_08_reboot_cpvm | Success | 131.56 | test_ssvm.py test_07_reboot_ssvm | Success | 133.62 | test_ssvm.py test_06_stop_cpvm | Success | 131.85 | test_ssvm.py test_05_stop_ssvm | Success | 163.88 | test_ssvm.py test_04_cpvm_internals | Success | 1.17 | test_ssvm.py test_03_ssvm_internals | Success | 5.70 | test_ssvm.py test_02_list_cpvm_vm | Success | 0.12 | test_ssvm.py test_01_list_sec_storage_vm | Success | 0.13 | test_ssvm.py test_02_list_snapshots_with_removed_data_store | Success | 86.93 | test_snapshots.py test_01_snapshot_root_disk | Success | 16.24 | test_snapshots.py test_04_change_offering_small | Success | 239.71 | test_service_offerings.py test_03_delete_service_offering | Success | 0.05 | test_service_offerings.py test_02_edit_service_offering | Success | 0.05 | test_service_offerings.py test_01_create_service_offering | Success | 0.11 |
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314631#comment-16314631 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-310287934 @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314640#comment-16314640 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-312587300 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-786 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314635#comment-16314635 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-310467742 Trillian test result (tid-1179) Environment: xenserver-65sp1 (x2), Advanced Networking with Mgmt server 6 Total time taken: 41757 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t1179-xenserver-65sp1.zip Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py Test completed. 49 look ok, 2 have error(s) Test | Result | Time (s) | Test File --- | --- | --- | --- test_05_rvpc_multi_tiers | `Failure` | 432.37 | test_vpc_redundant.py test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | `Failure` | 464.86 | test_vpc_redundant.py test_04_rvpc_privategw_static_routes | `Failure` | 752.32 | test_privategw_acl.py test_01_vpc_site2site_vpn | Success | 285.22 | test_vpc_vpn.py test_01_vpc_remote_access_vpn | Success | 166.50 | test_vpc_vpn.py test_01_redundant_vpc_site2site_vpn | Success | 496.63 | test_vpc_vpn.py test_02_VPC_default_routes | Success | 299.05 | test_vpc_router_nics.py test_01_VPC_nics_after_destroy | Success | 680.83 | test_vpc_router_nics.py test_04_rvpc_network_garbage_collector_nics | Success | 1578.15 | test_vpc_redundant.py test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | Success | 727.49 | test_vpc_redundant.py test_02_redundant_VPC_default_routes | Success | 973.23 | test_vpc_redundant.py test_09_delete_detached_volume | Success | 20.63 | test_volumes.py test_08_resize_volume | Success | 105.84 | test_volumes.py test_07_resize_fail | Success | 110.91 | test_volumes.py test_06_download_detached_volume | Success | 25.33 | test_volumes.py test_05_detach_volume | Success | 100.22 | test_volumes.py test_04_delete_attached_volume | Success | 15.24 | test_volumes.py test_03_download_attached_volume | Success | 15.26 | test_volumes.py test_02_attach_volume | Success | 10.91 | test_volumes.py test_01_create_volume | Success | 397.88 | test_volumes.py test_change_service_offering_for_vm_with_snapshots | Success | 479.76 | test_vm_snapshots.py test_03_delete_vm_snapshots | Success | 280.18 | test_vm_snapshots.py test_02_revert_vm_snapshots | Success | 181.38 | test_vm_snapshots.py test_01_create_vm_snapshots | Success | 130.94 | test_vm_snapshots.py test_deploy_vm_multiple | Success | 277.30 | test_vm_life_cycle.py test_deploy_vm | Success | 0.02 | test_vm_life_cycle.py test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py test_10_attachAndDetach_iso | Success | 41.89 | test_vm_life_cycle.py test_09_expunge_vm | Success | 185.28 | test_vm_life_cycle.py test_08_migrate_vm | Success | 65.91 | test_vm_life_cycle.py test_07_restore_vm | Success | 0.14 | test_vm_life_cycle.py test_06_destroy_vm | Success | 10.13 | test_vm_life_cycle.py test_03_reboot_vm | Success | 15.16 | test_vm_life_cycle.py test_02_start_vm | Success | 25.22 | test_vm_life_cycle.py test_01_stop_vm_forced | Success | 5.11 | test_vm_life_cycle.py test_01_stop_vm | Success | 30.23 | test_vm_life_cycle.py test_CreateTemplateWithDuplicateName | Success | 186.18 | test_templates.py test_08_list_system_templates | Success | 0.03 | test_templates.py test_07_list_public_templates | Success | 0.03 | test_templates.py test_05_template_permissions | Success | 0.04 | test_templates.py test_04_extract_template | Success | 5.13 | test_templates.py test_03_delete_template | Success | 5.08 | test_templates.py test_02_edit_template | Success | 90.06 | test_templates.py test_01_create_template | Success | 120.85 | test_templates.py test_10_destroy_cpvm | Success | 226.78 | test_ssvm.py test_09_destroy_ssvm | Success | 234.14 | test_ssvm.py test_08_reboot_cpvm | Success | 141.72 | test_ssvm.py test_07_reboot_ssvm | Success | 189.28 | test_ssvm.py test_06_stop_cpvm | Success | 136.68 | test_ssvm.py test_05_stop_ssvm | Success | 174.26 | test_ssvm.py test_04_cpvm_internals | Success | 1.43 | test_ssvm.py test_03_ssvm_internals | Success | 3.75 | test_ssvm.py test_02_list_cpvm_vm | Success | 0.10 | test_ssvm.py test_01_list_sec_storage_vm | Success | 0.11 | test_ssvm.py test_02_list_snapshots_with_removed_data_store | Success | 156.09 | test_snapshots.py test_01_snapshot_root_disk | Success | 21.38 | test_snapshots.py test_04_change_offering_small | Success | 59.16 | test_service_offerings.py test_03_delete_service_offering | Success | 0.08 |
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314633#comment-16314633 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-310295041 @borisstoyanov a Trillian-Jenkins matrix job (centos6 mgmt + xs65sp1, centos7 mgmt + vmware55u3, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests 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: us...@infra.apache.org > 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)
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314636#comment-16314636 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-310506943 Trillian test result (tid-1181) Environment: vmware-55u3 (x2), Advanced Networking with Mgmt server 7 Total time taken: 49291 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2146-t1181-vmware-55u3.zip Intermitten failure detected: /marvin/tests/smoke/test_deploy_vgpu_enabled_vm.py Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_root_resize.py Intermitten failure detected: /marvin/tests/smoke/test_iso.py Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py Intermitten failure detected: /marvin/tests/smoke/test_routers_network_ops.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py Intermitten failure detected: /marvin/tests/smoke/test_vpc_vpn.py Test completed. 47 look ok, 6 have error(s) Test | Result | Time (s) | Test File --- | --- | --- | --- test_04_rvpc_privategw_static_routes | `Failure` | 661.01 | test_privategw_acl.py test_3d_gpu_support | `Failure` | 393.36 | test_deploy_vgpu_enabled_vm.py ContextSuite context=TestVPCRedundancy>:teardown | `Error` | 492.60 | test_vpc_redundant.py ContextSuite context=TestDeployVmRootSize>:setup | `Error` | 0.00 | test_deploy_vm_root_resize.py test_01_vpc_site2site_vpn | Success | 299.73 | test_vpc_vpn.py test_01_vpc_remote_access_vpn | Success | 141.19 | test_vpc_vpn.py test_01_redundant_vpc_site2site_vpn | Success | 520.74 | test_vpc_vpn.py test_02_VPC_default_routes | Success | 341.18 | test_vpc_router_nics.py test_01_VPC_nics_after_destroy | Success | 610.38 | test_vpc_router_nics.py test_05_rvpc_multi_tiers | Success | 487.51 | test_vpc_redundant.py test_04_rvpc_network_garbage_collector_nics | Success | 1474.32 | test_vpc_redundant.py test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | Success | 570.10 | test_vpc_redundant.py test_02_redundant_VPC_default_routes | Success | 599.97 | test_vpc_redundant.py test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1154.15 | test_vpc_redundant.py test_09_delete_detached_volume | Success | 35.87 | test_volumes.py test_06_download_detached_volume | Success | 80.53 | test_volumes.py test_05_detach_volume | Success | 105.26 | test_volumes.py test_04_delete_attached_volume | Success | 15.16 | test_volumes.py test_03_download_attached_volume | Success | 15.21 | test_volumes.py test_02_attach_volume | Success | 59.89 | test_volumes.py test_01_create_volume | Success | 486.00 | test_volumes.py test_change_service_offering_for_vm_with_snapshots | Success | 491.10 | test_vm_snapshots.py test_03_delete_vm_snapshots | Success | 275.11 | test_vm_snapshots.py test_02_revert_vm_snapshots | Success | 222.05 | test_vm_snapshots.py test_01_create_vm_snapshots | Success | 162.08 | test_vm_snapshots.py test_deploy_vm_multiple | Success | 287.13 | test_vm_life_cycle.py test_deploy_vm | Success | 0.02 | test_vm_life_cycle.py test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py test_10_attachAndDetach_iso | Success | 26.84 | test_vm_life_cycle.py test_09_expunge_vm | Success | 125.19 | test_vm_life_cycle.py test_08_migrate_vm | Success | 60.84 | test_vm_life_cycle.py test_07_restore_vm | Success | 0.08 | test_vm_life_cycle.py test_06_destroy_vm | Success | 10.12 | test_vm_life_cycle.py test_03_reboot_vm | Success | 5.10 | test_vm_life_cycle.py test_02_start_vm | Success | 15.16 | test_vm_life_cycle.py test_01_stop_vm_forced | Success | 5.11 | test_vm_life_cycle.py test_01_stop_vm | Success | 10.11 | test_vm_life_cycle.py test_CreateTemplateWithDuplicateName | Success | 301.50 | test_templates.py test_08_list_system_templates | Success | 0.02 | test_templates.py test_07_list_public_templates | Success | 0.03 | test_templates.py test_05_template_permissions | Success | 0.04 | test_templates.py test_04_extract_template | Success | 10.21 | test_templates.py test_03_delete_template | Success | 5.09 | test_templates.py test_02_edit_template | Success | 90.13 | test_templates.py test_01_create_template | Success | 155.85 | test_templates.py test_10_destroy_cpvm | Success | 236.50 | test_ssvm.py test_09_destroy_ssvm | Success | 238.36 | test_ssvm.py test_08_reboot_cpvm | Success | 186.37 | test_ssvm.py test_07_reboot_ssvm | Success | 158.07 | test_ssvm.py test_06_stop_cpvm | Success | 171.48 | test_ssvm.py test_05_stop_ssvm | Success | 178.27 | test_ssvm.py
[jira] [Commented] (CLOUDSTACK-4757) Support OVA files with multiple disks for templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314639#comment-16314639 ] ASF GitHub Bot commented on CLOUDSTACK-4757: blueorangutan commented on issue #2146: CLOUDSTACK-4757: Support OVA files with multiple disks for templates URL: https://github.com/apache/cloudstack/pull/2146#issuecomment-312581286 @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. 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: us...@infra.apache.org > 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)
