Re: [Openstack] [Swift]A design draft of Storage Quota

2013-03-06 Thread Everett Toews
I already posted this over in dev but thought I'd tie off this thread too. I've just proposed a design summit session with the description below. I sincerely hope anyone interested in quotas will attend. Please have a look at the etherpad to see what's already been done. The quota situation is

Re: [Openstack] [Swift]A design draft of Storage Quota

2013-02-21 Thread Thierry Carrez
Alex Yang wrote: Storage Quotas Design https://docs.google.com/document/d/1b5hkT_E8PyzaAPjNImW0SF-yyh8vGrN_DNjMChol4_Q/edit This is the design draft of Storage Quota. Implementation of this design is https://github.com/AlexYangYu/StackLab-swift/tree/dev-quota Looks like a discussion that

Re: [Openstack] [Swift]A design draft of Storage Quota

2013-02-20 Thread Chmouel Boudjnah
I haven't had the chance to do a full reviews but here is a few toughts : - the account quota goes along this review: https://review.openstack.org/#/c/21563/ so we can get easily have account metadatas from middlewares. - I am not sure I fancy much the json blob in the ini config (why not a

Re: [Openstack] [Swift]A design draft of Storage Quota

2013-02-20 Thread Christian Schwede
Hi, you might also have a look at https://github.com/cschwede/swquota Account quota is stored in account metadata and set by a reseller account. I changed the code slightly to make it more consistent to the already merged container quota. @chmouel: I might create a pull request to swift

Re: [Openstack] [Swift]A design draft of Storage Quota

2013-02-20 Thread Alex Yang
Hi Schwede, I have already read your codes. To implement the authentication of updating metadata in the middleware is good for maintainance. But the account usage is not accurate because of the eventual consistency. So I do the usage quota based on container. I will refactor my implementation

Re: [Openstack] [Swift]A design draft of Storage Quota

2013-02-20 Thread Alex Yang
2013/2/20 Chmouel Boudjnah chmo...@chmouel.com I haven't had the chance to do a full reviews but here is a few toughts : - the account quota goes along this review: https://review.openstack.org/#/c/21563/ so we can get easily have account metadatas from middlewares. Yes, I also want

Re: [Openstack] [Swift]A design draft of Storage Quota

2013-02-20 Thread Kevin L. Mitchell
On Wed, 2013-02-20 at 18:11 +0800, Alex Yang wrote: Storage Quotas Design This is the design draft of Storage Quota. Implementation of this design is https://github.com/AlexYangYu/StackLab-swift/tree/dev-quota I'll also point out Boson: https://wiki.openstack.org/wiki/Boson and

Re: [Openstack] [Swift]A design draft of Storage Quota

2013-02-20 Thread Chmouel Boudjnah
Hi Kevin, On Wed, Feb 20, 2013 at 5:26 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: I'll also point out Boson: https://wiki.openstack.org/wiki/Boson and https://github.com/klmitch/boson with some initial work. Unfortunately, I'm not able to work on Boson at the moment due to

Re: [Openstack] [Swift]A design draft of Storage Quota

2013-02-20 Thread Kevin L. Mitchell
On Wed, 2013-02-20 at 21:09 +0100, Chmouel Boudjnah wrote: On Wed, Feb 20, 2013 at 5:26 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: I'll also point out Boson: https://wiki.openstack.org/wiki/Boson and https://github.com/klmitch/boson with some initial work. Unfortunately,

Re: [Openstack] [Swift]A design draft of Storage Quota

2013-02-20 Thread Chmouel Boudjnah
I was guessing this is the part of what synaps do but from looking at https://wiki.openstack.org/wiki/Synaps it may just provide only notifications and not enforcements. Chmouel. On Wed, Feb 20, 2013 at 9:17 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: On Wed, 2013-02-20 at 21:09

Re: [Openstack] [Swift]A design draft of Storage Quota

2013-02-20 Thread Everett Toews
On 2/20/13 1:28 PM, Tim Bell tim.b...@cern.ch wrote: We also feel an integrated approach such as Boson is the way forward for quota rather than each project have its own (and potentially differing) implementations on areas such as delegation. +1 to an integrated approach. It's easy to envision