Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of runseb@gmail.com designates
 209.85.215.175 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [RFC] Refactoring CloudStack
From: Sebastien Goasguen <runseb@gmail.com>
In-Reply-To: <50A0B437.80809@widodh.nl>
Date: Mon, 12 Nov 2012 09:52:37 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <85D1D9E4-32C0-4EB0-B8BA-05D909A4C4B6@gmail.com>
References: 
 <B1DF26ECC0458748AC97CECE2DA98D41012FA1E1C498@SJCPMAILBOX01.citrite.net>
 <50A0B437.80809@widodh.nl>
To: cloudstack-dev@incubator.apache.org

Alex,

I looked at the powerpoint.=20

Could you elaborate a bit on the new deployment plans (slides 19-21). It =
seems that you are aiming for more independent zones and a more reliable =
management layer, but I could not quite picture how you would actually =
deploy this.

On the componentization: I think it's great, but will this result in =
separate applications (like we AWSAPI now) ? and will these components =
still be tightly integrated from a packaging installation point of view =
? My concern being that we should still aim for a "one-click" install of =
CloudStack versus several recipe to integrate many different components.

Last thing, which is really a software implementation choice, I was =
talking to the Java User Group in Geneva and mentioned that the =
community was looking at moving to the Spring framework, some folks were =
a little surprised, suggesting that there was better frameworks that =
could be used.

thanks,

-Sebastien

On Nov 12, 2012, at 9:32 AM, Wido den Hollander <wido@widodh.nl> wrote:

> Hi Alex,
>=20
> Just wanted to let you know that I'm going to take a good look at =
this.
>=20
> Wido
>=20
> On 11/09/2012 07: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]
>>=20
>> 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.
>>=20
>> Please comment.
>>=20
>> --Alex
>>=20
>> [1] =
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Refactor=
ing
>>=20