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 Wed, 18 Jan 2017 17:50:27 GMT


ASF GitHub Bot commented on CLOUDSTACK-9738:

Github user nvazquez commented on the issue:
    Hi @ozhanrk, 
    In this PR, vm snapshots get deleted when the instance gets deleted from hypervisor, on
task sent by the vm cleanup thread. Can it be possible that you were referring to volume snapshots
instead of vm snapshots for restoring vms?

> 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