[jira] [Created] (CLOUDSTACK-8244) LibvirtServerDiscoverer.java has hard coded agent class
Marcus Sorensen created CLOUDSTACK-8244: --- Summary: LibvirtServerDiscoverer.java has hard coded agent class Key: CLOUDSTACK-8244 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8244 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Marcus Sorensen Fix For: 4.5.0 LibvirtServerDiscoverer.java has a hard-coded string-based reference to LibvirtComputingResource: String guidWithTail = guid + -LibvirtComputingResource; However, this class is configurable in the agent via agent.properties, and this breaks the configurability. This needs to be reworked ideally to discover agents regardless of what the suffix of the guid is. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8243) LibvirtServerDiscoverer.java has hard coded agent class
Marcus Sorensen created CLOUDSTACK-8243: --- Summary: LibvirtServerDiscoverer.java has hard coded agent class Key: CLOUDSTACK-8243 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8243 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Marcus Sorensen Fix For: 4.5.0 LibvirtServerDiscoverer.java has a hard-coded string-based reference to LibvirtComputingResource: String guidWithTail = guid + -LibvirtComputingResource; However, this class is configurable in the agent via agent.properties, and this breaks the configurability. This needs to be reworked ideally to discover agents regardless of what the suffix of the guid is. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8244) LibvirtServerDiscoverer.java has hard coded agent class
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Sorensen closed CLOUDSTACK-8244. --- Resolution: Duplicate LibvirtServerDiscoverer.java has hard coded agent class --- Key: CLOUDSTACK-8244 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8244 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Marcus Sorensen Fix For: 4.5.0 LibvirtServerDiscoverer.java has a hard-coded string-based reference to LibvirtComputingResource: String guidWithTail = guid + -LibvirtComputingResource; However, this class is configurable in the agent via agent.properties, and this breaks the configurability. This needs to be reworked ideally to discover agents regardless of what the suffix of the guid is. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8227) Creating VDI support tool for cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317154#comment-14317154 ] Tilak Raj Singh commented on CLOUDSTACK-8227: - HI Rajesh, I just sent a mail on us...@cloudstack.apache.org and cced your email id rajesh.batt...@citrix.com. I have explained my whole current setup there and the improvements I would like to add into it. Please have a look at it and let me know your feedback on the same. Also if you want to have a look at the current system let's discuss some time and I can show you the whole setup via team viewer. Regards Creating VDI support tool for cloudstack Key: CLOUDSTACK-8227 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8227 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Reporter: Tilak Raj Singh Labels: cloud, gsoc2015, java I wish to create a VDI support tool for cloudstack so that DesktopAsAService can be provided using Cloudstack. I wish to use Guacamole Web Service (http://guac-dev.org/) for the purpose which is based on VNC to do the same -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8227) Creating VDI support tool for cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317504#comment-14317504 ] Rajesh Battala commented on CLOUDSTACK-8227: Great. I will go through it and let you know. Thanks Rajesh Battala Creating VDI support tool for cloudstack Key: CLOUDSTACK-8227 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8227 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Reporter: Tilak Raj Singh Labels: cloud, gsoc2015, java I wish to create a VDI support tool for cloudstack so that DesktopAsAService can be provided using Cloudstack. I wish to use Guacamole Web Service (http://guac-dev.org/) for the purpose which is based on VNC to do the same -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8245) Scrolling down the network service providers list from the UI never ends
Ramamurti Subramanian created CLOUDSTACK-8245: - Summary: Scrolling down the network service providers list from the UI never ends Key: CLOUDSTACK-8245 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8245 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Reporter: Ramamurti Subramanian Priority: Minor Fix For: 4.6.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8104) Add TRIM/Discard support to Qemu
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315892#comment-14315892 ] Wido den Hollander commented on CLOUDSTACK-8104: Without virtio-scsi we can't implement trim/discard Add TRIM/Discard support to Qemu Key: CLOUDSTACK-8104 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8104 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Reporter: Wido den Hollander Assignee: Wido den Hollander Priority: Minor Thinly provisioned volumes on storage devices continue to grow because the storage device has no idea of which blocks are in use. For SSDs the TRIM/Discard feature was invented to give free/unused blocks back to the flash device, but this can also be used for Qemu. Ceph's RBD for example supports trimming so that volumes can shrink again when blocks are no longer in use. This is supported since Qemu 1.5, but since 1.6 it also works for QCOW2 images. It however requires the new virtio-scsi to work optimal, so it requires some changes. For more information see: * http://wiki.qemu.org/ChangeLog/1.5#Block_devices * http://wiki.qemu.org/ChangeLog/1.6#Block_devices * http://ceph.com/docs/master/rbd/qemu-rbd/#enabling-discard-trim * http://wiki.qemu.org/Features/VirtioSCSI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-8239) Add support for VirtIO-SCSI for KVM hypervisors
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wido den Hollander reassigned CLOUDSTACK-8239: -- Assignee: Wido den Hollander Add support for VirtIO-SCSI for KVM hypervisors --- Key: CLOUDSTACK-8239 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8239 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Storage Controller Affects Versions: 4.6.0 Environment: KVM Reporter: Andrei Mikhailovsky Assignee: Wido den Hollander Priority: Critical Labels: ceph, kvm, rbd, storage_drivers, virtio It would be nice to have support for virtio-scsi for KVM hypervisors. The reason for using virtio-scsi instead of virtio-blk would be increasing the number of devices you can attach to a vm, have ability to use discard and reclaim unused blocks from the backend storage like ceph rbd. There are also talks about having a greater performance advantage as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8239) Add support for VirtIO-SCSI for KVM hypervisors
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315895#comment-14315895 ] Wido den Hollander commented on CLOUDSTACK-8239: All new Linux versions support virtio-scsi, so I think we can safely switch to virtio-scsi for all new Linux Instances. Quick check is that Ubuntu 14.04 and CentOS 7 both support it. So it shouldn't be a big problem to change their XML defitinitions and choose VirtIO-SCSI for those guests. Add support for VirtIO-SCSI for KVM hypervisors --- Key: CLOUDSTACK-8239 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8239 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Storage Controller Affects Versions: 4.6.0 Environment: KVM Reporter: Andrei Mikhailovsky Assignee: Wido den Hollander Priority: Critical Labels: ceph, kvm, rbd, storage_drivers, virtio It would be nice to have support for virtio-scsi for KVM hypervisors. The reason for using virtio-scsi instead of virtio-blk would be increasing the number of devices you can attach to a vm, have ability to use discard and reclaim unused blocks from the backend storage like ceph rbd. There are also talks about having a greater performance advantage as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8227) Creating VDI support tool for cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316033#comment-14316033 ] Rajesh Battala commented on CLOUDSTACK-8227: Hi Tilak. We can discuss over mailing listing. we can see your initial setup and what's your plan. Thank Rajesh Battala Creating VDI support tool for cloudstack Key: CLOUDSTACK-8227 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8227 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Reporter: Tilak Raj Singh Labels: cloud, gsoc2015, java I wish to create a VDI support tool for cloudstack so that DesktopAsAService can be provided using Cloudstack. I wish to use Guacamole Web Service (http://guac-dev.org/) for the purpose which is based on VNC to do the same -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8241) Moving the uplaod_volume dict to configurableData section so that volume upload URL can be changed according to the setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316069#comment-14316069 ] ASF subversion and git services commented on CLOUDSTACK-8241: - Commit af09388eda491a529e88ed62fb2c3d62fe554a4d in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=af09388 ] CLOUDSTACK-8241: Moved upload volume dict data to configurableData section of the test_data.py file so that data can be changed according to the setup, also made relevant changes in the test cases Signed-off-by: Srikanteswararao tall...@apache.org Moving the uplaod_volume dict to configurableData section so that volume upload URL can be changed according to the setup - Key: CLOUDSTACK-8241 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8241 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Labels: automation Fix For: 4.5.0 The volume upload URL is hard coded right now and should be moved to configurableData section so that appropriate data can be filled before the running the relevant test cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8240) component.test_vmware_drs.TestVMPlacement.test_vm_creation_in_fully_automated_mode - Skip the test case because it is not possible to check the scenario through au
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316082#comment-14316082 ] ASF subversion and git services commented on CLOUDSTACK-8240: - Commit ec1c3894f0a2cfdd9b9b96e4e01b6e8bba77af0f in cloudstack's branch refs/heads/master from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ec1c389 ] CLOUDSTACK-8240: Skipping test case in test_vmware_drs.py because the scenario is not testable through automation Signed-off-by: Srikanteswararao Talluri tall...@apache.org component.test_vmware_drs.TestVMPlacement.test_vm_creation_in_fully_automated_mode - Skip the test case because it is not possible to check the scenario through automation --- Key: CLOUDSTACK-8240 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8240 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Labels: automation Fix For: 4.5.0 The test case fails because Vm is being deployed with memory so high (just below the host capacity) that such high amount of memory can't be specified in service offering. The scenario is not testable, hence test case should be skipped. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
