[
https://issues.apache.org/jira/browse/CLOUDSTACK-9738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15842687#comment-15842687
]
rashmidixit commented on CLOUDSTACK-9738:
-----------------------------------------
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1905
@rhtyd @karuturi Can we run tests on this PR and merge on success ?
---
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 infrastruct...@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)
