Yep, storing the quota info is all I'm trying to achieve with Keystone. For Swift, the enforcement would happen within Swift (middleware).
I see it as being roughly analogous to roles in Keystone. The roles are stored in Keystone but enforced by the individual projects. Everett On Fri, May 4, 2012 at 10:02 AM, Jay Pipes <jaypi...@gmail.com> wrote: > On 05/04/2012 10:14 AM, Rouault, Jason (Cloud Services) wrote: > >> IMHO, if it is a quota related to a tenant or user, then managing it in >> Keystone makes sense. >> > > I think, as Eoghan mentioned, there was pretty broad agreement that > *storing* quota information and even the CRUD operations on it were > appropriate for Keystone to do, but the actual enforcement of quotas should > be left in individual projects. > > Best, > -jay > > > ______________________________**_________________ > Mailing list: > https://launchpad.net/~**openstack<https://launchpad.net/~openstack> > Post to : openstack@lists.launchpad.net > Unsubscribe : > https://launchpad.net/~**openstack<https://launchpad.net/~openstack> > More help : > https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp> >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
