incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gavin Lee <gavin....@gmail.com>
Subject Re: [DISCUSS] About shipping a non-OSS CloudStack
Date Sat, 15 Sep 2012 07:38:44 GMT
Put these non-oss components somewhere, for both developers and users.
The users keep the jars in hand is also important, consider they want
to install cloudstack with vmware hypervisor, and without internet
access.


On Sat, Sep 15, 2012 at 8:54 AM, Edison Su <Edison.su@citrix.com> wrote:
>
>
>> -----Original Message-----
>> From: Wido den Hollander [mailto:wido@widodh.nl]
>> Sent: Friday, September 14, 2012 3:37 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: [DISCUSS] About shipping a non-OSS CloudStack
>>
>>
>>
>> On 09/14/2012 07:08 PM, Chiradeep Vittal wrote:
>> >
>> >
>> > On 9/14/12 8:27 AM, "Wido den Hollander" <wido@widodh.nl> wrote:
>> >
>> >> On 09/14/2012 05:23 PM, Rohit Yadav wrote:
>> >>>
>> >>> On 14-Sep-2012, at 8:43 PM, Prasanna Santhanam
>> >>> <prasanna.santhanam@citrix.com> wrote:
>> >>>
>> >>>> Until CloudStack 3.0.2 - VMWare support existed in cloudstack and
>> with
>> >>>> the ASF builds we will effectively 'break' this since VMWare is
>> >>>> non-oss. There are other components too but VmWare is the bigger
>> >>>> piece.
>> >>>>
>> >>>> Hosters and EndUsers would be affected by this. Is there a plan
on
>> >>>> creating the non-oss builds once we have OSS fixed and cleared?
I
>> >>>> didn't see a discussion on this.
>> >>>>
>> >>>> In my opinion we have three options:
>> >>>>
>> >>>> 1) Instructions for users to build non-oss components from source
>> >>>> 2) Have private hosters/packagers have these binaries in their
>> >>>> repositories and point the endusers to these
>> >>>> 3) We create a maven profile to fetch (curl) the non-oss jars from
>> a
>> >>>> non-ASF location, compile against CS, put the artifact on
>> jenkins.c.o
>> >>>
>> >>> How about option 3 is feasible in a slightly modified way:
>> >>>
>> >>> We host nonoss-libs/jars in non-ASF infrastructure, the ASF
>> CI/Jenkins
>> >>> fetches them in a directory.
>> >>> ACS is build against them, and packaged as debs/rpm and separate
>> >>> bin-tarball (oss and nonoss).
>> >>>
>> >
>> > For developers / committers, it would be nice to have a place to
>> download
>> > these non-oss jars.
>> >
>>
>> Indeed. I've picked all the old jar files and put them online on my
>> personal webspace: http://zooi.widodh.nl/cloudstack/build-dep/
>>
>> We probably want a different location for them, but for now you can
>> fetch them there.
>
> I created a nonoss build at http://jenkins.cloudstack.org/job/build-4.0-nonoss-rhel63/.
> It's based on the patches created by Rohit, don't find a place to put these patches(because
one of the patch contains those binary jars).
>
>>
>> Wido
>>
>> >>
>> >> My intention was to build the Debian/Ubuntu packages with non-OSS
>> >> support, same goes for the RPM packages.
>> >>
>> >> Since they are hosted on non-ASF infra it shouldn't be a problem.
>> >>
>> >> Wido
>> >
>> > Does not solve the problem for developers? I am currently downloading
>> them
>> > from the repository history.
>> >
>> >>
>> >>> The non-oss package are only plugins and these built packages
>> >>> (debs/rpms) are copied to the same non-ASF infrastructure/repo.
>> >>> The CI cleans all non-oss packages. ASF hosts only the oss ones.
>> >>>
>> >>> Thoughts?
>> >>>
>> >>>> Thoughts? Flames?
>> >>>
>> >>> +1 for bringing this to the community.
>> >>>
>> >>> --
>> >>> Rohit
>> >>>
>> >>>>
>> >>>> --
>> >>>> Prasanna.,
>> >
>> >
>> >>
>> >



-- 
Gavin

Mime
View raw message