When defining a price list, inputs are currently limited to 2 decimal places, while calculations use many more.
Due to the fact that pricing is defined in specific units, it should be beneficial to watch and define pricing with as many decimal places as necessary.
It should also be possible to define pricing based on different measures:
- For instance, it should be possible to define 5 GB / month, or 5 MB/month (not 0.005 GB/month). For that it should be possible to select the measure that is used to define the currency input (even if the calculation are always made in the measurement of the input)
- As a first step, it should be possible to define that as a configuration help only. Months will be considered of 30 days 720 hours, and will not consider the different lengths of months.
- In a second step, charges will be consistent. If you define a monthly rate and you use the resources, you get exactly that price (i.e. if you define $5/month/CPU and you use 1 CPU continuously, you get a price of 5$ indepedentnly of whether the month is 28, 29, 30 or 31 days long)