cloudstack/engine/storage
Rohit Yadav 491a10be0c
storage: publish delete usage event for snapshot deletion (#3212)
Problem: Users are billed for destroyed VMs with VM snapshots because usage records don't get that the VM and VM snapshots are removed.
Root Cause: The destroyVirtualMachine and expungeVirtualMachine APIs were removing VM snapshots but not generating VMSNAPSHOT.DELETE usage event due to which the VM snapshots were not marked as removed in the usage_vmsnapshot table.
Solution: The issue was fixed by emitting the proper usage event for all the VM snapshots of a VM that is destroyed.
2019-04-10 17:12:55 +05:30
..
cache Updating pom.xml version numbers for release 4.13.0.0-SNAPSHOT 2019-03-20 18:47:35 -03:00
configdrive Updating pom.xml version numbers for release 4.13.0.0-SNAPSHOT 2019-03-20 18:47:35 -03:00
datamotion Updating pom.xml version numbers for release 4.13.0.0-SNAPSHOT 2019-03-20 18:47:35 -03:00
image Updating pom.xml version numbers for release 4.13.0.0-SNAPSHOT 2019-03-20 18:47:35 -03:00
integration-test Updating pom.xml version numbers for release 4.13.0.0-SNAPSHOT 2019-03-20 18:47:35 -03:00
snapshot storage: publish delete usage event for snapshot deletion (#3212) 2019-04-10 17:12:55 +05:30
src server: remove unused StrategyPriority.PLUGIN. (#3014) 2018-11-14 15:07:37 +05:30
volume Updating pom.xml version numbers for release 4.13.0.0-SNAPSHOT 2019-03-20 18:47:35 -03:00
pom.xml Updating pom.xml version numbers for release 4.13.0.0-SNAPSHOT 2019-03-20 18:47:35 -03:00
storage.ucls CLOUDSTACK-10105: Use maven standard project structure in all projects (#2283) 2018-01-20 03:19:27 +05:30