Now that we are doing this can we also not do the checking limits through ACL refactoring we are going to do ?
Thanks, -Nitin On 26-Dec-2012, at 2:56 PM, Sanjay Tripathi wrote: > 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 >
