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 35DEE9FED for ; Sat, 26 May 2012 16:42:29 +0000 (UTC) Received: (qmail 50406 invoked by uid 500); 26 May 2012 16:42:29 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 50376 invoked by uid 500); 26 May 2012 16:42:28 -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 50367 invoked by uid 99); 26 May 2012 16:42:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 May 2012 16:42:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Kishan.Kavala@citrix.com designates 203.166.19.134 as permitted sender) Received: from [203.166.19.134] (HELO SMTP.CITRIX.COM.AU) (203.166.19.134) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 May 2012 16:42:22 +0000 X-IronPort-AV: E=Sophos;i="4.75,662,1330905600"; d="scan'208";a="11517741" Received: from banpmailmx01.citrite.net ([10.103.128.73]) by SYDPIPO01.CITRIX.COM.AU with ESMTP/TLS/RC4-MD5; 26 May 2012 16:41:59 +0000 Received: from BANPMAILBOX01.citrite.net ([10.103.128.72]) by BANPMAILMX01.citrite.net ([10.103.128.73]) with mapi; Sat, 26 May 2012 22:11:57 +0530 From: Kishan Kavala To: "cloudstack-dev@incubator.apache.org" Date: Sat, 26 May 2012 22:11:57 +0530 Subject: RE: Regions - further discussions Thread-Topic: Regions - further discussions Thread-Index: Ac00WQM852QyQVvSQA+UGbK2cAvBsgAAObRAAAAY0dAABr/44AAKyQ3AAAJihcAAEfMpqwDs0BtAAAUyU2AAqNmPgA== Message-ID: <33740054EBF5B64BB213E2E0916F2C13EA0FAA085A@BANPMAILBOX01.citrite.net> References: <33740054EBF5B64BB213E2E0916F2C13E9EAE42D46@BANPMAILBOX01.citrite.net> <61AE1E2837A06D4A8E98B796183842D40116B8789F7C@SJCPMAILBOX01.citrite.net> ,<64FB1554ABC9B44FAA773FBD6CB889C2F916285DF6@BANPMAILBOX01.citrite.net> <33740054EBF5B64BB213E2E0916F2C13E9EADD3A31@BANPMAILBOX01.citrite.net> <64FB1554ABC9B44FAA773FBD6CB889C2F93A9CE99F@BANPMAILBOX01.citrite.net> <64FB1554ABC9B44FAA773FBD6CB889C2F93A9CE9EF@BANPMAILBOX01.citrite.net> In-Reply-To: <64FB1554ABC9B44FAA773FBD6CB889C2F93A9CE9EF@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 > -----Original Message----- > From: Abhinandan Prateek [mailto:Abhinandan.Prateek@citrix.com] > Sent: Wednesday, 23 May 2012 1:31 PM > To: cloudstack-dev@incubator.apache.org > Subject: RE: Regions - further discussions >=20 >=20 > Initial draft from Kishan is here: > http://wiki.cloudstack.org/display/RelOps/Regions+Functional+Spec >=20 I've update the spec with details about Account management across Regions: Accounts: - When creating the account, it is created first in the Region that the use= r is logged into - Account UUID will include Region marker, indicating the Region that it is= created from - This Region is then responsible for propagation of Account creation to ot= her Regions - If a Region receives a login from an unknown uuid, then use the Region ma= rker to auto-propagate the account into this region from another Region or = its origins - Account deletion is always forwarded to the Region that originally create= d the account=20 - The Region that originally created account is responsible for deleting th= e account from all of the regions before it declares the account is deleted= . If it cannot reach an Region, account deletion fails. The same applies for Domains. Please let me know your thoughts on the above mentioned approach for Accoun= t Management. ~kishan