measure TU as part of the billable items - Githubissues

0-complexity / openvcloud

OpenvCloud

Other

2 stars 4 forks source link

measure TU as part of the billable items #1854

Open hofkensj opened 5 years ago

hofkensj commented 5 years ago

Detailed description

As part of the billable items (and in the billing files) we need to take care of TU's.

TU's were now very difficult to calculate since they were a combination of SSD Storage Cache used and an amount of IOPS.

We have decided to take that complexity out and reduce it to a very simple calculation. It is 400 IOPS (4x oversubscribed) - based on 4k blocks

Now we need to make sure that this can be measured/reported and restricted at account level.

Changes needed

[ ] report TU in billing files (per account / vdc / vm / disk) - TU's can be portions of TU (not integer numbers needed, TU is based on configured not)
[ ] be able to restrict accounts and VDC per TU/SU/NU and CU
[ ] recalculate the "other" restrictions/QoS per disk in TU as well - so all format it back to amount of 4k / 80r-20w block IOPS

wvandebroeck commented 5 years ago

Add reporting in the admin portal on the CU-SU-TU-NU, add the same overview in the end user portal per VDC and per account.