Add Option to Use Base 10 for Quota Warnings

[jarulsamy]

My institution uses base 10 for all storage quotas. When quotas are calculated from our storage system, we convert the raw quota from bytes to KiB by dividing by 1024 to generate the JSON file for OOD quota warnings. However, this leads to misleading discrepancies between our internal quota reporting for billing (which uses base 10) and OOD.

Also, it is worth mentioning that the quota warnings displayed within OOD are suffixed with KB, MB, GB, etc. are calculated based on 1024 bytes per KB, 1024 KB per MB and so on. These are also generally referred to as Kibibytes (KiB), Mibibytes (MiB) and so on[1] while the metric variants (base 10) are referred to as -byte to avoid ambiguity. Unfortunately, there are three competing standards for this, Metric, IEC, and JEDEC, so some feedback on which standards to follow would be appreciated.

I propose that we:

• Add an option to use base 10 instead of base 2 for the block calculations.
• Use the correct suffix depending on the base. [K,M,G,T,P]iB for base 2, [K,M,G,T,P]B for base 10.

[1] - SI and international standard IEC 80000-13 consider base 2 as -bibyte - https://en.wikipedia.org/wiki/Byte#Multiple-byte_units

[johrstrom]

Hi, sorry for not commenting on this sooner.

I propose that we:
Add an option to use base 10 instead of base 2 for the block calculations.
Use the correct suffix depending on the base. [K,M,G,T,P]iB for base 2, [K,M,G,T,P]B for base 10.

Yea, I think you're right. We can definitely correct the suffix soon and adding an option for base 10 sounds reasonable.