[Openstack] Keystone Centralized Quota Management

Dmitry Stepanenko dstepanenko at mirantis.com
Mon Aug 19 06:54:40 UTC 2013

While working on store-quota-data blueprint (
https://blueprints.launchpad.net/keystone/+spec/store-quota-data) in the
step of discussing appropriate identity-api extension, we stopped on the
resource object discussion.

Resource is a new term in keystone - it's some characteristics which can be
measured and limited in use. The question is - will resource be always tied
to some specific service or there can be use cases when resource is tied to
more than one service (or not tied to any concrete service)?

The thing is that in the first case (when resource is tied to some
service), we can add "service_id" field to resource object to show it's
dependency. In the second case it's not
appropriate to add such field.

So, if you have any use cases when resource can be tied to more than one
service or not tied to any service, feel free to share them with me.

If you have any other ideas / comments on this, please also feel free to
share them.

Last version of design can be found here:

Thanks & regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130819/b1efc579/attachment.html>

More information about the Openstack mailing list