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 rohit.yadav@citrix.com
 designates 203.166.19.134 as permitted sender)
From: Rohit Yadav <rohit.yadav@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Fri, 12 Oct 2012 11:50:17 +0530
Subject: Re: [ASF40][DISCUSS] Split AWS API / CloudBridge into a separate
 project
Thread-Topic: [ASF40][DISCUSS] Split AWS API / CloudBridge into a separate
 project
Thread-Index: Ac2oQaYGwO9+7D85SxixbCP/k/0jOQ==
Message-ID: <5A275EE5-A23A-4FA3-AB0E-27C38EBA67A8@citrix.com>
References: <50740B4B.8010707@widodh.nl>
 <CAKprHVZLMSahGkToK3YYUmvgPxC6xQSBme4UC=5NMA=hsPA9Xw@mail.gmail.com>
 <97F4356AEA71904482CD192135C038F9010D96E23F96@BANPMAILBOX01.citrite.net>
 <CA+96GG6OAKiAVP=HakrS-4B-Jgrp_-L-xLNatumymHzD8R+L8Q@mail.gmail.com>
 <CAKprHVZ43_s1YhvNGrg_S7FWW+3ad6u42i7fUKDDLA+6E9rvsg@mail.gmail.com>
 <CA+96GG4XcUfpHz=Go1yQ=pC=WsgJVooW=CPHzYatatsXWM8-FQ@mail.gmail.com>,<507492CD.6010300@widodh.nl>
 <38D062F1-C0FC-41C4-87BF-810E230679EB@schubergphilis.com>
In-Reply-To: <38D062F1-C0FC-41C4-87BF-810E230679EB@schubergphilis.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 12-Oct-2012, at 11:42 AM, Hugo Trippaers <HTrippaers@schubergphilis.com>=
 wrote:

>=20
>=20
> Op 9 okt. 2012 om 23:11 heeft "Wido den Hollander" <wido@widodh.nl> het v=
olgende geschreven:
>=20
>>=20
>>=20
>> On 10/09/2012 07:48 PM, Chip Childers wrote:
>>> On Tue, Oct 9, 2012 at 12:31 PM, David Nalley <david@gnsa.us> wrote:
>>>> On Tue, Oct 9, 2012 at 12:17 PM, Chip Childers
>>>> <chip.childers@sungard.com> wrote:
>>>>> OK,
>>>>>=20
>>>>> So let me try to summarize the opinions here:
>>>>>=20
>>>>> We have a couple of folks that think it should be split back out, but
>>>>> more are erring on the side of keeping the functionality.
>>>>>=20
>>>>> Assuming that we keep the code in the ACS repo for now, the second
>>>>> question is one of packaging.  Wido proposed a "cloudbridge" package
>>>>> for this specific code.  I think that makes sense, in that it gives u=
s
>>>>> options for breaking apart from CS in the future.
>>>>>=20
>>>>> Can we get some opinions about the packaging specific portion of the =
issue now?
>>>>=20
>>>>=20
>>>> So we release source code - so from a release perspective I think it
>>>> makes next to no difference.
>>>> For the convenience binaries that are being built it might make a
>>>> tremendous amount of difference - up to an including functionality not
>>>> working
>>>> I'd specifically not want to substantially change RPMs at this stage.
>>>> Debs could have this broken out since it has never been there, but it
>>>> would all need to be tested.
>>>>=20
>>>> --David
>>>>=20
>>>=20
>>> OK, so let's move forward with this plan:
>>>=20
>>> 1 - Get the DEB package built (as a separate package).
>>=20
>> This will be hard. Since we have a central control file for the Debian p=
ackaging it will be something like cloud-awsapi or cloud-bridge
>>=20
>> In the spec file I saw that that cloud-awsapi is depending on cloud-deps=
, so that starts to tie it in with the rest of the code-base on a packaging=
 level.
>=20
> With the maven build a lot of the dependency problems can be fixed per su=
b-package. In fact lot of fixes in there already to make sure awsapi build =
properly regardless of changes to other parts of the code.=20
>=20
> As for packaging, the maven build is producing war files with all the dep=
s included. So there will be a dedicated set of dependencies for awsapi and=
 another set for management server etc. for packagers that should make it e=
asy to package each item separately with its dependencies. Most webapp clas=
s loaders will look in its Web-inf/lib dir first before going to other plac=
es preventing conflicts with different versions of libraries.
>=20
> This doesn't yet help us for 4.0, but the problem should just go away (ju=
st like the deps directory) when people work on master again
>=20
> So -1 to split it off, makes more sense to keep it in the tree for me.

-1 to split it off;
Reverting my vote due to recent changes and my better understanding of mave=
n build system on master.

>=20
>=20
>>=20
>>> 2 - Test the AWS API via a DEB package installation
>>>=20
>>> We don't touch the RPM's now, since it's already been tested and (as
>>> of this morning) validated as working.
>>>=20
>>> Does someone want to pick up the DEB packaging for Wido (since I
>>> assume he's sleeping right now)?
>>>=20
>>=20
>> Not a sleep yet :) I'll be offline soon though, but I can follow up on w=
ork done over night (for me) and continue in the morning on what Edison cam=
e up with.
>>=20
>> Wido
>>=20
>>> -chip
>>>=20