Hi, I see three ways to approach storage billing:
- Bill according to the available storage (limit set in the quotas). - Bill the storage used by the running VMs. This was not possible before 4.4, the DISK/SIZE was added for the storage scheduling. Now you can do this: $ oneacct -u 0 -x | xpath -e "/HISTORY_RECORDS/HISTORY/VM/TEMPLATE/DISK/SIZE" - Bill the DS usage. This usage is tracked in the user quotas, but we don't keep a history for the changes made here. You could create a script to store the user quotas information in a database with a timestamp, and trigger it with a hook [1] on image create and image remove. Regards [1] http://docs.opennebula.org/stable/integration/infrastructure_integration/hooks.html -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula<http://twitter.com/opennebula><cmar...@opennebula.org> On Sat, Jan 25, 2014 at 11:53 PM, ML mail <mlnos...@yahoo.com> wrote: > Hello, > > I was checking the oneacct tool and I noticed that there is no accounting > of the storage used by a user. Am I missing something? > > How does someone bill the storage usage (OS, DATABLOCK, etc) of a customer > on a hourly rate for example? > > Regards, > M.L. > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org