← Back to team overview

openstack team mailing list archive

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

 

This only relates to SystemUsageData?

Or is the thought that we're getting rid of the idea of Projects all together with Keystone?

On Jun 2, 2011, at 11:43 AM, Glen Campbell wrote:

> Yeah, originally we had thought that Account != Project, but I believe
> we've since changed to thinking that they're equivalent. Are you going to
> update the spec, or would you like me to?
> 
> FYI, Monsyne Dragon has done a bit of work on some of this already; you
> may want to sync with him for the current status.
> 
> 
> 
> 
> 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
>> 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@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.
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp



Follow ups

References