[jira] [Commented] (CLOUDSTACK-7747) VM Snapshot - Support only for vm revert cases that will not result in VM state change
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215907#comment-14215907 ] ASF subversion and git services commented on CLOUDSTACK-7747: - Commit f43ffb9a0f71f380f896e1e5c581725e9c08faab in cloudstack's branch refs/heads/4.5 from [~anshulg] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f43ffb9 ] CLOUDSTACK-7688, CLOUDSTACK-7747: restricted various operations for VM with VM snapshots which breaks VM snapshots. Now they are informed that they cannot perform the operation. To perform operation they have to remove VM snapshots of VM. > VM Snapshot - Support only for vm revert cases that will not result in VM > state change > -- > > Key: CLOUDSTACK-7747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7747 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar >Priority: Critical > > Currently we extend support for all the possible combinations .In cases were > the Vm start changes from “Stopped” to “Running”, CS does not account for > this VM’s capacity and VM start does not use our allocators. > Following will be the only configuration we would have to support: > 1.Revert a "Running" VM to a "Disk and Memory" Snapshot ( with and without > "quiesce" option). > 1.Revert a "Stopped" VM to a "Disk " Snapshot ( with and without "quiesce" > option). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7747) VM Snapshot - Support only for vm revert cases that will not result in VM state change
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234233#comment-14234233 ] ASF subversion and git services commented on CLOUDSTACK-7747: - Commit 08e5993a45c54926f8707e86b1ffad94b3e29a51 in cloudstack's branch refs/heads/4.3 from [~anshulg] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=08e5993 ] CLOUDSTACK-7688, CLOUDSTACK-7747: restricted various operations for VM with VM snapshots which breaks VM snapshots. Now they are informed that they cannot perform the operation. To perform operation they have to remove VM snapshots of VM. (cherry picked from commit f43ffb9a0f71f380f896e1e5c581725e9c08faab) Signed-off-by: Rohit Yadav Conflicts: server/src/com/cloud/storage/VolumeApiServiceImpl.java server/src/com/cloud/vm/UserVmManagerImpl.java server/src/com/cloud/vm/snapshot/VMSnapshotManagerImpl.java > VM Snapshot - Support only for vm revert cases that will not result in VM > state change > -- > > Key: CLOUDSTACK-7747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7747 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar >Priority: Critical > > Currently we extend support for all the possible combinations .In cases were > the Vm start changes from “Stopped” to “Running”, CS does not account for > this VM’s capacity and VM start does not use our allocators. > Following will be the only configuration we would have to support: > 1.Revert a "Running" VM to a "Disk and Memory" Snapshot ( with and without > "quiesce" option). > 1.Revert a "Stopped" VM to a "Disk " Snapshot ( with and without "quiesce" > option). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7747) VM Snapshot - Support only for vm revert cases that will not result in VM state change
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189864#comment-14189864 ] ASF subversion and git services commented on CLOUDSTACK-7747: - Commit 62f9bf0fff99746cf91f4ac9d6c2abfa3edaa6c5 in cloudstack's branch refs/heads/master from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=62f9bf0 ] PR #26 CLOUDSTACK-7688, CLOUDSTACK-7747 Restricted various operations for VM with VM Snapshots #26 This closes #26 > VM Snapshot - Support only for vm revert cases that will not result in VM > state change > -- > > Key: CLOUDSTACK-7747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7747 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar >Priority: Critical > > Currently we extend support for all the possible combinations .In cases were > the Vm start changes from “Stopped” to “Running”, CS does not account for > this VM’s capacity and VM start does not use our allocators. > Following will be the only configuration we would have to support: > 1.Revert a "Running" VM to a "Disk and Memory" Snapshot ( with and without > "quiesce" option). > 1.Revert a "Stopped" VM to a "Disk " Snapshot ( with and without "quiesce" > option). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
