openstack team mailing list archive

[Everett Toews <everett.toews@xxxxxxxxx>]

Hi All,

I led the session [1] on Swift Quotas at the Summit and I'd appreciate some
feedback on the updated spec [2] and blueprint [3]. I also have a couple of
design level questions.

1. Should we store the Swift quota data in Keystone?

One of the ideas that came out of the session was that we could store the
Swift quota data in Keystone. I took a look at Keystone and it appears the
best place for this would be in the metada table but it appears to me that
it's only accessible via the User Metadata Extension API in Keystone. Is it
feasible to store the Swift quota data in Keystone this way? Should we?

On a related note, during the Pluggable Tenant Data session [4] led by Phil
Day something similar was being discussed for moving Nova quotas to
Keystone.

2. Where should the code for Swift quotas live?

It was suggested during the session that this code could live in a
middleware for Swift. Seems like a reasonable approach to me. I've taken a
look at some of the code in /swift/common/middleware and it looks
relatively straight-forward. Any thoughts or suggestions on implementing
this as middleware?

Regards,
Everett

[1] http://etherpad.openstack.org/SwiftQuotas
[2] http://wiki.openstack.org/SwiftQuotas
[3] https://blueprints.launchpad.net/swift/+spec/storage-quotas
[4] http://etherpad.openstack.org/FolsomPluggableTenantData