Open Stack

The other decision we've made is that Nova will not do any aggregation.
Instead, the plan is to treat usage data as a notification and pipe it
into the notification message queue. This will allow cloud administrators
to set up external handlers to do their own aggregation, especially since
aggregation by tenant could easily span multiple zones.

In Rackspace's case, we have an internal component that is reading the
notification message queues and converting the data into ATOM format for
consumption by external services like billing and monitoring databases.





On 5/27/11 7:04 PM, "Ziad Sawalha" <ziad.sawalha at rackspace.com> wrote:

>Project is indeed the equivalent of tenant.
>
>The multi-tenant-accounting blueprint says usage must be TAGGED with the
>tenant so that an operator can map and aggregate usage as is appropriate
>for their own business logic.
>
>If we aggregate by tenant, we just need ton recognize that there may
>eventually be a use case where an operator needs the data pre-aggregation.
>
>
>On 5/27/11 6:46 PM, "Jesse Andrews" <anotherjesse at gmail.com> wrote:
>
>>A few of us were looking at starting to implement
>>http://wiki.openstack.org/SystemUsageData, starting with updating the
>>spec to reflect plans related to unified auth (the keystone project).
>>
>>In the blueprint, it was called out that data was to be aggregated by
>>Account ID - which it claimed is NOT the same as a project.
>>
>>My understanding of how unified auth will work is:
>>
>>   Nova will be sent a Tenant, User, Roles/Groups from the auth_token
>>middleware
>>
>>If this is so, accounts (things that bind many tenants together) would
>>exist outside of nova, so this level of aggregation (multiple tenants
>>into an account) would occur in an external billing system, not in
>>Nova.
>>
>>I'd like to clarify this so I can update the blueprint.  (or
>>alternatively clarify how tenants/users and ... work)
>>
>>Thanks,
>>Jesse
>>
>>_______________________________________________
>>Mailing list: https://launchpad.net/~openstack
>>Post to     : openstack at lists.launchpad.net
>>Unsubscribe : https://launchpad.net/~openstack
>>More help   : https://help.launchpad.net/ListHelp
>
>
>
>Confidentiality Notice: This e-mail message (including any attached or
>embedded documents) is intended for the exclusive and confidential use of
>the
>individual or entity to which this message is addressed, and unless
>otherwise
>expressly indicated, is confidential and privileged information of
>Rackspace.
>Any dissemination, distribution or copying of the enclosed material is
>prohibited.
>If you receive this transmission in error, please notify us immediately
>by e-mail
>at abuse at rackspace.com, and delete the original message.
>Your cooperation is appreciated.
>
>
>_______________________________________________
>Mailing list: https://launchpad.net/~openstack
>Post to     : openstack at lists.launchpad.net
>Unsubscribe : https://launchpad.net/~openstack
>More help   : https://help.launchpad.net/ListHelp