Open Stack

IMHO, if it is a quota related to a tenant or user, then managing it in
Keystone makes sense.

Jason

-----Original Message-----
From: openstack-bounces+jason.rouault=hp.com at lists.launchpad.net
[mailto:openstack-bounces+jason.rouault=hp.com at lists.launchpad.net] On
Behalf Of Eoghan Glynn
Sent: Friday, May 04, 2012 3:11 AM
To: Endre Karlson
Cc: openstack at lists.launchpad.net
Subject: Re: [Openstack] [Swift][Keystone] Swift Quotas



> Should you mix this into Keystone ? Seems kind of wrong to mix 
> identity manager with Quotas?


This was discussed at several sessions the design summit, so I brought it up
at the keystone 'state of the nation' session to get a feel for the keystone
community's disposition to the idea.

There was in-principle agreement that storing such data in the keystone
backend is a reasonable approach (well, no strong objections in any case).

The idea is that the determining if a user is over-quota is related to
authorization in the sense that it determines whether a user normally
authorized to consume a resource is allowed to do so in this particular
case.

>From an implementation point, it would also aid greatly in allowing
the nova quotas infrastructure to be promoted to openstack-common and hence
be reused by other projects such as glance.

Cheers,
Eoghan

_______________________________________________
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4854 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120504/db654673/attachment.bin>