openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #10427
Re: Monitoring / Billing Architecture proposed
Doug,
Do we mirror the table structure of nova, etc. and add created/modified columns?
Or do we flatten into an instance event record with everything?
Bran
-------------------------------------------------
Brian Schott, CTO
Nimbis Services, Inc.
brian.schott@xxxxxxxxxxxxxxxxxx
ph: 443-274-6064 fx: 443-274-6060
On Apr 23, 2012, at 3:23 PM, Doug Hellmann wrote:
>
>
> On Mon, Apr 23, 2012 at 1:50 PM, Brian Schott <brian.schott@xxxxxxxxxxxxxxxxxx> wrote:
> So, we could build on this. No reason to reinvent, but we might want to expand the number of events. I'm concerned about things like what happens when flavors change over time. Maybe the answer is, always append to the flavor/instance-type table. The code I remember and the admin interface that Ken wrote allowed you to modify flavors. That would break billing unless you also track flavor modifications.
>
> That seems like a situation where you would want to denormalize the billing database and record the flavor details along with the rest of the creation event data.
>
> Doug
>
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
Follow ups
References