On Fri, 2011-05-27 at 13:08 -0400, Carl Trieloff wrote:
On 05/27/2011 11:41 AM, Mark McLoughlin wrote:
> On Thu, 2011-05-26 at 14:14 -0400, Hugh Brock wrote:
>>> 2) Quotas
>>> When an administrator adds a provider account in conductor, she
>>> needs to be able to set a per-user quota for that account - e.g.
>>> Mary can only use 20Gb of S3 storage on this EC2 account
>>> (This sounds to me like a policy stored in Conductor, enforced
>>> either by conductor or image factory. If the latter, the quota
>>> could be passed to image factory via the credentials XML)
>> Hmm... I guess the storage used is always going to be billable to the
>> provider account used, isn't it. I suppose given that if we're
>> supposed to deal with anything having to do with accounts, we should
>> also be enforcing storage quota. Unfortunately that gets us back into
>> the business of having to be involved in every write to the image
>> factory, which makes me uncomfortable.
> What I'm imaging is:
> - An admin, in the Conductor UI, can set a per-user-per-provider
> image storage quota - i.e. "Mary can only user 20 GB of storage on
> this provider account for image storage"
> - When the provider account credentials XML are passed to image
> factory, we could include this storage quota
> - Image factory could query how much storage is used by images owned
> by that user on that provider and enforce the quota
This is more complex that the requirement I have given which is, storage
per user for iwhd. not per user per provider, we don't need the per
provider constraint from all the converstation.
Hmm, but the "expensive" storage is in the providers, not the filesystem
storage used by iwhd. It's the provider account storage that seems to me
to be the interesting one to set a quota on.
Indeed, in the case of EC2 snapshot builds, iwhd isn't storing any
images ... they're all in S3.
when we get to per provider, we care more about whether we are
caching, the cache policy for iwhd, provider cache size and not less
Losing me a little - you're referring to e.g. the S3 storage of EC2
images as a "cache"?
Currently, it's often the authoritative storage for the image and there
is no other copy of it.