← Back to team overview

openstack team mailing list archive

Re: Updating SystemUsageData blueprint w.r.t. accounts/tenants


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@xxxxxxxxx> 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
>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
>I'd like to clarify this so I can update the blueprint.  (or
>alternatively clarify how tenants/users and ... work)
>Mailing list: https://launchpad.net/~openstack
>Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>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@xxxxxxxxxxxxx, and delete the original message.
Your cooperation is appreciated.

Follow ups