cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "rashmidixit (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9738) Optimize vm expunge process for instances with vm snapshots
Date Mon, 16 Jan 2017 06:07:27 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823505#comment-15823505
] 

rashmidixit commented on CLOUDSTACK-9738:
-----------------------------------------

Github user ozhanrk commented on the issue:

    https://github.com/apache/cloudstack/pull/1905
  
    Hi, we currently hold vm snapshots like as vm backup, even if we destroy vm with expunge.
So that we could restore vm snapshot on future time. Does this pr has any effect on our scenario?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---


> Optimize vm expunge process for instances with vm snapshots
> -----------------------------------------------------------
>
>                 Key: CLOUDSTACK-9738
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9738
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.10.0.0
>            Reporter: Nicolas Vazquez
>            Assignee: Nicolas Vazquez
>             Fix For: 4.10.0.0
>
>
> 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
present
> # 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
(v6.3.4#6332)

Mime
View raw message