olivierlemasle commented on issue #4982: URL: https://github.com/apache/cloudstack/issues/4982#issuecomment-833805201
Actually, the bug is to sum the backup sizes over the time frame. I think that what I've called the **Option 1** (cf above) is the best way to handle backup usages. In that option, the usage value is the duration (in hours) over the time frame. This is **aligned with other storage usage types in CloudStack** (volumes, ISOs, templates, snapshots). For all these usage types, the size of the volume/ISO/template/snapshot is displayed in "size", and the duration is displayed "raw_usage" / "usage_display". The **Option 2** is less accurate. E.g. it does not show that from 14:00:00 to 14:59:59, the VM was assigned to the backup offering during only half the time. However, this option is also less a breaking change. It consists of just using as the "size" the last known size over the time frame. I really think these options should be discussed before we implement any change. I would prefer the Option 1 but I'm interested to hear your opinion / the opinion of the community. On a side node, you wrote: > ... before removing the offering from the VM and reassigning **another** backup offering ... It may not be important, but in my scenario above, the VM was re-assigned to the *same* backup offering. This is not a far-fetched scenario: actually, removing the backup offering and re-assigning the VM to the backup offering is the only way to attach or detach a volume to the VM. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
