Open Stack

Thanks Everett!

So, does this mean that nova continue to store quotas assigned to projects as well as keystone? Meaning they will be duplicated?

Thanks again!
Glaucimar Aguiar


From: Everett Toews [mailto:everett.toews at RACKSPACE.COM]
Sent: quarta-feira, 28 de novembro de 2012 18:55
To: Aguiar, Glaucimar (Brazil R&D-ECL); openstack at lists.launchpad.net
Subject: Re: [Openstack] Quota classes, Store quota data relation

Store Quota Data (in Keystone) is only intended to be a very simple way to store quotas centrally. It is not related to quota classes and there are no plans to do so.

That blueprint came out of a use case to have quotas in Swift. However, Swift doesn't store any user/tenant/project data so it was moved to Keystone. The idea being that you could write Swift middleware to check the quotas in Keystone before performing some operation.

Regards,
Everett

From: <Aguiar>, "Glaucimar (Brazil R&D-ECL)" <glaucimar.aguiar at hp.com<mailto:glaucimar.aguiar at hp.com>>
Date: Wednesday, November 28, 2012 2:36 PM
To: "openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>" <openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>>
Subject: [Openstack] Quota classes, Store quota data relation

Hi,

I am trying to understand the relation of quota classes' implementation (which I understand as unfinished) with the https://blueprints.launchpad.net/keystone/+spec/store-quota-data blueprint, if any.
Per my understanding the implementation of StoreQuotaData and the movement of services to use this central repository require the implementation of quota classes in nova to be also moved to this centralized location. Are there plans on this area?

Thanks for clarifications or help in better understand this relationship.

Glaucimar Aguiar

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121128/271154cc/attachment.html>