OK, I understand - but this still requires various sized compute service offerings created by the admin - when I read that statement the first time, it appeared as if that was not required, hence my question..
Hari -----Original Message----- From: Sanjay Tripathi [mailto:sanjay.tripa...@citrix.com] Sent: Wednesday, January 2, 2013 3:44 AM To: cloudstack-dev@incubator.apache.org Subject: RE: [DISCUSS] Limit Resources to domain/account Hi Hari, Today CS imposes the limits on the number on VMs and we are proposing the limits on CPUs, RAM, storage etc, so with the help of this feature, user can create several small VMs or one large VM (depends on the requirement) within the imposed limits. Regards, Sanjay -----Original Message----- From: Hari Kannan [mailto:hari.kan...@citrix.com] Sent: Thursday, December 27, 2012 9:58 PM To: cloudstack-dev@incubator.apache.org Subject: RE: [DISCUSS] Limit Resources to domain/account Hi Sanjay, Can you please explain how this is possible? " With the help of this feature, users would be able to create custom VMs under the limits(CPU, RAM, storage etc.) set by CS admin. They would be free to choose CPU, memory, storage as per there requirements." Hari -----Original Message----- From: Sanjay Tripathi [mailto:sanjay.tripa...@citrix.com] Sent: Thursday, December 27, 2012 12:22 AM To: cloudstack-dev@incubator.apache.org Subject: RE: [DISCUSS] Limit Resources to domain/account Hi Venkata, Please find my answers inline. >> (i) what is the difference between (3) and (11) ? Right now we are limiting the user on the basis of number of volumes (root and data disks) that a user can create and not on the basis of storage space a user can use. (11) is for limiting the storage space (as pointed out by Hari). >>(ii) what is the difference between (4), (5) and (12) except no. of ISOs? In (4) and (5), the limit is on numbers and in (12), the limit is on secondary storage space. >>(iii) how the network bandwidth you mentioned in (13) is different from >>throttling that we specify at network offering / vm.network.throttling.rate - >>used by service offering ? By using vm.network.throttling.rate, CS is limiting the network rate for user VMs and in (13), we are proposing to limit the network rate on domain/account basis. >>(iv) can you please give some more info on how this is going to help >>providers / accounts with this additional setting? Is this to control some >>kind of licensing limitations? With the help of this feature, users would be able to create custom VMs under the limits(CPU, RAM, storage etc.) set by CS admin. They would be free to choose CPU, memory, storage as per there requirements. Thanks, Sanjay -----Original Message----- From: Venkata SwamyBabu Budumuru [mailto:venkataswamybabu.budum...@citrix.com] Sent: Wednesday, December 26, 2012 9:46 PM To: cloudstack-dev@incubator.apache.org Subject: RE: [DISCUSS] Limit Resources to domain/account Hi Sanjay, Few queries I have here : (i) what is the difference between (3) and (11) ? (ii) what is the difference between (4), (5) and (12) except no. of ISOs? (iii) how the network bandwidth you mentioned in (13) is different from throttling that we specify at network offering / vm.network.throttling.rate - used by service offering ? (iv) can you please give some more info on how this is going to help providers / accounts with this additional setting? Is this to control some kind of licensing limitations? Thanks, SWAMY -----Original Message----- From: Sanjay Tripathi [mailto:sanjay.tripa...@citrix.com] Sent: Wednesday, December 26, 2012 2:57 PM 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
