openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #11322
Re: [Metering] schema and counter definitions
On Mon, May 7, 2012 at 5:21 PM, Loic Dachary <loic@xxxxxxxxxxxx> wrote:
> Hi Tomasz,
Hi
>
> I could not agree more and this is the reason why I/O shows in the list of meters shown in http://wiki.openstack.org/EfficientMetering (c5) "disk IO in megabyte per second has a high impact on the service availability and could be billed separately ".
Yes but for disk drives I/O (number of read/write ops) are the key
resource usage information. It's very hard to setup a billing model
for disk drive usage on bandwidth as low bandwidth disk operations
(small random read/writes) can utilize disk drive more than huge
sequential reads/writes. I need also to mention that AWS is also
charging for I/O in their volume service.
>
>
> It looks like you already have a codebase that could be useful for the metering implementation. Would you be willing to share it ?
Yes. Just give me few days.
--
Tomasz Paszkowski
SS7, Asterisk, SAN, Datacenter, Cloud Computing
+48500166299
Follow ups
References