As you would know, Abiquo has the capacity to account any resource allocated and used by users in order to allow cloud providers to generate bills using their billing systems or using an Abiquo billing connector.
Accounting data is obviously one of the key parts of the product because it’s valuable data that tells Abiquo customers exactly how their users are consuming cloud resources in the platform.
As in other parts of the product, the engineering team are using information received from customers and labs in order to improve scalability. And accounting is a critical part of the platform because as the platform grows, the data generated keeps growing every hour/day/week, so the processes that consolidate the data need to have a very good response time.
In Abiquo EE 2.2 we have reviewed this processes and we have improved a lot the performance numbers measured in previous releases.
The following points sumarize the enhancements of this improvement:
- Improved security: separate ‘kinton_accounting’ schema to hold the new accounting tables and views so accounting queries do not access the main Abiquo schema
- Improved storage efficiency: saves 50-75% of space used by the pre-upgrade accounting table
- Improved VIEW performance: greatly improved query performance on large accounting tables
- Improved recovery handling: you can now recover missed accounting periods
This diagram is an overview of the Abiquo 2.0 accounting system. The accounting tables are part of the kinton schema.
After the upgrade to Abiquo 2.2, the accounting tables are now part of the kinton_accounting schema, as shown with the darker orange and green boxes in the following diagram.
After the upgrade, by default the system will retain accounting data for 90 days. You can manually recover missed accounting periods.
You should now access accounting data using the template queries in the new accounting schema.
Finally… I think that seeing a comparison is better than more words in this post.
Enjoy your bills! 😉