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 87E30D4BA for ; Tue, 9 Oct 2012 11:32:51 +0000 (UTC) Received: (qmail 5236 invoked by uid 500); 9 Oct 2012 11:32:51 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 5081 invoked by uid 500); 9 Oct 2012 11:32:48 -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 5061 invoked by uid 99); 9 Oct 2012 11:32:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2012 11:32:48 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [109.72.87.137] (HELO smtp01.mail.pcextreme.nl) (109.72.87.137) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2012 11:32:41 +0000 Received: from [IPv6:2a00:f10:113:0:bdb8:9ec8:9b72:5cbb] (unknown [IPv6:2a00:f10:113:0:bdb8:9ec8:9b72:5cbb]) by smtp01.mail.pcextreme.nl (Postfix) with ESMTPSA id D11CD7633D for ; Tue, 9 Oct 2012 13:32:20 +0200 (CEST) Message-ID: <50740B4B.8010707@widodh.nl> Date: Tue, 09 Oct 2012 13:32:27 +0200 From: Wido den Hollander User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: "cloudstack-dev@incubator.apache.org" Subject: [ASF40][DISCUSS] Split AWS API / CloudBridge into a separate project Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 [0]: http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201210.mbox/%3C507357EF.9060104%40widodh.nl%3E [1]: http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201210.mbox/%3C9CEC48D0-004C-4DDC-9AB5-30EBB9C7EE57%40citrix.com%3E [2]: https://issues.apache.org/jira/browse/CLOUDSTACK-294 [3]: https://github.com/CloudStack/CloudBridge