[
https://issues.apache.org/jira/browse/CLOUDSTACK-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800903#comment-13800903
]
ASF subversion and git services commented on CLOUDSTACK-4894:
-------------------------------------------------------------
Commit 25d6e6ec66b141fe728d68062ff04a74615fb310 in branch refs/heads/master
from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=25d6e6e ]
CLOUDSTACK-4894: DestroyVirtualMachine API - added "expunge" admin-only
parameter. When passed as true, the vm gets expunged immediately (false by
default to preserve the initial command behavior)
Conflicts:
api/src/org/apache/cloudstack/api/ApiConstants.java
api/src/org/apache/cloudstack/api/command/user/vm/DestroyVMCmd.java
> destroyVm API: add support to force expunge the vm immediately
> ---------------------------------------------------------------
>
> Key: CLOUDSTACK-4894
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4894
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: Alena Prokharchyk
> Assignee: Alena Prokharchyk
> Fix For: 4.2.1
>
>
> When destroyVM API is called, the vm gets destroyed only in the DB. The
> actual expunge is being taken care later on by expunge thread (configured
> using expunge.interval and expunge.delay params). As we keep on getting the
> requests on adding a support for forceful expunge - when vm is expunged
> immediately after the call is made - it would make sense to introduce some
> flag to destroyVm command, controlling the behavior.
> So destroyVm will get new parameter - expunge (boolean, false by default).
> When true is passed as a value, the vm will be expunged right away.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
