[jira] [Commented] (CLOUDSTACK-8228) Allow adding hosts from different subnets in same POD
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14325703#comment-14325703 ] Daan Hoogland commented on CLOUDSTACK-8228: --- [~tillu] : marking this as fixed in 'future'. please adjust if you have any commits/reviews specific to a version. thanks Allow adding hosts from different subnets in same POD - Key: CLOUDSTACK-8228 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8228 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.1 Reporter: Tilak Raj Singh Priority: Minor Fix For: Future According to definition of Pods, all hosts in one Pod should belong to the same subnet only. But through the web GUI when trying to add hosts of different subnets running same hypervisor into same Pod in Basic Networking, cloudstack does not not throw any error. Such operation should not be allowed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8228) Allow adding hosts from different subnets in same POD
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-8228: -- Fix Version/s: (was: 4.4.2) Future Allow adding hosts from different subnets in same POD - Key: CLOUDSTACK-8228 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8228 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.1 Reporter: Tilak Raj Singh Priority: Minor Fix For: Future According to definition of Pods, all hosts in one Pod should belong to the same subnet only. But through the web GUI when trying to add hosts of different subnets running same hypervisor into same Pod in Basic Networking, cloudstack does not not throw any error. Such operation should not be allowed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-3383) GetHostStatsCommand fails when agent is running Ubuntu 13.04 (raring)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daan Hoogland resolved CLOUDSTACK-3383.
---
Resolution: Fixed
[~hvt]: should be fixed. can you verify?
GetHostStatsCommand fails when agent is running Ubuntu 13.04 (raring)
-
Key: CLOUDSTACK-3383
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3383
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM
Affects Versions: 4.1.0
Environment: Ubuntu 13.04
Reporter: Harm van Tilborg
Assignee: Wido den Hollander
Labels: agent, kvm, libvirt
Fix For: 4.5.0, 4.6.0, 4.4.2
Attachments: ubuntu14-usage-stats.patch
2013-07-05 13:02:37,782 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-3:null) Processing command:
com.cloud.agent.api.GetHostStatsCommand
2013-07-05 13:02:37,782 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Executing: /bin/bash -c idle=$(top -b -n 1|grep
Cpu\(s\):|cut -d% -f4|cut -d, -f2);echo $idle
2013-07-05 13:02:37,940 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Execution is successful.
2013-07-05 13:02:37,941 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-3:null) Seq 1-2144469000: { Ans: , MgmtId:
159497075554, via: 1, Ver: v1, Flags: 10,
[{Answer:{result:false,details:empty String,wait:0}}] }
When I check the output of Ubuntu's 13.04 top (top -v = procps-ng version
3.3.3), it's formatted like this:
raring# top -b -n 1|grep Cpu\(s\):
%Cpu(s): 0.2 us, 0.2 sy, 0.0 ni, 99.5 id, 0.1 wa, 0.0 hi, 0.0 si, 0.0
st
While on Ubuntu 12.04 (top -v = procps version 3.2.8) it looks like this:
precise# top -b -n 1|grep Cpu\(s\):
Cpu(s): 0.3%us, 0.1%sy, 0.0%ni, 99.6%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st
So I believe it is better to split the string on a comma (,) than using the
percentage (%).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-6181) Root resize
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14325724#comment-14325724 ] Nux edited comment on CLOUDSTACK-6181 at 2/18/15 11:19 AM: --- Ok, done some tests. Env: ACS 4.5 RC3, CentOS 6 stock hypervisors. Live resizing a live ROOT volume from cloudmonkey left me with a corrupted (beyond fsck) volume; it is still readable but the VM OS (CentOs 6) does not function properly, can't even login, though surprisingly still boots. While doing this resize I noticed in the hypervisors the command used is solely qemu-img, eg: /usr/bin/qemu-img resize /var/lib/libvirt/images/5b99dd72-7ac2-4e78-85bd-47c82b65ebea So while /usr/share/cloudstack-common/scripts/storage/qcow2/resizevolume.sh seems to invoke virsh blockresize I have not seen it in the processes, the solution here would be to avoid qemu-img resize for live VMs (?). Of course, just to be sure, if I live resize the ROOT volume (of a new machine obviously) via virsh blockresize manually, then not only it doesn't get corrupted, but the OS instantly sees the modification. Why can't we just use solely virsh blockresize for live VMs? All in all, the resize operation is very valuable, without it we can't upgrade/downgrade machines and I'd rather keep it, even with the current risks. People just need to be aware of the problem or apply Loic's patch? Thoughts? was (Author: nuxro): Ok, done some tests. Env: ACS 4.5 RC3, CentOS 6 stock hypervisors. Live resizing a live ROOT volume from cloudmonkey left me with a corrupted (beyond fsck) volume; it is still readable but the VM OS (CentOs 6) does not function properly, can't even login, though surprisingly still boots. While doing this resize I noticed in the hypervisors the command used is solely qemu-img, eg: /usr/bin/qemu-img resize /var/lib/libvirt/images/5b99dd72-7ac2-4e78-85bd-47c82b65ebea So while /usr/share/cloudstack-common/scripts/storage/qcow2/resizevolume.sh seems to invoke virsh blockresize, the solution here would be to avoid qemu-img resize for live VMs. Of course, just to be sure, if I live resize the ROOT volume (of a new machine obviously) via virsh blockresize manually, then not only it doesn't get corrupted, but the OS instantly sees the modification. Why can't we just use solely virsh blockresize for live VMs? All in all, the resize operation is very valuable, without it we can't upgrade/downgrade machines and I'd rather keep it, even with the current risks. People just need to be aware of the problem or apply Loic's patch? Thoughts? Root resize --- Key: CLOUDSTACK-6181 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6181 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Storage Controller, UI Affects Versions: 4.4.0 Environment: KVM/libvirt/CentOS, Xenserver Reporter: Nux Labels: disk, resize, template Fix For: 4.4.0 Rationale: Currently the root size of an instance is locked to that of the template. This creates unnecessary template duplicates, prevents the creation of a market place, wastes time and disk space and generally makes work more complicated. Real life example - a small VPS provider might want to offer the following sizes (in GB): 10,20,40,80,160,240,320,480,620 That's 9 offerings. The template selection could look like this, including real disk space used: Windows 2008 ~10GB Windows 2008+Plesk ~15GB Windows 2008+MSSQL ~15GB Windows 2012 ~10GB Windows 2012+Plesk ~15GB Windows 2012+MSSQL ~15GB CentOS ~1GB CentOS+CPanel ~3GB CentOS+Virtualmin ~3GB CentOS+Zimbra ~3GB CentOS+Docker ~2GB Debian ~1GB Ubuntu LTS ~1GB In this case the total disk space used by templates will be 828 GB, that's almost 1 TB. If your storage is expensive and limited SSD this can get painful! If the root resize feature is enabled we can reduce this to under 100 GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6181) Root resize
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14325724#comment-14325724 ] Nux commented on CLOUDSTACK-6181: - Ok, done some tests. Env: ACS 4.5 RC3, CentOS 6 stock hypervisors. Live resizing a live ROOT volume from cloudmonkey left me with a corrupted (beyond fsck) volume; it is still readable but the VM OS (CentOs 6) does not function properly, can't even login, though surprisingly still boots. While doing this resize I noticed in the hypervisors the command used is solely qemu-img, eg: /usr/bin/qemu-img resize /var/lib/libvirt/images/5b99dd72-7ac2-4e78-85bd-47c82b65ebea So while /usr/share/cloudstack-common/scripts/storage/qcow2/resizevolume.sh seems to invoke virsh blockresize, the solution here would be to avoid qemu-img resize for live VMs. Of course, just to be sure, if I live resize the ROOT volume (of a new machine obviously) via virsh blockresize manually, then not only it doesn't get corrupted, but the OS instantly sees the modification. Why can't we just use solely virsh blockresize for live VMs? All in all, the resize operation is very valuable, without it we can't upgrade/downgrade machines and I'd rather keep it, even with the current risks. People just need to be aware of the problem or apply Loic's patch? Thoughts? Root resize --- Key: CLOUDSTACK-6181 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6181 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Storage Controller, UI Affects Versions: 4.4.0 Environment: KVM/libvirt/CentOS, Xenserver Reporter: Nux Labels: disk, resize, template Fix For: 4.4.0 Rationale: Currently the root size of an instance is locked to that of the template. This creates unnecessary template duplicates, prevents the creation of a market place, wastes time and disk space and generally makes work more complicated. Real life example - a small VPS provider might want to offer the following sizes (in GB): 10,20,40,80,160,240,320,480,620 That's 9 offerings. The template selection could look like this, including real disk space used: Windows 2008 ~10GB Windows 2008+Plesk ~15GB Windows 2008+MSSQL ~15GB Windows 2012 ~10GB Windows 2012+Plesk ~15GB Windows 2012+MSSQL ~15GB CentOS ~1GB CentOS+CPanel ~3GB CentOS+Virtualmin ~3GB CentOS+Zimbra ~3GB CentOS+Docker ~2GB Debian ~1GB Ubuntu LTS ~1GB In this case the total disk space used by templates will be 828 GB, that's almost 1 TB. If your storage is expensive and limited SSD this can get painful! If the root resize feature is enabled we can reduce this to under 100 GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8264) Add missing change in test_data.py
Gaurav Aradhye created CLOUDSTACK-8264: -- Summary: Add missing change in test_data.py Key: CLOUDSTACK-8264 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8264 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 Fix For: 4.5.0 Add the change overwritten inadvertently by commit 500baea9b6c816caae93ab2f8d0ba31f99c3f8fc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6181) Root resize
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14326194#comment-14326194 ] Marcus Sorensen commented on CLOUDSTACK-6181: - If you want you can just take the new agent code for a spin: http://marcus.mlsorensen.com/cloudstack-extras/cloudstack-agent-4.5.0-SNAPSHOT.el6.x86_64.rpm Root resize --- Key: CLOUDSTACK-6181 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6181 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Storage Controller, UI Affects Versions: 4.4.0 Environment: KVM/libvirt/CentOS, Xenserver Reporter: Nux Labels: disk, resize, template Fix For: 4.4.0 Rationale: Currently the root size of an instance is locked to that of the template. This creates unnecessary template duplicates, prevents the creation of a market place, wastes time and disk space and generally makes work more complicated. Real life example - a small VPS provider might want to offer the following sizes (in GB): 10,20,40,80,160,240,320,480,620 That's 9 offerings. The template selection could look like this, including real disk space used: Windows 2008 ~10GB Windows 2008+Plesk ~15GB Windows 2008+MSSQL ~15GB Windows 2012 ~10GB Windows 2012+Plesk ~15GB Windows 2012+MSSQL ~15GB CentOS ~1GB CentOS+CPanel ~3GB CentOS+Virtualmin ~3GB CentOS+Zimbra ~3GB CentOS+Docker ~2GB Debian ~1GB Ubuntu LTS ~1GB In this case the total disk space used by templates will be 828 GB, that's almost 1 TB. If your storage is expensive and limited SSD this can get painful! If the root resize feature is enabled we can reduce this to under 100 GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6181) Root resize
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14326249#comment-14326249 ] Nux commented on CLOUDSTACK-6181: - Sure! Tried it and the corruption went away, thanks! This is the output on the HV procs at the moment I ran the resize, seems ok at first sight: http://fpaste.org/187115/42428110/raw/ However, there is a problem. The new size is visible physically, in the guest, but not in the DB; cloudmonkey and the UI still show the volume with the old size... Could this be because only the agent is of different version? (wild guess) If I revert to the RC3 version of the agent the DB is updated accordingly. Root resize --- Key: CLOUDSTACK-6181 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6181 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Storage Controller, UI Affects Versions: 4.4.0 Environment: KVM/libvirt/CentOS, Xenserver Reporter: Nux Labels: disk, resize, template Fix For: 4.4.0 Rationale: Currently the root size of an instance is locked to that of the template. This creates unnecessary template duplicates, prevents the creation of a market place, wastes time and disk space and generally makes work more complicated. Real life example - a small VPS provider might want to offer the following sizes (in GB): 10,20,40,80,160,240,320,480,620 That's 9 offerings. The template selection could look like this, including real disk space used: Windows 2008 ~10GB Windows 2008+Plesk ~15GB Windows 2008+MSSQL ~15GB Windows 2012 ~10GB Windows 2012+Plesk ~15GB Windows 2012+MSSQL ~15GB CentOS ~1GB CentOS+CPanel ~3GB CentOS+Virtualmin ~3GB CentOS+Zimbra ~3GB CentOS+Docker ~2GB Debian ~1GB Ubuntu LTS ~1GB In this case the total disk space used by templates will be 828 GB, that's almost 1 TB. If your storage is expensive and limited SSD this can get painful! If the root resize feature is enabled we can reduce this to under 100 GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8267) ACS 4.5.0 Template Delete Button Missing in UI
ilya musayev created CLOUDSTACK-8267: Summary: ACS 4.5.0 Template Delete Button Missing in UI Key: CLOUDSTACK-8267 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8267 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0, 4.6.0 Environment: Build of ACS 4.5.0 on 2/10/2015 Reporter: ilya musayev Priority: Critical Fix For: 4.5.0 In ACS 4.5.0 Template Delete Button Missing in UI? is this by design? This would be a major bug (for some folks who operate public clouds with cloudstack UI, blocker). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8266) Automatic workload Management in the clusters Managed by CloudStack for efficient host Management.
Rajesh Battala created CLOUDSTACK-8266: -- Summary: Automatic workload Management in the clusters Managed by CloudStack for efficient host Management. Key: CLOUDSTACK-8266 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8266 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.5.0 Environment: Java, Linux, Hypervisor Reporter: Rajesh Battala Fix For: 4.5.0 CloudStack manages hypervisor hosts as clusters. It will deploy the vm's to ensure proper hosts capacity are used max. Due to some operations by user on vm's like stop/migrate/destroy hosts usage in the clusters will be in inefficient state. To solve this issue we can have a new Manager who will regularly checks host capacity and implement Server Consolidtion by taking the actions: 1. Live migrate the vm's if possible along with storage. Migrate them such that hosts are fully utilized. 2. After redistributing the vm's Shutdown the hosts which are empty. 3. When load is getting increased,power-on the hosts remotely by WOL(Wake On Lan) mechanisam. This idea is discussed and presented in Collab Conference 2014. Here is the youtube link https://www.youtube.com/watch?v=hJKdZcSpGNQ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8263) KVM live resize not working for libvirt-resizable storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14326545#comment-14326545 ] ASF subversion and git services commented on CLOUDSTACK-8263: - Commit c82d026e0888375bf93a96c2270ce11c612c in cloudstack's branch refs/heads/4.5 from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c82d011 ] CLOUDSTACK-8263: KVM - virsh resize doesnt refresh libvirt's view of the volume size, refresh pool Change-Id: I5ea54f7389d72b57bb625e4d87b45b65eb0c96cd KVM live resize not working for libvirt-resizable storage - Key: CLOUDSTACK-8263 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8263 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: Marcus Sorensen Assignee: Marcus Sorensen Fix For: 4.5.0 KVM resize volume requires a reboot for most QCOW2 based storage, because the libvirt bindings aren't able to notify the hypervisor. We can leverage the existing resize CLI scripts to notify the hypervisor for these storage types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6181) Root resize
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14326486#comment-14326486 ] Marcus Sorensen commented on CLOUDSTACK-6181: - Crap. Why in the world does the libvirt pool not see the update via 'virsh blockresize' ... Try this, forces a pool refresh after resize. Works in my test: http://marcus.mlsorensen.com/cloudstack-extras/cloud-plugin-hypervisor-kvm-4.5.0-SNAPSHOT.jar drop it into /usr/share/cloudstack-agent/lib where you installed the last RPM and restart the agent. Root resize --- Key: CLOUDSTACK-6181 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6181 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Storage Controller, UI Affects Versions: 4.4.0 Environment: KVM/libvirt/CentOS, Xenserver Reporter: Nux Labels: disk, resize, template Fix For: 4.4.0 Rationale: Currently the root size of an instance is locked to that of the template. This creates unnecessary template duplicates, prevents the creation of a market place, wastes time and disk space and generally makes work more complicated. Real life example - a small VPS provider might want to offer the following sizes (in GB): 10,20,40,80,160,240,320,480,620 That's 9 offerings. The template selection could look like this, including real disk space used: Windows 2008 ~10GB Windows 2008+Plesk ~15GB Windows 2008+MSSQL ~15GB Windows 2012 ~10GB Windows 2012+Plesk ~15GB Windows 2012+MSSQL ~15GB CentOS ~1GB CentOS+CPanel ~3GB CentOS+Virtualmin ~3GB CentOS+Zimbra ~3GB CentOS+Docker ~2GB Debian ~1GB Ubuntu LTS ~1GB In this case the total disk space used by templates will be 828 GB, that's almost 1 TB. If your storage is expensive and limited SSD this can get painful! If the root resize feature is enabled we can reduce this to under 100 GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8263) KVM live resize not working for libvirt-resizable storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14326547#comment-14326547 ] ASF subversion and git services commented on CLOUDSTACK-8263: - Commit fe5d41d8c3c332ecec9283bbc4ad9578845ca6b3 in cloudstack's branch refs/heads/4.4 from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fe5d41d ] CLOUDSTACK-8263: KVM - virsh resize doesnt refresh libvirt's view of the volume size, refresh pool Change-Id: I5ea54f7389d72b57bb625e4d87b45b65eb0c96cd KVM live resize not working for libvirt-resizable storage - Key: CLOUDSTACK-8263 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8263 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: Marcus Sorensen Assignee: Marcus Sorensen Fix For: 4.5.0 KVM resize volume requires a reboot for most QCOW2 based storage, because the libvirt bindings aren't able to notify the hypervisor. We can leverage the existing resize CLI scripts to notify the hypervisor for these storage types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8263) KVM live resize not working for libvirt-resizable storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14326548#comment-14326548 ] ASF subversion and git services commented on CLOUDSTACK-8263: - Commit 6c05d9f572ee245b43bb06b384c339d17a20b83d in cloudstack's branch refs/heads/master from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6c05d9f ] CLOUDSTACK-8263: KVM - virsh resize doesnt refresh libvirt's view of the volume size, refresh pool Change-Id: I5ea54f7389d72b57bb625e4d87b45b65eb0c96cd KVM live resize not working for libvirt-resizable storage - Key: CLOUDSTACK-8263 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8263 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: Marcus Sorensen Assignee: Marcus Sorensen Fix For: 4.5.0 KVM resize volume requires a reboot for most QCOW2 based storage, because the libvirt bindings aren't able to notify the hypervisor. We can leverage the existing resize CLI scripts to notify the hypervisor for these storage types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7583) Send statistics collected by StatsCollector to optional Graphite host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14326662#comment-14326662 ] Marcus Sorensen commented on CLOUDSTACK-7583: - Is there no documentation / functional spec for this? Send statistics collected by StatsCollector to optional Graphite host - Key: CLOUDSTACK-7583 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7583 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: Future Reporter: Wido den Hollander Assignee: Wido den Hollander Fix For: 4.6.0 It would be very useful if the StatsCollector inside the management server could also send all the stats collected to a Graphite server in addition to the usage database. This allows for easy graph generation for CPU, Network and Disk I/O of Instances and hosts. Via a global setting we can configure: * Graphite host * Graphite port * Key prefix We can then send Instance and Host information, like: cloudstack.stats.instances.vm id.cpu.num 1 cloudstack.stats.instances.vm id.cpu.utilization 50 cloudstack.stats.instances.vm id.network.read_kbs 4817 cloudstack.stats.instances.vm id.network.write_kbs 672 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-1032) Management Server updates for VHDX templates, and Hyper-V clusters
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-1032: Fix Version/s: (was: 4.3.2) Future Management Server updates for VHDX templates, and Hyper-V clusters -- Key: CLOUDSTACK-1032 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1032 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: API, Template, UI Affects Versions: 4.3.2 Reporter: Donal Lafferty Assignee: Donal Lafferty Fix For: Future UI exposed by management server must allow templates with the VHDX image type used by Hyper-V 2012, and it must allow Hyper-V clusters to be configured. SystemVMs are not available in this phase, so management server should be stopped from attempting to create them on this kind of cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-2248) Automation: Add automation for Better VM Sync
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-2248: Fix Version/s: (was: 4.3.2) Future Automation: Add automation for Better VM Sync - Key: CLOUDSTACK-2248 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2248 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Sudha Ponnaganti Priority: Critical Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-2227) [Automation] Add Automation for Egress firewall rules for guest network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-2227: Fix Version/s: (was: 4.3.2) Future [Automation] Add Automation for Egress firewall rules for guest network --- Key: CLOUDSTACK-2227 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2227 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Network Devices Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Priority: Critical Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-2229) Automation: Add Automation for resize volume feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-2229: Fix Version/s: (was: 4.3.2) Future Automation: Add Automation for resize volume feature Key: CLOUDSTACK-2229 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2229 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Reporter: Sudha Ponnaganti Assignee: Srikanteswararao Talluri Priority: Critical Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-2226) Automation: Add Automation for User and Domain admin can change his password
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-2226: Fix Version/s: (was: 4.3.2) Future Automation: Add Automation for User and Domain admin can change his password Key: CLOUDSTACK-2226 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2226 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Priority: Critical Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-2228) Automation - Add automation for EC2 Query API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-2228: Fix Version/s: (was: 4.3.2) Future Automation - Add automation for EC2 Query API - Key: CLOUDSTACK-2228 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2228 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: AWSAPI Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Priority: Critical Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-917) QA - review Document vSphere / ESXi patch installation procedure
[ https://issues.apache.org/jira/browse/CLOUDSTACK-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-917: --- Fix Version/s: (was: 4.3.2) Future QA - review Document vSphere / ESXi patch installation procedure Key: CLOUDSTACK-917 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-917 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Priority: Minor Fix For: Future - review docs for this procedure - Need to perform the procedure as well -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-4945) [Doc] Pluggable VM Snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-4945: Fix Version/s: (was: 4.3.2) Future [Doc] Pluggable VM Snapshot --- Key: CLOUDSTACK-4945 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4945 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Fix For: Future Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf, Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-3390) Documentation for Mapping CloudStack Zone and VMWare Datacenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-3390: Fix Version/s: (was: 4.3.2) Future Documentation for Mapping CloudStack Zone and VMWare Datacenter --- Key: CLOUDSTACK-3390 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3390 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc, VMware Reporter: Radhika Nair Assignee: angeline shen Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-879) QA S3-backed Secondary Storage Feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-879: --- Fix Version/s: (was: 4.3.2) Future QA S3-backed Secondary Storage Feature -- Key: CLOUDSTACK-879 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-879 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Test Reporter: Chip Childers Assignee: John Burwell Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-2074) [UI] UI of Affinity / Anti-affinity Rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-2074: Fix Version/s: (was: 4.3.2) Future [UI] UI of Affinity / Anti-affinity Rules -- Key: CLOUDSTACK-2074 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2074 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: Jessica Wang Assignee: Jessica Wang Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-4960) [doc] Release notes for SMTP timeout parameters
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-4960: Fix Version/s: (was: 4.3.2) Future [doc] Release notes for SMTP timeout parameters --- Key: CLOUDSTACK-4960 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4960 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Anshul Gangwar Fix For: Future Mention in the release notes that SMTP timeout parameters alert.smtp.timeout and alert.smtp.connectiontimeout are added to global configuration with default timeout value to 30secs. Previously they were infinite and not available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5127) [Doc] Document XS VM Snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5127: Fix Version/s: (was: 4.3.2) Future [Doc] Document XS VM Snapshot - Key: CLOUDSTACK-5127 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5127 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-666) Health monitoring for Brocade load balanced instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-666: --- Fix Version/s: (was: 4.3.2) Future Health monitoring for Brocade load balanced instances - Key: CLOUDSTACK-666 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-666 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Reporter: Rajesh Battala Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-829) Document EC2 Query API usage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-829: --- Fix Version/s: (was: 4.3.2) Future Document EC2 Query API usage Key: CLOUDSTACK-829 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-829 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: AWSAPI, Doc Reporter: Chip Childers Assignee: sebastien goasguen Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-4876) QA : LDAP user provisioning improvements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-4876: Fix Version/s: (was: 4.3.2) Future QA : LDAP user provisioning improvements Key: CLOUDSTACK-4876 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4876 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: API Reporter: Sudha Ponnaganti Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5052) [UI] host socket count per hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5052: Fix Version/s: (was: 4.3.2) Future [UI] host socket count per hypervisor - Key: CLOUDSTACK-5052 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5052 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Reporter: Harikrishna Patnala Fix For: Future UI changes are mentioned in the FS: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Report+CPU+sockets Changes to existing APIs We will introduce 1) new parameter in listhost API call named hypervisortype 2) new parameter in listhost response named cpusockets http://localhost:8080/client/api?command=listHostshypervisor=xenserversessionkey=uMjdI0ko3GbIkvPk3GLSnn7zNTY%3Dpage=1pageSize=20type=routinglistAll=true_=1382505530956 In reponse we have new parameter value cpusockets:1 UI changes --- We show the following information in 'Infrastructure' tab. From UI it looks like === Hypervisor | Hosts | Sockets === VMware | 20 | 45 -- XenServer 6.2| 50 | 70 -- XenServer | 50 | unknown -- KVM | 15 | 35 -- Hyper-V | 30 | unknown === Some minimal calculations are required from the listHost response. 1) Call listHosts API with filter hypervisor (say xenserver) 2) take the count of number of hosts 3) In the response we need to take sum of all the values of parameter cpusockets. If cpusockets are not mentioned for particular hypervisor type we leave the value as unknown. This we need to for all hypervisor types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5128) [Doc] Update VR to use Xen 64 bit template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5128: Fix Version/s: (was: 4.3.2) Future [Doc] Update VR to use Xen 64 bit template -- Key: CLOUDSTACK-5128 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5128 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-915) QA - Create SELinux policy for KVM agent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-915: --- Fix Version/s: (was: 4.3.2) Future QA - Create SELinux policy for KVM agent - Key: CLOUDSTACK-915 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-915 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Reporter: Sudha Ponnaganti Fix For: Future - Need to write test cases and proide test results - Automation ?? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-2829) QA Allow specification of different VIF drivers per traffic type in KVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-2829: Fix Version/s: (was: 4.3.2) Future QA Allow specification of different VIF drivers per traffic type in KVM --- Key: CLOUDSTACK-2829 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2829 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Assignee: Dave Cahill Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-912) QA Create-Tag feature is not avialable for VPN Customer Gateway
[ https://issues.apache.org/jira/browse/CLOUDSTACK-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-912: --- Fix Version/s: (was: 4.3.2) Future QA Create-Tag feature is not avialable for VPN Customer Gateway --- Key: CLOUDSTACK-912 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-912 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Fix For: Future - Upload test cases/ test plan - add automation - test on ASF Master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5129) [Doc] UCS Enhancements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5129: Fix Version/s: (was: 4.3.2) Future [Doc] UCS Enhancements -- Key: CLOUDSTACK-5129 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5129 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-1955) Packaging: package cloudstack-sysdaemons
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-1955: Fix Version/s: (was: 4.3.2) Future Packaging: package cloudstack-sysdaemons - Key: CLOUDSTACK-1955 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1955 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Storage Controller Reporter: Chiradeep Vittal Fix For: Future Copying systemvm.zip around and starting daemons without some kind of init script isn't ideal. Probably have a meta-package (perhaps the root cloudstack package) that would require cloudstack-sysdaemons. A person would still be able to 'yum install cloudstack-server and not get those dameons, but the 'default' install (yum install cloudstack) would have SS/CP as a dependency and thus have it installed and started. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-2267) QA: Support remove network over VMware deployments with dvSwitch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-2267: Fix Version/s: (was: 4.3.2) Future QA: Support remove network over VMware deployments with dvSwitch Key: CLOUDSTACK-2267 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2267 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti Assignee: Sailaja Mada Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-831) Document remote access VPN on SRX support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-831: --- Fix Version/s: (was: 4.3.2) Future Document remote access VPN on SRX support - Key: CLOUDSTACK-831 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-831 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Reporter: Chip Childers Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5130) [Doc] Choose Single-part or Multi-part Upload to Object Storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5130: Fix Version/s: (was: 4.3.2) Future [Doc] Choose Single-part or Multi-part Upload to Object Storage --- Key: CLOUDSTACK-5130 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5130 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-773) Document Object Store-Integration with CS as secondary Storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-773: --- Fix Version/s: (was: 4.3.2) Future Document Object Store-Integration with CS as secondary Storage -- Key: CLOUDSTACK-773 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-773 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Fix For: Future Document Object Store-Integration with CS as secondary Storage -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5125) [doc] Release Note Known Issues, Fixed Issues, and New features
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5125: Fix Version/s: (was: 4.3.2) Future [doc] Release Note Known Issues, Fixed Issues, and New features --- Key: CLOUDSTACK-5125 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5125 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-823) Document any changes to the baremetal provisioning feature.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-823: --- Fix Version/s: (was: 4.3.2) Future Document any changes to the baremetal provisioning feature. --- Key: CLOUDSTACK-823 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-823 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Chip Childers Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-4602) [DOC] CLONE - Update the supported ec2 version from 2010-11-15 to a more recent EC2 API version i.e. 2012-08-15.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-4602: Fix Version/s: (was: 4.3.2) Future [DOC] CLONE - Update the supported ec2 version from 2010-11-15 to a more recent EC2 API version i.e. 2012-08-15. Key: CLOUDSTACK-4602 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4602 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: AWSAPI Affects Versions: 4.2.0 Reporter: Likitha Shetty Labels: documentation Fix For: Future As described the functional spec - https://cwiki.apache.org/confluence/display/CLOUDSTACK/EC2++-+Functional+Spec+for+Query+API+support, the AWS EC2 version supported by CS AWSAPI needs to be updated to more recent version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5126) [Doc] Release Notes 4.2.1 Upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5126: Fix Version/s: (was: 4.3.2) Future [Doc] Release Notes 4.2.1 Upgrade - Key: CLOUDSTACK-5126 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5126 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-1442) Document BigSwitch plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-1442: Fix Version/s: (was: 4.3.2) Future Document BigSwitch plugin - Key: CLOUDSTACK-1442 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1442 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Jessica Tomechak Assignee: Kanzhe Jiang Priority: Minor Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5287) [doc] nTier Apps 2.0 : Remote access VPN to VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5287: Fix Version/s: (was: 4.3.2) Future [doc] nTier Apps 2.0 : Remote access VPN to VPC --- Key: CLOUDSTACK-5287 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5287 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5290) [doc] Document LDAP user provisioning improvements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5290: Fix Version/s: (was: 4.3.2) Future [doc] Document LDAP user provisioning improvements -- Key: CLOUDSTACK-5290 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5290 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Labels: ldap Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5292) [doc] Document Monitering services in virtual router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5292: Fix Version/s: (was: 4.3.2) Future [doc] Document Monitering services in virtual router Key: CLOUDSTACK-5292 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5292 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: Future Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf, Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5291) [doc] Document Site-to-Site VPN VR-to-VR
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5291: Fix Version/s: (was: 4.3.2) Future [doc] Document Site-to-Site VPN VR-to-VR Key: CLOUDSTACK-5291 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5291 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5288) [DOC]Document VR Upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5288: Fix Version/s: (was: 4.3.2) Future [DOC]Document VR Upgrade Key: CLOUDSTACK-5288 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5288 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: Future Attachments: Apache_CloudStack-4.3.0-Admin_Guide-en-US.pdf -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-3933) [Doc] Document the Global Setting Changes to the s3.enable and swift.enable Parameters
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-3933: Fix Version/s: (was: 4.3.2) Future [Doc] Document the Global Setting Changes to the s3.enable and swift.enable Parameters -- Key: CLOUDSTACK-3933 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3933 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-1441) Document ApiDiscoverService
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-1441: Fix Version/s: (was: 4.3.2) Future Document ApiDiscoverService --- Key: CLOUDSTACK-1441 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1441 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Jessica Tomechak Priority: Minor Labels: api Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-1001) Doc - Hyper V Support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-1001: Fix Version/s: (was: 4.3.2) Future Doc - Hyper V Support - Key: CLOUDSTACK-1001 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1001 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc, Management Server, Template, UI Reporter: Sudha Ponnaganti Assignee: Radhika Nair Fix For: Future Attachments: Apache_CloudStack-4.3.0-Installation_Guide-en-US.pdf Need to document Hyper V Support -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5131) [Doc] Device ID Changes for XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5131: Fix Version/s: (was: 4.3.2) Future [Doc] Device ID Changes for XenServer - Key: CLOUDSTACK-5131 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5131 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-2841) QA: Test RBD cloning, backup and snapshotting
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-2841: Fix Version/s: (was: 4.3.2) Future QA: Test RBD cloning, backup and snapshotting - Key: CLOUDSTACK-2841 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2841 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Snapshot, Storage Controller, Volumes Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Assignee: sadhu suresh Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-878) Document S3-backed Secondary Storage Feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-878: --- Fix Version/s: (was: 4.3.2) Future Document S3-backed Secondary Storage Feature Key: CLOUDSTACK-878 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-878 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Chip Childers Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-946) QA - BigSwitch network plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-946: --- Fix Version/s: (was: 4.3.2) Future QA - BigSwitch network plugin - Key: CLOUDSTACK-946 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-946 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.1.0 Reporter: Sudha Ponnaganti Assignee: Kanzhe Jiang Fix For: Future core tasks that need to be done: - review requirements/FS - upload test plan/test cases - get test cases reviewed - add automation - upload test results - review documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5940) [doc] Publishing Alerts Via CS Root API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5940: Fix Version/s: (was: 4.3.2) Future [doc] Publishing Alerts Via CS Root API --- Key: CLOUDSTACK-5940 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5940 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6377) List templates returns destroyed templates when copying the same template after deleting.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-6377: Summary: List templates returns destroyed templates when copying the same template after deleting. (was: List templates returns destroyed temples when copying the same template after deleting.) List templates returns destroyed templates when copying the same template after deleting. - Key: CLOUDSTACK-6377 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6377 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Management Server Affects Versions: 4.2.0 Reporter: Bharat Kumar Fix For: 4.3.2 steps to reproduce. 1.) copy template from zone A to zone B 2.) delete template form zone B 3.) copy template to zone B again. expected. the list template api should list the template as not destroyed Actual behaviour. Template in zone B is shown as destroyed( even after successful copy). when calling the list templates API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-4934) Rename Limit Resources testcases
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajani Karuturi resolved CLOUDSTACK-4934.
-
Resolution: Fixed
Rename Limit Resources testcases
Key: CLOUDSTACK-4934
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4934
Project: CloudStack
Issue Type: Task
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.2.1, 4.3.0
Reporter: Girish Shilamkar
Assignee: Girish Shilamkar
Priority: Trivial
Fix For: 4.3.2
Limit resources testcases were in
test/integration/component/{cpu_limits/memory_limits} directory and have
common names. Renamed and move them to test/integration/component
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-6377) List templates returns destroyed templates when copying the same template after deleting.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-6377. - Resolution: Fixed List templates returns destroyed templates when copying the same template after deleting. - Key: CLOUDSTACK-6377 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6377 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Management Server Affects Versions: 4.2.0 Reporter: Bharat Kumar Fix For: 4.3.2 steps to reproduce. 1.) copy template from zone A to zone B 2.) delete template form zone B 3.) copy template to zone B again. expected. the list template api should list the template as not destroyed Actual behaviour. Template in zone B is shown as destroyed( even after successful copy). when calling the list templates API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-1466) [Automation] Limit Resources on domains/accounts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-1466. - Resolution: Fixed [Automation] Limit Resources on domains/accounts - Key: CLOUDSTACK-1466 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1466 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.1.0 Reporter: Girish Shilamkar Assignee: Ashutosk Kelkar Priority: Critical Fix For: 4.3.2 Attachments: LimitResourcesTestPlan1.xlsx Automate attached test plan for feature - Limit resources on domain/accounts (cpu/memory/primary storage/secondary storage) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-1478) [DOC] Document baremetal kickstart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-1478: Affects Version/s: 4.3.2 [DOC] Document baremetal kickstart -- Key: CLOUDSTACK-1478 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1478 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.2 Reporter: Jessica Tomechak Priority: Minor Fix For: 4.3.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-1478) [DOC] Document baremetal kickstart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-1478: Fix Version/s: (was: 4.3.2) Future [DOC] Document baremetal kickstart -- Key: CLOUDSTACK-1478 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1478 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.2 Reporter: Jessica Tomechak Priority: Minor Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-1833) Automation: Sanity Marvin tests are checked in by Nitin - Need to Extend it
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-1833. - Resolution: Fixed Automation: Sanity Marvin tests are checked in by Nitin - Need to Extend it --- Key: CLOUDSTACK-1833 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1833 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Assignee: Gaurav Aradhye Priority: Critical Fix For: 4.3.2 Test plan is posted on Wiki -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-631) Create interfaces for Storage Provisioning Plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-631: --- Fix Version/s: (was: 4.3.2) Future Create interfaces for Storage Provisioning Plugin - Key: CLOUDSTACK-631 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-631 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Reporter: Alex Huang Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-632) Start a new VM with the new orchestration
[ https://issues.apache.org/jira/browse/CLOUDSTACK-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-632: --- Fix Version/s: (was: 4.3.2) Future Start a new VM with the new orchestration - Key: CLOUDSTACK-632 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-632 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Reporter: Alex Huang Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-634) Introduce plugins for the provisioning of the snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-634: --- Fix Version/s: (was: 4.3.2) Future Introduce plugins for the provisioning of the snapshots --- Key: CLOUDSTACK-634 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-634 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Reporter: Alex Huang Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-633) Redo the orchestration for snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-633: --- Fix Version/s: (was: 4.3.2) Future Redo the orchestration for snapshots Key: CLOUDSTACK-633 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-633 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Reporter: Alex Huang Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5001) [UI] Cluster details are not getting displayed after completing the Add cluster Task
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5001: Fix Version/s: (was: 4.3.2) Future [UI] Cluster details are not getting displayed after completing the Add cluster Task Key: CLOUDSTACK-5001 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5001 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.1 Reporter: Sailaja Mada Assignee: Brian Federle Fix For: Future Attachments: alllogs.rar, errorsnap1.png Steps: 1. Configure Adv Zone with VMWARE 2. Tried to add one more cluster from the same DataCenter. Observation: 1. AddCluster Task gets completed . But UI does not display the details of the Cluster. 2. We need to go back to Infra page and then list clusters to ensure that it is added. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5000) [UI] UI does not invoke a screen to add second Primary storage if one of the zone does not have any pod
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5000: Fix Version/s: (was: 4.3.2) 4.5.0 [UI] UI does not invoke a screen to add second Primary storage if one of the zone does not have any pod --- Key: CLOUDSTACK-5000 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5000 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.1 Reporter: Sailaja Mada Assignee: Brian Federle Fix For: 4.5.0 Attachments: NoAddPrimarySscreen.png, alllogs.rar Steps: 1. Configure Adv Zone with VMWARE with Zone wide Primary storage 2. In the same setup i have one of the zone Disabled which have no pods and clusters 3. Tried to add one more Primary storage. Observation: UI does not invoke a screen to add second Primary storage if one of the zone does not have any pod -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-4496) [VMWARE]System VM's are failed to start with NPE when host is maitanance state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-4496: Fix Version/s: (was: 4.3.2) 4.5.0 [VMWARE]System VM's are failed to start with NPE when host is maitanance state -- Key: CLOUDSTACK-4496 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4496 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.1 Reporter: Sailaja Mada Assignee: Sateesh Chodapuneedi Fix For: 4.5.0 Attachments: errorlogs.rar Steps: 1. Configure Adv Zone with VMWARE using standard vSwitch (All the traffics are with single with Physical Network) 2. From vCenter, ESXi host is in Maintenance state . 3. System VM's failed to start with NPE when host is maitanance state 2013-08-26 12:40:10,132 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:null) release mem from host: 1, old used: 268435456,reserved: 0, total: 17166258176; new used: 0,reserved:0; movedfromreserved: false,moveToReserveredfalse 2013-08-26 12:40:10,139 WARN [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Exception while trying to start secondary storage vm com.cloud.exception.AgentUnavailableException: Resource [Host:1] is unreachable: Host 1: Unable to start instance due to null at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:981) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:575) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:568) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:267) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:696) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300) at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: java.lang.NullPointerException at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:421) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:543) at com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2526) at com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2582) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:885) ... 20 more 2013-08-26 12:40:10,142 INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Unable to start secondary storage vm for standby capacity, secStorageVm vm Id : 1, will recycle it and start a new one 2013-08-26 12:40:10,143 INFO [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:null) Primary secondary storage is not even started, wait until next turn 2013-08-26 12:40:34,135 DEBUG [storage.image.TemplateDataFactoryImpl] (consoleproxy-1:null) template 8 is already in store:1, type:Primary 2013-08-26 12:40:34,140 DEBUG [storage.volume.VolumeServiceImpl] (consoleproxy-1:null) Found template routing-8 in storage pool 1 with VMTemplateStoragePool id: 2 2013-08-26 12:40:34,156 DEBUG
[jira] [Updated] (CLOUDSTACK-4404) [Doc] Hypervisor Support Matrix for ASFCS 4.2 Features
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-4404: Fix Version/s: (was: 4.3.2) Future [Doc] Hypervisor Support Matrix for ASFCS 4.2 Features -- Key: CLOUDSTACK-4404 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4404 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Reporter: Radhika Nair Assignee: Sudha Ponnaganti Fix For: Future Create a a hypervisor matrix for all the features introduced in ASFCS 4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6307) java.lang.Exception: Uanble to find management port group null
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajani Karuturi updated CLOUDSTACK-6307:
Fix Version/s: (was: 4.3.2)
(was: 4.4.3)
(was: 4.6.0)
java.lang.Exception: Uanble to find management port group null
--
Key: CLOUDSTACK-6307
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6307
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller, VMware
Affects Versions: 4.3.0
Environment: Apache CloudStack 4.3.0 with VMware vSphere 5.5 -
advanced network with vlan tagging, primary and secondary storage are hosted
on NFS
Reporter: ilya musayev
Labels: SSVM, TEMPLATE, VSPHERE
Fix For: 4.5.0
When converting a volume to template, following error is observed on ssvm
cloud.log
2014-03-29 19:08:45,903 DEBUG [cloud.agent.Agent] (Agent-Handler-3:null)
Received response: Seq 10-6933: { Ans: , MgmtId: 345049223690, via: 10, Ver:
v1, Flags: 100010, [{com.cloud.agent.api.PingAnswer:{_
command:{hostType:Storage,hostId:10,wait:0},result:true,wait:0}}]
}
2014-03-29 19:08:46,908 INFO [vmware.util.VmwareContext]
(agentRequest-Handler-5:null) Connected, conn:
sun.net.www.protocol.https.DelegateHttpsURLConnection:https://243.221.84.11/folder/CloudStack-Shell/Clou
dStack-Shell.vmsd?dcPath=Diamond-CICdsName=b0d3033166f3361abea8b85e0efe4055,
retry: 0
2014-03-29 19:08:47,201 INFO [vmware.mo.SnapshotDescriptor]
(agentRequest-Handler-5:null) Parse snapshot file content: .encoding = UTF-8
2014-03-29 19:08:47,202 INFO [vmware.mo.SnapshotDescriptor]
(agentRequest-Handler-5:null) Parse snapshot file content: snapshot.lastUID =
1
2014-03-29 19:08:47,203 INFO [vmware.mo.SnapshotDescriptor]
(agentRequest-Handler-5:null) Parse snapshot file content: snapshot.current =
1
2014-03-29 19:08:47,203 INFO [vmware.mo.SnapshotDescriptor]
(agentRequest-Handler-5:null) Parse snapshot file content: snapshot0.uid = 1
2014-03-29 19:08:47,203 INFO [vmware.mo.SnapshotDescriptor]
(agentRequest-Handler-5:null) Parse snapshot file content: snapshot0.filename
= CloudStack-Shell-Snapshot1.vmsn
2014-03-29 19:08:47,204 INFO [vmware.mo.SnapshotDescriptor]
(agentRequest-Handler-5:null) Parse snapshot file content:
snapshot0.displayName = 2fe485b8b-e9cd-354c-bd4d-d49a05f73252
2014-03-29 19:08:47,204 INFO [vmware.mo.SnapshotDescriptor]
(agentRequest-Handler-5:null) Parse snapshot file content:
snapshot0.description = Temporary snapshot for template creation
2014-03-29 19:08:47,204 INFO [vmware.mo.SnapshotDescriptor]
(agentRequest-Handler-5:null) Parse snapshot file content:
snapshot0.createTimeHigh = 325059
2014-03-29 19:08:47,205 INFO [vmware.mo.SnapshotDescriptor]
(agentRequest-Handler-5:null) Parse snapshot file content:
snapshot0.createTimeLow = -1945658117
2014-03-29 19:08:47,205 INFO [vmware.mo.SnapshotDescriptor]
(agentRequest-Handler-5:null) Parse snapshot file content: snapshot0.numDisks
= 1
2014-03-29 19:08:47,205 INFO [vmware.mo.SnapshotDescriptor]
(agentRequest-Handler-5:null) Parse snapshot file content:
snapshot0.disk0.fileName = ROOT-37.vmdk
2014-03-29 19:08:47,206 INFO [vmware.mo.SnapshotDescriptor]
(agentRequest-Handler-5:null) Parse snapshot file content:
snapshot0.disk0.node = scsi0:0
2014-03-29 19:08:47,206 INFO [vmware.mo.SnapshotDescriptor]
(agentRequest-Handler-5:null) Parse snapshot file content:
snapshot.numSnapshots = 1
2014-03-29 19:08:47,207 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-5:null) Convert snapshot disk file name to datastore
path. ROOT-37.vmdk-[b0d3033166f3361abea8b85e0efe4055]
CloudStack-Shell/ROOT-37.vmdk
2014-03-29 19:08:50,736 INFO [vmware.mo.VirtualMachineMO]
(agentRequest-Handler-5:null) volss: copy vmdk and ovf file starts
1396120130736
2014-03-29 19:08:50,737 INFO [vmware.mo.HypervisorHostHelper]
(agentRequest-Handler-5:null) Resolving host name in url through vCenter,
url:
https://west-diamond-vhv07.corp.company-x.com/nfc/52cb24d3-d48b-9edf-cae1-a35a122e5dfb/disk-0.vmdk
2014-03-29 19:08:50,864 WARN [vmware.mo.HypervisorHostHelper]
(agentRequest-Handler-5:null) Unexpected exception
java.lang.Exception: Uanble to find management port group null
at
com.cloud.hypervisor.vmware.mo.HostMO.getHyperHostNetworkSummary(HostMO.java:981)
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.resolveHostNameInUrl(HypervisorHostHelper.java:1286)
at
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.exportVm(VirtualMachineMO.java:1413)
at
[jira] [Resolved] (CLOUDSTACK-5003) [DOC] Documentation tasks for 4.2.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-5003. - Resolution: Fixed [DOC] Documentation tasks for 4.2.1 --- Key: CLOUDSTACK-5003 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5003 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Abhinandan Prateek Fix For: 4.3.2 This ticket is for following up progress on following items required · Release notes · Admin guide updates - New Features 1. XS VM Snapshots 2. Update VR to use Xen 64 bit template · Known Issues · Fixed issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5123) vmware - mem overprovisioning behaviour
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5123: Fix Version/s: (was: 4.3.2) Future vmware - mem overprovisioning behaviour --- Key: CLOUDSTACK-5123 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5123 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Fix For: Future In case of vmware take the factor from global setting instead of defaulting it to 1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-2402) Document volume snapshot enhancements for VMware
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-2402. - Resolution: Fixed Document volume snapshot enhancements for VMware Key: CLOUDSTACK-2402 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2402 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Reporter: Jessica Tomechak Assignee: Kiran Koneti Priority: Minor Fix For: 4.3.2 Documentation effect is low. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-1561) Document VM snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-1561. - Resolution: Fixed Document VM snapshots - Key: CLOUDSTACK-1561 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1561 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Reporter: Jessica Tomechak Assignee: Chandan Purushothama Priority: Minor Fix For: 4.3.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-833) [DOC] Document increase in VMware 5.1 max cluster size
[ https://issues.apache.org/jira/browse/CLOUDSTACK-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-833: --- Affects Version/s: 4.3.2 [DOC] Document increase in VMware 5.1 max cluster size -- Key: CLOUDSTACK-833 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-833 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.2 Reporter: David Nalley Fix For: 4.3.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-833) [DOC] Document increase in VMware 5.1 max cluster size
[ https://issues.apache.org/jira/browse/CLOUDSTACK-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-833: --- Fix Version/s: (was: 4.3.2) Future [DOC] Document increase in VMware 5.1 max cluster size -- Key: CLOUDSTACK-833 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-833 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.2 Reporter: David Nalley Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-6014) Contrail:MS:syncDomain java.net.ConnectException: Connection refused
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-6014. - Resolution: Fixed Contrail:MS:syncDomain java.net.ConnectException: Connection refused Key: CLOUDSTACK-6014 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6014 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Contrail, Management Server Affects Versions: 4.2.1 Environment: Master with Contrail and Xen Reporter: Parth Jagirdar Assignee: Parth Jagirdar Priority: Critical Fix For: 4.3.2 On a fresh install, Following in seen in MS logs. 2014-01-31 11:35:32,986 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterMonitor-1:ctx-8103e482) Found 0 running routers. 2014-01-31 11:35:32,989 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:ctx-34cc0ed0) Found 0 routers to update status. 2014-01-31 11:35:32,992 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:ctx-34cc0ed0) Found 0 networks to update RvR status. 2014-01-31 11:35:33,877 DEBUG [o.a.c.n.c.m.ContrailManager] (DBSyncTimer:null) DB Sync task is running 2014-01-31 11:35:33,877 DEBUG [o.a.c.n.c.m.ServerDBSync] (DBSyncTimer:null) syncing cloudstack db with vnc 2014-01-31 11:35:33,877 DEBUG [o.a.c.n.c.m.ServerDBSync] (DBSyncTimer:null) sync start: Domain 2014-01-31 11:35:33,881 INFO [n.j.c.a.ApiConnector] (DBSyncTimer:null) http connection localhost, 8082 does not exit 2014-01-31 11:35:33,890 WARN [o.a.c.n.c.m.ServerDBSync] (DBSyncTimer:null) syncDomain java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384) at java.net.Socket.connect(Socket.java:546) at java.net.Socket.connect(Socket.java:495) at java.net.Socket.init(Socket.java:392) at java.net.Socket.init(Socket.java:206) at net.juniper.contrail.api.ApiConnectorImpl.checkConnection(ApiConnectorImpl.java:127) at net.juniper.contrail.api.ApiConnectorImpl.execute(ApiConnectorImpl.java:156) at net.juniper.contrail.api.ApiConnectorImpl.list(ApiConnectorImpl.java:433) at org.apache.cloudstack.network.contrail.management.ServerDBSyncImpl.syncDomain(ServerDBSyncImpl.java:231) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.cloudstack.network.contrail.management.DBSyncGeneric.sync(DBSyncGeneric.java:112) at org.apache.cloudstack.network.contrail.management.ServerDBSyncImpl.syncAll(ServerDBSyncImpl.java:139) at org.apache.cloudstack.network.contrail.management.ContrailManagerImpl.syncNetworkDB(ContrailManagerImpl.java:429) at org.apache.cloudstack.network.contrail.management.ContrailManagerImpl$DBSyncTask.run(ContrailManagerImpl.java:446) at java.util.TimerThread.mainLoop(Timer.java:534) at java.util.TimerThread.run(Timer.java:484) 2014-01-31 11:35:33,891 WARN [o.a.c.n.c.m.ServerDBSync] (DBSyncTimer:null) DB Synchronization java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.cloudstack.network.contrail.management.DBSyncGeneric.sync(DBSyncGeneric.java:112) at org.apache.cloudstack.network.contrail.management.ServerDBSyncImpl.syncAll(ServerDBSyncImpl.java:139) at org.apache.cloudstack.network.contrail.management.ContrailManagerImpl.syncNetworkDB(ContrailManagerImpl.java:429) at org.apache.cloudstack.network.contrail.management.ContrailManagerImpl$DBSyncTask.run(ContrailManagerImpl.java:446) at java.util.TimerThread.mainLoop(Timer.java:534) at java.util.TimerThread.run(Timer.java:484) Caused by:
[jira] [Updated] (CLOUDSTACK-3466) [DOC] VM Migration across VMWARE clusters which are added with different switches(StandardSwith,DVS,Nexus) is not supported
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-3466: Fix Version/s: (was: 4.3.2) Future [DOC] VM Migration across VMWARE clusters which are added with different switches(StandardSwith,DVS,Nexus) is not supported Key: CLOUDSTACK-3466 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3466 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Reporter: Sailaja Mada Assignee: Jessica Tomechak Labels: Releasenotes Fix For: Future Steps: 1. Tried to migrate VM from VMWARE DVS to Stand Vswitch cluster. It failed as host added with standard switch does not have VDS . DVS has cluster scope. Hence migration of VM is supported across cluster with DVS as the backend vswitch. But if another cluster has vswitch as backend then we don’t support migration between those clusters with different backend vswitches This has to be documented . Details of the error log : 2013-07-05 16:08:11,648 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-100:job-243) release mem from host: 6, old used: 536870912,reserved: 0, total: 34346127360; new used: 0,reserved:0; movedfromreserved: false,moveToReserveredfalse 2013-07-05 16:08:11,685 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-100:job-243) Unexpected exception while executing org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd com.cloud.utils.exception.CloudRuntimeException: Failed to migrated vm VM[User|instance2] along with its volumes. com.cloud.utils.exception.CloudRuntimeException: Error while migrating the vm VM[User|instance2] to host Host[-6-Routing]. Exception: java.lang.RuntimeException Message: Network card 'Network adapter 1' has a DVPort backing, which is not supported. This could be because the host does not support VDS or because the host has not joined a VDS. Stack: java.lang.RuntimeException: Network card 'Network adapter 1' has a DVPort backing, which is not supported. This could be because the host does not support VDS or because the host has not joined a VDS. at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290) at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.migrate(VirtualMachineMO.java:329) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3638) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:420) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) at com.cloud.storage.VolumeManagerImpl.migrateVolumes(VolumeManagerImpl.java:2177) at com.cloud.vm.VirtualMachineManagerImpl.migrateWithStorage(VirtualMachineManagerImpl.java:1682) at com.cloud.vm.UserVmManagerImpl.migrateVirtualMachineWithVolume(UserVmManagerImpl.java:4035) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd.execute(MigrateVirtualMachineWithVolumeCmd.java:137) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at
[jira] [Updated] (CLOUDSTACK-5132) [Doc] Support for Acquiring IP Without Enabling SourceNAT Service
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5132: Fix Version/s: (was: 4.3.2) Future [Doc] Support for Acquiring IP Without Enabling SourceNAT Service - Key: CLOUDSTACK-5132 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5132 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-815) Document AWS Style Regions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-815: --- Fix Version/s: (was: 4.3.2) Future Document AWS Style Regions -- Key: CLOUDSTACK-815 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-815 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Sangeetha Hariharan Fix For: Future Document AWS Style Regions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-827) Document new advanced searching capabilities.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-827: --- Fix Version/s: (was: 4.3.2) Future Document new advanced searching capabilities. -- Key: CLOUDSTACK-827 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-827 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: David Nalley Labels: doc Fix For: Future We need to document how the awesome new advanced search capabilities work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-885) Document new storage subsystem
[ https://issues.apache.org/jira/browse/CLOUDSTACK-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-885: --- Fix Version/s: (was: 4.3.2) Future Document new storage subsystem -- Key: CLOUDSTACK-885 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-885 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Chip Childers Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-1077) Fix and move DomainChecker adapter to plugins/acl
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-1077: Fix Version/s: (was: 4.3.2) Future Fix and move DomainChecker adapter to plugins/acl - Key: CLOUDSTACK-1077 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1077 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: API Reporter: Rohit Yadav Fix For: Future DomainChecker ACL adapter plugin is already in place, the task is to fix the plugin and get rid of tightly couple VO class usage with interfaces and fix methods using the same, and move it out of CloudStack to plugins/acl as a plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-2838) Move netscaler to OSS in the default build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-2838: Fix Version/s: (was: 4.3.2) Future Move netscaler to OSS in the default build -- Key: CLOUDSTACK-2838 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2838 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.2.0 Reporter: Prasanna Santhanam Fix For: Future Move the NetScaler build to use the new JARs from maven central and enable it as part of default build -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-1074) Scaling up CPU and RAM for running VMs - KVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-1074: Fix Version/s: (was: 4.3.2) Future Scaling up CPU and RAM for running VMs - KVM Key: CLOUDSTACK-1074 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1074 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Nitin Mehta Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-663) health monitoring for F5 load balanced instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-663: --- Fix Version/s: (was: 4.3.2) Future health monitoring for F5 load balanced instances Key: CLOUDSTACK-663 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-663 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Reporter: Rajesh Battala Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-2868) Document AWS Regions - Issues seen when trying to move a zone from 1 region to another
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-2868: Fix Version/s: (was: 4.3.2) Future Document AWS Regions - Issues seen when trying to move a zone from 1 region to another -- Key: CLOUDSTACK-2868 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2868 Project: CloudStack Issue Type: Sub-task Components: Doc Affects Versions: 4.1.0 Reporter: Jessica Tomechak Fix For: Future Description of the parent bug, CLOUDSTACK-1819, states Fix requires proper documentation to be added. Opening this bug to track that documentation task. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5103) Documentation for DB HA
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5103: Fix Version/s: (was: 4.3.2) Future Documentation for DB HA --- Key: CLOUDSTACK-5103 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5103 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Damodar Reddy T Assignee: Radhika Nair Fix For: Future Please go through https://cwiki.apache.org/confluence/display/CLOUDSTACK/Database+High+Availability+%28DB+HA%29#DatabaseHighAvailability%28DBHA%29-ProposedSolution -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-3298) Documentation for Deploy Virtual Machine Userdata Enhancements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-3298: Fix Version/s: (was: 4.3.2) Future Documentation for Deploy Virtual Machine Userdata Enhancements -- Key: CLOUDSTACK-3298 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3298 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: shweta agarwal Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-1049) provide a way to extract commit sha1 from packages generated on jenkins
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-1049. - Resolution: Fixed provide a way to extract commit sha1 from packages generated on jenkins --- Key: CLOUDSTACK-1049 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1049 Project: CloudStack Issue Type: Wish Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Environment: CloudStack-non-OSS-49-rhel6.3.tar.gz Reporter: Sanjeev N Assignee: Rayees Namathponnan Fix For: 4.3.2 QA environments deployed from jenkins artifacts (rpms, debs) need to have a way to post the commit sha1 of the package. This will help make bug reports faster to track. Packaging should however have a flag to disable this when a release build is made. Downstream distros doing their own packaging shouldn't have to assume they are building from a git tree. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-1253) remove @author tags from codebase
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-1253. - Resolution: Fixed remove @author tags from codebase - Key: CLOUDSTACK-1253 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1253 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Prasanna Santhanam Fix For: 4.3.2 As of Jun 8 2013 (2dc25df62) console-proxy/src/com/cloud/consoleproxy/ConsoleProxyPasswordBasedEncryptor.java: * @author Kelven Yang console-proxy/src/com/cloud/consoleproxy/vnc/packet/client/FramebufferUpdateRequestPacket.java: * @author Volodymyr M. Lisivka engine/api/src/org/apache/cloudstack/engine/cloud/entity/api/BackupEntity.java: * @author ahuang engine/api/src/org/apache/cloudstack/engine/cloud/entity/api/NicEntity.java: * @author ahuang engine/storage/integration-test/test/org/apache/cloudstack/storage/test/StorageFactoryBean.java: * @author Mattias Severson, Jayway plugins/hypervisors/baremetal/resources/security_group_agent/security_group_agent/cs_sg_agent.py:@author: frank plugins/hypervisors/baremetal/resources/security_group_agent/security_group_agent/xmlobject.py:@author: Frank plugins/network-elements/dns-notifier/src/org/apache/cloudstack/network/element/DnsNotifier.java: * @author ahuang scripts/network/ping/baremetal_user_data.py:@author: frank Some of the following have been resolved: As of Feb 8: (f65ba4) api/src/com/cloud/exception/RequestLimitException.java: * @author minc api/src/org/apache/cloudstack/api/ApiErrorCode.java: * @author minc api/src/org/apache/cloudstack/query/QueryService.java: * @author minc awsapi/src/com/cloud/bridge/io/DimeDelimitedInputStream.java: * @author Rick Rineholt console-proxy/src/com/cloud/consoleproxy/vnc/packet/client/FramebufferUpdateRequestPacket.java: * @author Volodymyr M. Lisivka deps/XenServerJava/src/com/xensource/xenapi/Auth.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Blob.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Bond.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Console.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Crashdump.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/DRTask.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/DataSource.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Event.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/GPUGroup.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Host.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/HostCpu.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/HostCrashdump.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/HostMetrics.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/HostPatch.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Message.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Network.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/PBD.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/PCI.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/PGPU.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/PIF.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/PIFMetrics.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Pool.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/PoolPatch.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Role.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/SM.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/SR.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Secret.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Session.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Subject.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Task.java: * @author Citrix Systems, Inc. deps/XenServerJava/src/com/xensource/xenapi/Tunnel.java: * @author Citrix Systems, Inc.
[jira] [Resolved] (CLOUDSTACK-6927) Security group python script has several issues
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-6927. - Resolution: Fixed Security group python script has several issues --- Key: CLOUDSTACK-6927 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6927 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.4.0, 4.3.1 Reporter: sebastien goasguen Fix For: 4.3.2 -virtual router is not cleaned up properly from iptables -routes are not cleaned up properly if needed -not using python list to store results of virsh list. -there can be duplicates in cleanup list - -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-382) Install Guide: Network Type Descriptions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-382. Resolution: Fixed Install Guide: Network Type Descriptions Key: CLOUDSTACK-382 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-382 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: pre-4.0.0 Reporter: Chip Childers Priority: Minor Fix For: 4.3.2 In the install guide, Section 2.7.2 (Basic Zone Network Traffic Types) and 2.7.4 (Advanced Zone Network Traffic Types) both describe a traffic type of Storage. This is confusing, since it really only means secondary storage. Should we change this label? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-4890) [VM snapshot] Do not delete VM snapshots until VM is expunged. Currently after VM is restored, unable to recover VM snapshots as these are destroyed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-4890: Fix Version/s: (was: 4.3.2) 4.5.0 [VM snapshot] Do not delete VM snapshots until VM is expunged. Currently after VM is restored, unable to recover VM snapshots as these are destroyed Key: CLOUDSTACK-4890 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4890 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.1 Environment: MSCloudPlatform-4.2.1-732-rhel6.3.tar.gz Hosts XS 6.2 Reporter: angeline shen Priority: Minor Fix For: 4.5.0 1. Create multiple VM snapshots for the same VM - say 3 snapshots - S1,S2,S3. 2. Destroy the Vm. 3. Restore VM. All VM snapshots are removed. It would be nice to be able to recover VM snapshots when VM is restored . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
