mirror of https://github.com/apache/cloudstack.git
e303baa1bf
CLOUDSTACK-9738: [Vmware] Optimize vm expunge process for instances with vm snapshots## 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 ## Use cases 1. deleteVMsnapohsot-> no changes to current behavior 2. 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 3. destroyVM with expunge=true: * Vmsnaphsot is marked with removed timestamp and state = Expunging in DB * VM is deleted in HW * pr/1905: CLOUDSTACK-9738: [Vmware] Optimize vm expunge process for instances with vm snapshots Signed-off-by: Rajani Karuturi <rajani.karuturi@accelerite.com> |
||
|---|---|---|
| .. | ||
| alert | ||
| api | ||
| capacity | ||
| configuration | ||
| consoleproxy | ||
| event | ||
| ha | ||
| keystore | ||
| metadata | ||
| network | ||
| projects | ||
| resource | ||
| resourcelimit | ||
| server | ||
| servlet | ||
| snapshot | ||
| storage | ||
| template | ||
| user | ||
| vm | ||
| vpc | ||