cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9738) Optimize vm expunge process for instances with vm snapshots
Date Tue, 07 Feb 2017 02:11:41 GMT


ASF GitHub Bot commented on CLOUDSTACK-9738:

Github user nvazquez commented on the issue:
    @karuturi regarding tests done, we've compared the number of delete tasks sent to Vmware
hypervisor on expunging a vm with `N` vm snapshots before and after this optimization, reducing
from `N+1` tasks to only `1`. Is a marvin test required for this case?

> Optimize vm expunge process for instances with vm snapshots
> -----------------------------------------------------------
>                 Key: CLOUDSTACK-9738
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions:
>            Reporter: Nicolas Vazquez
>            Assignee: Nicolas Vazquez
>             Fix For:
> h2. Description
> It was noticed that expunging instances with many vm snapshots took a look of time, as
hypervisor received as many tasks as vm snapshots instance had, apart from the delete vm task.
We propose a way to optimize this process for instances with vm snapshots by sending only
one delete task to hypervisor, which will delete vm and its snapshots
> h2. Use cases
> # deleteVMsnapohsot-> no changes to current behavior
> # destroyVM with expunge=false ->  no actions to VMsnaphsot is performed at the moment.
When VM cleanup thread is executed it will perform the same sequence as #3. If instance is
recovered before expunged by the cleanup thread it will remain intact with VMSnapshot chain
> # destroyVM with expunge=true:
> #*       Vmsnaphsot is  marked with removed timestamp and state = Expunging in DB
> #*       VM is deleted in HW

This message was sent by Atlassian JIRA

View raw message