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 6926BDE91 for ; Mon, 12 Nov 2012 16:50:38 +0000 (UTC) Received: (qmail 41124 invoked by uid 500); 12 Nov 2012 16:50:38 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 41092 invoked by uid 500); 12 Nov 2012 16:50:38 -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 41079 invoked by uid 99); 12 Nov 2012 16:50:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Nov 2012 16:50:37 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.149.205] (HELO na3sys009aog111.obsmtp.com) (74.125.149.205) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Nov 2012 16:50:29 +0000 Received: from mail-ye0-f197.google.com ([209.85.213.197]) (using TLSv1) by na3sys009aob111.postini.com ([74.125.148.12]) with SMTP ID DSNKUKEovqegRHHO4O3jiEgXE+c0Ro9LtFgQ@postini.com; Mon, 12 Nov 2012 08:50:09 PST Received: by mail-ye0-f197.google.com with SMTP id l11so11695748yen.0 for ; Mon, 12 Nov 2012 08:50:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=o1iwiydPh3Ve1pHR65m5n5E4LYbWLO/vQfhI30FqKhM=; b=mVrWnqndGtZhmnYKryQ/AmHMQQafByx6Xv0XU2fHaQHVfkLWLJ6WCHPi81JYKRDI6e IUVO31fS6a9054Ej9qUImvubar6ZNX1aaTdnvchCd0WdRPpJYCADJe/FzHSpciysQQ/z Qstt5tqRJKuRDQg/nNXC22t2Cw1HPgVI750iBDCwjuMJ0skeAqOUEYpgHtph8PbIEROP K1ORA/pGVHYeGariZHqqvNbAFX7c8DUh1OTNj87PtHnqwgryBPCFtlqKh31Ls/zUmNa7 6nivqRFt7eHXdHSZ5hP5GXUIfIc7Jj4p+yfNgZhcshFc0v3hlkS2+opVxui1Sx/gwU/o UCmA== Received: by 10.58.2.71 with SMTP id 7mr21511538ves.42.1352739006133; Mon, 12 Nov 2012 08:50:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.58.2.71 with SMTP id 7mr21511514ves.42.1352739005969; Mon, 12 Nov 2012 08:50:05 -0800 (PST) Received: by 10.58.239.135 with HTTP; Mon, 12 Nov 2012 08:50:05 -0800 (PST) In-Reply-To: References: Date: Mon, 12 Nov 2012 11:50:05 -0500 Message-ID: Subject: Re: [RFC] Refactoring CloudStack From: Chip Childers To: cloudstack-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=047d7b2e76e0ecb4e504ce4f1701 X-Gm-Message-State: ALoCoQmcLrnmk9p3boeLS1BdQfosRfetMdB7cq9aNdD+HJszVcgtcIXRNWt0DJGMEk1E4Grb/psrxjnm7xVD1VbxwM8Q5hR299N2yxQ2S9gkfqd0Wuj9e3ZjLPaA9pmsMs0AECfRem1frANNWY7RqokH2XkltCG/IgO+xBQJ4/ITDQr2wFIgF8CN63R9ewYPR2VJwPlx518r X-Virus-Checked: Checked by ClamAV on apache.org --047d7b2e76e0ecb4e504ce4f1701 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Nov 9, 2012 at 1:12 PM, Alex Huang wrote: > I sent out an email a couple of months ago about the need to refactor > CloudStack into small pieces. At the time, the overall sentiment was the > community is heavily invested in releasing 4.0 and this should be brought > up post 4.0. Now that 4.0 has been released, I like to bring this up > again. I created a powerpoint to illustrate that need. Please take a look > at [1] > > This work is related to Edison's Storage subsystem, Kelven's Spring, > Murali's notification system proposals. The work is to be done in the > javelin branch. > > Please comment. > > --Alex > > [1] > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Refactoring > > > Alex, This is a fantastic, multi-leveled proposal with lots of implications. I think that I'm going to keep my comments to the high-level intent of the document, and ask that we re-initiate discussions on the implementation details individually. In general, I'm highly supportive of this! Some specific questions from the slides: Slide 2 (Design Goals) - to me, the idea of "Allowing cloudstack components to be written in any language" has some significant implications on choice of framework and implementation design decisions for the refactoring work. Do you agree? Slide 10 - there is a mention of a Policy Monitoring Service - what is that? Slide 10 - Is the box labeled CloudStack Orchestration Platform more correctly labeled Cloud Engine? If not, I think I'm not understanding the diagram. If so, then it makes sense to me. Slide 21 - The "Account database" is shown. Any thoughts in how would multi-region users be synced? -chip --047d7b2e76e0ecb4e504ce4f1701--