openstack team mailing list archive

[Everett Toews <everett.toews@xxxxxxxxx>]

Hi All,

I've started a blueprint<https://blueprints.launchpad.net/keystone/+spec/store-quota-data>and
spec <http://wiki.openstack.org/KeystoneStoreQuotaData> to store quota data
in Keystone. Please have a look if you're interested and any feedback is
welcome.

Of course, writing up the spec brought up number of questions for me. You
can find more detail in the spec but here they are to get some more
exposure.

1. For the keystone CLI I'm proposing using JSON for batch create, update,
and delete of quotas. I don't believe this is done anywhere else in
OpenStack. Good idea? Bad idea?
My plan is to go with the JSON.

2. For the RESTful API, do we have just one DELETE with details of what to
delete in the body of the request?
My plan is to go with just one DELETE.

3. For the implementation I'm proposing two options. 1. Store the data in
the current metadata table. 2. Store the data in a new metadata_per_tenant
table. Thoughts?
My plan is to use option 2.

4. If you change the word quota to the word metadata in the User Stories
and the Design sections, this becomes a generic mechanism for accessing
metadata per tenant. Do we want a generic metadata service for keystone or
stick with a service specific to quotas, while keeping the underlying
implementation generic?
I'm on the fence about this one. On one hand, it's very clear to have a
well defined API that's just used for quotas. On the other hand, it's very
flexible to have a generic API that can be used for any metadata (although
maybe that promotes abuse of the feature).

Regards,
Everett