incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frank Zhang <Frank.Zh...@citrix.com>
Subject RE: [ASF40][DISCUSS] Split AWS API / CloudBridge into a separate project
Date Tue, 09 Oct 2012 19:04:13 GMT
Installation has nothing to do with packaging.
The project can be maintained in separate place, but we are still able to make a one-shot
installer.
Awsapi calling CloudStack api is a nature separate project, including it in CloudStack only
makes CloudStack quite immense. 

> -----Original Message-----
> From: Prachi Damle [mailto:Prachi.Damle@citrix.com]
> Sent: Tuesday, October 09, 2012 11:28 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [ASF40][DISCUSS] Split AWS API / CloudBridge into a separate
> project
> 
> +1 on keeping awsapi as part of CloudStack since it's a value-add to CS + one-
> step installation for users
> 
> We should not want to break it out because the packaging is hard. The
> functionality added is more important.
> 
> -----Original Message-----
> From: Rajesh Battala [mailto:rajesh.battala@citrix.com]
> Sent: Tuesday, October 09, 2012 9:09 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [ASF40][DISCUSS] Split AWS API / CloudBridge into a separate
> project
> 
> 
> 
> -----Original Message-----
> From: David Nalley [mailto:david@gnsa.us]
> Sent: Tuesday, October 09, 2012 8:20 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ASF40][DISCUSS] Split AWS API / CloudBridge into a separate
> project
> 
> On Tue, Oct 9, 2012 at 7:32 AM, Wido den Hollander <wido@widodh.nl>
> wrote:
> > Hi,
> >
> > I started a innocent thread on the -dev list yesterday[0] about some
> > packaging remarks regarding the AWS API aka CloudBridge.
> >
> > This turned out to be a rather large thread where Edison mentioned[1]
> > we might want to split this out into a separate repository.
> >
> > Some time ago we agreed that we don't want to split CloudStack up into
> > multiple smaller projects since it would be very hard to keep all the
> > projects in sync.
> >
> > I'm now looking at packaging AWS API into Deb files as by CS-294[2],
> > but I'm thinking about Edison's remark.
> >
> > I know this question might come at a awkward moment, just prior to the
> > 4.0 release, but when I create a cloud-awsapi Debian package people
> > will start using it and we'll be dealing with the legacy at a later point.
> >
> > If we create a "cloudbridge" package separate from the cloud-*
> > packages we can move forward from there.
> >
> > At the old Github account[3] there is even a separate CloudBridge
> > repository, this got merged into master on May 25th of this year with
> > commit
> > bc7dbd7d9681dc2729326ff78fb5fe586b336b25
> >
> > Since 4.0 is not out of the door yet, do we want to keep this in the
> > cloudstack repository or split it out (again)?
> >
> > I've seen numerous build failures with awsapi breaking master while
> > it's not actually a part of the code base, so in this case I'm in
> > favor of breaking it out, but we should discuss this.
> >
> > Note: We already have a LOT of e-mail on this list, so can we try to
> > stick ontopic here and keep it to the point? Tnx!
> >
> > Wido
> 
> 
> -1 to breaking it out for 4.0
> We are in code freeze at this point - the code present is what we need to
> deal with.
> [Rajesh Battala]
> 
> -1 for breaking it out from 4.0 release.
> It's really important and value added to ASF CS 4.0
> 
> Thanks
> Rajesh Battala

Mime
View raw message