incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanjay Tripathi <sanjay.tripa...@citrix.com>
Subject RE: [DISCUSS] Limit Resources to domain/account
Date Tue, 22 Jan 2013 08:20:00 GMT
Hi Hari, 

Thanks for the suggestions, I have updated the FS with the use cases you pointed out.

Regards,
Sanjay

> -----Original Message-----
> From: Hari Kannan [mailto:hari.kannan@citrix.com]
> Sent: Tuesday, January 22, 2013 7:47 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [DISCUSS] Limit Resources to domain/account
> 
> Hi Sanjay,
> 
> May I request you to update the FS with a couple of points of interest:
> 
> 1 - when you refer to storage space, what does this exactly mean? Actual,
> consumed space (for example thin prov storage might consume less than
> stated size) or does it imply stated size? I assume it refers to the latter, but
> better to clarify for posterity.
> 2 - can you please elaborate more this scenario, when the limit is
> "downsized" to a value lower than the current "consumed" or "used" level?
> You do talk about this under use case, section 6, I think, but the reference to
> just VMs in that section is somewhat ambiguous - hence, it makes sense to
> clarify
> 3 - can you confirm this: if a domain has limit X , we will ensure sub-
> domain/account under them can have their own limits (nested) - if so,
> ensure the top-level limits are honored? And the sum of stated limits of
> lower level (sub-domain or accounts, for example) can be greater than the
> stated limit of the higher level (domain, for example), but the enforced limit
> is never greater - what I mean is Domain D may have CPU limit of 80, sub-
> domain D1 and D2 each may have limits of 60 each, but together they will
> never be allocated greater than 80? Or is this not the case?
> 4 - can you write something up in the FS regarding this: the lower of 2 limits
> will be enforced - for example, if there is a VM limit of 10 and CPU limit of 20,
> after the user requests 5 VMs of 2 CPUs each, his next request will be denied
> (as he has exhausted his CPU limit, even though he has a higher VM limit)?
> 5 - ensure we log these error messages in 3 and 4??
> 
> Thanks!
> 
> Hari
> 
> -----Original Message-----
> From: Sanjay Tripathi [mailto:sanjay.tripathi@citrix.com]
> Sent: Wednesday, December 26, 2012 1:27 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: [DISCUSS] Limit Resources to domain/account
> 
> Hi all,
> 
> CloudStack today offers the ability to limit the following resources to a
> domain/account:
> 1. VM - Number of instance a user can create 2. Pubic IP - Number of public
> IP addresses a user can own.
> 3. Volume - Number of disk volumes a user can create.
> 4. Snapshot - Number of snapshots a user can create.
> 5. Template - Number of templates that a user can register/create.
> 6. Projects - Number of projects a user can create.
> 7. Network - Number of guest networks that a user can create.
> 8. VPC - Number of VPCs that a user can create
> 
> These limits are useful to some extent but if admin would like to allow user
> to create custom VMs based on need, for e.g. one large VM or many small
> VMs etc.
> Admin would like to restrict the resources like CPU, RAM, storage etc. a user
> can consume by setting limits.
> 
> I would like to propose a new feature based on the above mentioned
> requirements in which admin would be able to set limits on following
> resources apart from the above mentioned resources types:
> 9. CPUs
> 10. RAM
> 11. Primary (shared) storage (Volumes)
> 12. Secondary storage (Snapshots, Templates & ISOs) 13. Network
> bandwidth rate (in bps) 14. Number of times a OS template can be deployed
> 
> I am working on FS and will share it shortly.
> 
> Please let me know your comments/suggestions.
> 
> Thanks,
> Sanjay
> 

Mime
View raw message