You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Abhinandan Prateek (JIRA)" <ji...@apache.org> on 2013/10/31 06:22:25 UTC

[jira] [Updated] (CLOUDSTACK-4894) [UI] destroyVm API: add support to force expunge the vm immediately

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abhinandan Prateek updated CLOUDSTACK-4894:
-------------------------------------------

    Summary: [UI] destroyVm API: add support to force expunge the vm immediately   (was: destroyVm API: add support to force expunge the vm immediately )

> [UI] 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: API, UI
>    Affects Versions: 4.2.0
>            Reporter: Alena Prokharchyk
>            Assignee: Sonny Chhen
>             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)