Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3F2ECE401 for ; Thu, 14 Feb 2013 20:57:58 +0000 (UTC) Received: (qmail 59243 invoked by uid 500); 14 Feb 2013 20:57:57 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 59198 invoked by uid 500); 14 Feb 2013 20:57:57 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 59190 invoked by uid 99); 14 Feb 2013 20:57:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2013 20:57:57 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hari.kannan@citrix.com designates 66.165.176.63 as permitted sender) Received: from [66.165.176.63] (HELO SMTP02.CITRIX.COM) (66.165.176.63) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2013 20:57:52 +0000 X-IronPort-AV: E=Sophos;i="4.84,666,1355097600"; d="scan'208";a="7206355" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Feb 2013 20:57:31 +0000 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.73]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Thu, 14 Feb 2013 12:57:30 -0800 From: Hari Kannan To: "cloudstack-dev@incubator.apache.org" Date: Thu, 14 Feb 2013 12:57:27 -0800 Subject: RE: [DISCUSS] Limit Resources to domain/account Thread-Topic: [DISCUSS] Limit Resources to domain/account Thread-Index: Ac34bQq9wvGpMnlySE+GNky0ZT8LQABAWIcABGGczPA= Message-ID: <6E004C34C1C59E45A35B4338808BC315013016346A5B@SJCPMAILBOX01.citrite.net> References: <02C38648D4635F4EB02DE11EE81CF1EE012F106804B0@BANPMAILBOX01.citrite.net> In-Reply-To: <02C38648D4635F4EB02DE11EE81CF1EE012F106804B0@BANPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hi Sanjay, The FS states that " Root/Domain Admin should be able to limit the followi= ng resources" etc. Do you mean a domain admin can change the limit for his own domain? If so, = I wonder if this is appropriate?? A domain admin must be able to change onl= y for any/all sub-domains or accounts under his own domain or all sub-domai= ns - Does it make sense? Also, I don't see FS being up-to-date - for example, the detail regarding t= he upgrade scenario doesn't seem to be updated, as per Chiradeep' suggestio= n.. Can you please take of it? Thanks! Hari -----Original Message----- From: Sanjay Tripathi [mailto:sanjay.tripathi@citrix.com]=20 Sent: Wednesday, January 23, 2013 9:06 AM To: cloudstack-dev@incubator.apache.org Subject: RE: [DISCUSS] Limit Resources to domain/account Comments Inline > -----Original Message----- > From: Chiradeep Vittal [mailto:Chiradeep.Vittal@citrix.com] > Sent: Tuesday, January 22, 2013 12:22 PM > To: CloudStack DeveloperList > Subject: Re: [DISCUSS] Limit Resources to domain/account >=20 > Are there any alarms / events /warnings raised for this condition? [] If user cross the resource limit set for his/her account, CloudStack th= rows a message to the user that limit of this resource type has been exceed= ed. Apart from this CS does not send any alarm or warnings for this conditi= on(if there is a requirement for this, I can definitely add it into this fe= ature). > Can the end-user see how much capacity he / she has left (through an=20 > API > call) > Can they see it on the UI? [] We don't have separate API for this. To calculate the resources that are= left for his/her account, user can use listAccounts API which displays the= resource limits and the total resources that are being consumed by that ac= count. In CloudStack UI, user can see the resource details under the "accounts" de= tailView. > Should the limits be associated with an account? Or should the account=20 > be linked to a 'rate plan'. >=20 > On 1/21/13 10:36 PM, "Chiradeep Vittal" > wrote: >=20 > >Please update the FS with this important detail. > > > >On 1/16/13 11:52 AM, "Sanjay Tripathi" wrot= e: > > > >>Koushik, > >> > >>>What is the upgrade story? For e.g. say based on the existing VM's=20 > >>>for an account, the total CPU and RAM exceeds the global maximums. > >>>What happens in this case? > >> > >> > >>If admin sets the limits for an account and suppose that account=20 > >>already has existing VMs whose total CPU and RAM counts are=20 > >>exceeding the limits, in this case CloudStack would not shut down=20 > >>the VMs assigned to account to level the resources. If the user=20 > >>tries to deploy a VM, CS will check the limits of that account and=20 > >>in this case CS will not allow the account to deploy the VM. > >> > >>>Also for CPU number of cores are considered, should speed also be=20 > >>>considered? > >>Thanks for suggestion :), we can consider speed also as a part of=20 > >>CPU resource. > >> > >>Thanks, > >>Sanjay > >> > >> > >>> -----Original Message----- > >>> From: Chris Sears [mailto:chris.x.sears@sungard.com] > >>> Sent: Wednesday, January 16, 2013 10:39 PM > >>> To: cloudstack-dev@incubator.apache.org > >>> Subject: Re: [DISCUSS] Limit Resources to domain/account > >>> > >>> On Wed, Jan 16, 2013 at 6:00 AM, Sanjay Tripathi=20 > >>> >>> > wrote: > >>> > >>> > Can anyone suggest that what should be the default max resource=20 > >>> > values that an account/project can have for the following global=20 > >>> > config > >>> parameters: > >>> > >>> > >>> It seems like the least surprising default max would be to leave=20 > >>>them all unlimited. Otherwise, it's likely some admins will just=20 > >>>overlook this and then just stumble upon the arbitrary limit. If=20 > >>>you default to unlimited, only admins who need to restrict it will=20 > >>>need to be concerned with the settings. > >>> > >>> As an aside, I wasn't clear from the FS how to specify "unlimited" > >>>in the UI. > >>> Does leaving the value blank imply unlimited? > >>> > >>> - Chris > >