cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4894) destroyVm API: add support to force expunge the vm immediately
Date Mon, 21 Oct 2013 18:14:44 GMT


Alena Prokharchyk commented on CLOUDSTACK-4894:

The API is fixed with 2e75e8ced0a9d7c59e39dbfececb50fcc9e13f6a. Reassigning to the UI folks.

For UI: the destroyVm command got one new parameter "expunge" - available for root/domain
admins only. So only root/domain admin UI should be fixed. On destroy vm dialog, add a checkbox
"expunge" (unchecked by default). Note that when expunge=true is passed to the call, no object
is returned in the queryAsyncJobResult response as the vm will be gone from the DB.

> destroyVm API: add support to force expunge the vm immediately 
> ---------------------------------------------------------------
>                 Key: CLOUDSTACK-4894
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    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

View raw message