Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D6AEED460 for ; Thu, 20 Dec 2012 06:29:16 +0000 (UTC) Received: (qmail 72254 invoked by uid 500); 20 Dec 2012 06:29:15 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 71769 invoked by uid 500); 20 Dec 2012 06:29:15 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 71737 invoked by uid 99); 20 Dec 2012 06:29:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Dec 2012 06:29:14 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Xuefei.Xu@citrix.com designates 66.165.176.89 as permitted sender) Received: from [66.165.176.89] (HELO SMTP.CITRIX.COM) (66.165.176.89) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Dec 2012 06:29:08 +0000 X-IronPort-AV: E=Sophos;i="4.84,322,1355097600"; d="scan'208";a="1373616" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 20 Dec 2012 06:28:46 +0000 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Wed, 19 Dec 2012 22:28:46 -0800 From: Anthony Xu To: "cloudstack-dev@incubator.apache.org" , "cloudstack-users@incubator.apache.org" Date: Wed, 19 Dec 2012 22:28:44 -0800 Subject: RE: [DISCUSS] Dedicated Resources: Dedicate Pods, Clusters, Hosts to a domain Thread-Topic: [DISCUSS] Dedicated Resources: Dedicate Pods, Clusters, Hosts to a domain Thread-Index: Ac3eeflBVHGmm+TSQxaG9ZAmslya8QAALKRA Message-ID: References: In-Reply-To: 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 > In this feature > - Root Admin should be able to dedicate a pod/cluster/host to a > particular domain or sub-domain. How about primary storage? Can PS be dedicated to a domain? Can an account have dedicated resource? > - If there is no available resources in the dedicated pod/cluster/host, > then CloudStack should fail the operation > for a user in that domain. If this happens, how does admin handle this? Can admin extend resource for this domain? Anthony > -----Original Message----- > From: Deepti Dohare [mailto:deepti.dohare@citrix.com] > Sent: Wednesday, December 19, 2012 10:20 PM > To: cloudstack-dev@incubator.apache.org; cloudstack- > users@incubator.apache.org > Subject: [DISCUSS] Dedicated Resources: Dedicate Pods, Clusters, Hosts > to a domain >=20 > Hi, >=20 > Currently in CloudStack architecture, domains can have dedicated zones > but not pods, clusters or hosts. >=20 > We are proposing this functionality in "Dedicated Resources" where a > domain or a sub-domain can have dedicated pods, clusters or hosts. >=20 > Why we need this feature: > Dedicating a zone might be very expensive offering for an end users, > whereas dedicating a pod, cluster or a host > may be more economical. This feature will allow Root-Admin to dedicate > resources to a specific domain that needs > private infrastructure for additional security or performance > guarantees. >=20 > In this feature > - Root Admin should be able to dedicate a pod/cluster/host to a > particular domain or sub-domain. > - Any users in that domain can access pod/cluster/host dedicated to > their domain. > - No users outside that domain, can access the dedicated pod, cluster > or hosts (eg. deploy instance on that pod/cluster/host). > - If there is no available resources in the dedicated pod/cluster/host, > then CloudStack should fail the operation > for a user in that domain. >=20 > I have filed a jira request: > https://issues.apache.org/jira/browse/CLOUDSTACK-681, to track this > feature. Please let me know any comments and suggestions. >=20 > Thanks > Deepti