rssLink RSS for all categories
 
icon_red
icon_green
icon_red
icon_red
icon_blue
icon_green
icon_green
icon_red
icon_red
icon_red
icon_orange
icon_green
icon_green
icon_green
icon_green
icon_blue
icon_green
icon_orange
icon_red
icon_green
icon_red
icon_red
icon_green
icon_red
icon_red
icon_red
icon_red
icon_orange
icon_green
 

FS#12739 — FS#17621 — Object Storage bandwidth billing

Attached to Project— Cloud
Incident
Cloud
CLOSED
100%
At the beginning of each month, we are launching the Public Cloud billing to retrospectively pay the resources consumed during the previous month. While billing the consumption of February (billing launched in early March), we faced the limits of the billing code as it was developed so far. Indeed, we are based on a set of stored procedures within a PGSQL to perform aggregation and billing processing. However, the process showed very long, more than 5 minutes per customer.
We then decided to completely rewrite the way we store data and how we may charge to go on a more flexible solution which easily allows processing, thanks specifically to a partitionning of our data and the code rewriting in Go! language.
During the rewriting process, we realized that the way we have been charging the Object Storage bandwidth so far is incorrect. We are charging average amounts between 2 and 6 times lower than the actual consumption of the customer.
The solution to this problem could be raising the price of your Public Cloud invoice compared to previous months. Some customers have also showed us inconsistencies in the visualization of consumption of bandwidth in the manager v6. This visualization still uses some of the code from the old billing model. We are currently completing the migration of the display code, so you can find the moment to find a difference between your actual consumption and consumption presented in your client manager.
Date:  Sunday, 29 May 2016, 23:16PM
Reason for closing:  Done