You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Chip Childers <ch...@sungard.com> on 2012/09/12 21:55:04 UTC
[ASFCS40][DISCUSS] Binary packaging - another round of discussions
that I'd like us to come to a conclusion on.
All,
This is another issue that we need to come to a consensus on (and I
think we can do lazy consensus if required here) prior to 4.0 being
released.
We've variously been discussing how to best provide binary artifacts
from the 4.0 release. Knowing that we are purely discussing
convenience builds for users, and that ASF releases are source only,
I'd like to propose the following approach.
I propose that the project only publishes source tarballs to the ASF
mirrors, and that we rely on the community at large to publish binary
build artifacts.
Wido has volunteered to host deb and rpm repos containing packages
built from the source, and I know that (over time) we will see the
actual distributions put cloudstack packages together. I would
imagine (and am not speaking for Wido), that we could work with Wido
to ensure that his hosted repos have the latest release in them. We
would then be in a position where it's OK if a specific distro
packaging community is a version or two behind the ASF releases. That
scenario would allow us to point users that want the very latest
release to the custom repo, but folks that want official distro
packages can simply use the version being provided by their OS's
packaging system.
For the convenience of the community, I'd further propose that we
provide a set of links to these community repos on our download page
(including appropriate verbiage about the URLs not representing
official ASF release artifacts). This would also include instructions
for how to setup a RHEL/CentOS/Ubuntu system to pull from Wido's
hosted repos.
As for QA teams involved in the testing of ASF releases, I believe
that we should continue to use jenkins.c.o (with Citrix's agreement
and continued support) as the source for downloading packages for
testing. This is because it can do it for us on a nightly schedule.
There is one optional part of this proposal: we include a tarball of
cloudstack jar files on the ASF mirrors. Although, I'm just not sure
what value that provides to the community.
Thoughts?
-chip
Re: [ASFCS40][DISCUSS] Binary packaging - another round of
discussions that I'd like us to come to a conclusion on.
Posted by Noah Slater <ns...@tumbolia.org>.
This recent thread looks very relevant: http://s.apache.org/55E
Now that I understand your question I don't think what you want to do is a
> problem at all.
> As long as you aren't storing GPL components in svn or distributing them
> there should be no
> problem providing plugins that are targeted to third-party systems. See
> http://www.apache.org/legal/resolved.html#platform
On Tue, Oct 2, 2012 at 9:39 AM, Noah Slater <ns...@tumbolia.org> wrote:
> (For clarity, in this email non-OS means "not compatible with the Apache
> license.")
>
> Can you clarify what "link" means in this context? You need to be careful
> with licenses such as the GPL, which expressly prohibit linking (in quite a
> vague sense) unless the your software is also GPL. (Which is what the LGPL
> was for.)
>
> But beyond that, as long as the source tarball that we release contains no
> binaries (of any sort) and nothing that is incompatible with our license,
> then we should be fine. (I am not sure about the build question. In
> general, I don't think it is problematic to have non-OS software on our
> systems. JIRA for example! But we would have to check the specifics with
> Infra.)
>
> Though that does make me wonder about how much non-OS stuff is required on
> the installation machine. I am presuming the core of will work, and it is
> just that some plugins will not work unless you have the required non-OS
> dependancies locally?
>
> In fact, to make doubly sure, is this the situation you're describing:
>
> 1. Build the source release of CloudStack with plugin sources that can
> only be compiled with non-OS software present (note that the compilation
> does not happen during the source release, we only ship the source of them.)
> 2. Prepare binary packages from the source release that compile the
> the non-OS plugins with the non-OS software present (and distribute these
> from non-ASF locations)
> 3. Users download the binary packages and use the non-OS plugins if
> they have that non-OS software locally
>
> For 1) what happens if you're installing form the source release, and you
> don't have the non-OS software present?
>
> For 2) do you need the non-OS software present to compile the plugins when
> preparing the binary package?
>
> For 3) what happens if you're installing from the binary package, and
> don't have the non-OS software present?
>
>
> On Tue, Oct 2, 2012 at 9:14 AM, Rohit Yadav <ro...@citrix.com>wrote:
>
>> Moving binary packaging discussion with Noah from another thread here;
>>
>> >Just a clarification here. It is fine to use, or depend on proprietary
>> >software that exists on the system. During the build, or after install.
>> >"For example, using a GPL'ed tool during the build is OK." [1] The
>> >stipulation is that we cannot ship anything WITH the build that is
>> >incompatible with our license.
>> >
>> >[1] http://www.apache.org/legal/resolved.html
>>
>> Thanks Noah, so if we build CloudStack against nonoss deps/libs (on
>> non-ASF infra, not likely but if possible on ASF infra) and publish the
>> binary (which won't have any non ASF compliant libs/deps/artifacts) on ASF
>> infra that will work?
>> Only the plugins (which are all ASF compliant) are linked against these
>> nonoss libs.
>> If we do this, we won't have to do separate builds, nonoss/oss, less
>> trouble for QA and a user will be just required to install nonoss libs/deps
>> to have the plugins work.
>>
>> Let's do this?
>>
>> Regards.
>>
>> ________________________________________
>> From: Noah Slater [nslater@tumbolia.org]
>> Sent: Sunday, September 30, 2012 11:10 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: [ASFCS40][DISCUSS] Binary packaging - another round of
>> discussions that I'd like us to come to a conclusion on.
>>
>> This all sounds good to me.
>>
>> What would be the difference between the src.tar.gz and the jar one?
>>
>> On Wed, Sep 12, 2012 at 8:55 PM, Chip Childers <chip.childers@sungard.com
>> >wrote:
>>
>> > All,
>> >
>> > This is another issue that we need to come to a consensus on (and I
>> > think we can do lazy consensus if required here) prior to 4.0 being
>> > released.
>> >
>> > We've variously been discussing how to best provide binary artifacts
>> > from the 4.0 release. Knowing that we are purely discussing
>> > convenience builds for users, and that ASF releases are source only,
>> > I'd like to propose the following approach.
>> >
>> > I propose that the project only publishes source tarballs to the ASF
>> > mirrors, and that we rely on the community at large to publish binary
>> > build artifacts.
>> >
>> > Wido has volunteered to host deb and rpm repos containing packages
>> > built from the source, and I know that (over time) we will see the
>> > actual distributions put cloudstack packages together. I would
>> > imagine (and am not speaking for Wido), that we could work with Wido
>> > to ensure that his hosted repos have the latest release in them. We
>> > would then be in a position where it's OK if a specific distro
>> > packaging community is a version or two behind the ASF releases. That
>> > scenario would allow us to point users that want the very latest
>> > release to the custom repo, but folks that want official distro
>> > packages can simply use the version being provided by their OS's
>> > packaging system.
>> >
>> > For the convenience of the community, I'd further propose that we
>> > provide a set of links to these community repos on our download page
>> > (including appropriate verbiage about the URLs not representing
>> > official ASF release artifacts). This would also include instructions
>> > for how to setup a RHEL/CentOS/Ubuntu system to pull from Wido's
>> > hosted repos.
>> >
>> > As for QA teams involved in the testing of ASF releases, I believe
>> > that we should continue to use jenkins.c.o (with Citrix's agreement
>> > and continued support) as the source for downloading packages for
>> > testing. This is because it can do it for us on a nightly schedule.
>> >
>> > There is one optional part of this proposal: we include a tarball of
>> > cloudstack jar files on the ASF mirrors. Although, I'm just not sure
>> > what value that provides to the community.
>> >
>> > Thoughts?
>> >
>> > -chip
>> >
>>
>>
>>
>> --
>> NS
>>
>
>
>
> --
> NS
>
--
NS
Re: [ASFCS40][DISCUSS] Binary packaging - another round of
discussions that I'd like us to come to a conclusion on.
Posted by Noah Slater <ns...@tumbolia.org>.
Thanks for the information! Don't let my confusion put you off. I'm just
making sure we have our ducks in a row. I don't have the time to respond to
this in full today, but I'll come back to this thread tomorrow. However, I
did just want to report back that the first response on legal-discuss seems
to indicate that we can build binary packages that link against legally
incompatible 3rd party software. With the stipulation that this is NOT the
default for users who are building from the source release.
And just to clarify one other point, we will NEVER do a binary release. A
"release" (and thanks for clarifying terminology for me!) is something
which is VOTEd on by the community. We will never vote on binary packages.
We are free to provide them to accompany source releases, as a matter of
convenience. And we can build and host these on ASF infra.
On Thu, Oct 4, 2012 at 12:26 PM, Rohit Yadav <ro...@citrix.com> wrote:
>
> On 04-Oct-2012, at 3:59 PM, Noah Slater <ns...@tumbolia.org> wrote:
>
> > Comments inline.
> >
> > On Thu, Oct 4, 2012 at 11:08 AM, Rohit Yadav <ro...@citrix.com>
> wrote:
> >
> >>
> >> On 04-Oct-2012, at 2:45 PM, Noah Slater <ns...@tumbolia.org> wrote:
> >>
> >>> Can you outline your plan for both the source release and the binary
> >>> packages?
> >>
> >> This is just for binary release. For source release, all the code that
> >> needs to be shipped is already in the repository.
> >
> >
> > We need to be clear that we are not making binary "releases".
>
> I understand that we're making source releases now, I think I mentioned on
> IRC that I'm proposing this for post 4.0.
> Sometimes in future we will be doing releases right?
>
> >
> >
> >>> Will the source release contain the source for all the plugins? (My
> best
> >>> guess is yes, and this sounds fine.)
> >>
> >> Yes, it already does, in plugins/ directory.
> >
> >
> > Okay, cool.
> >
> >
> >>> If you were providing a binary package, why separate out the plugins?
> >>
> >> If all plugins artifacts are in separate deb/rpm packages, user has more
> >> power to decide which plugin she wants and which she does not.
> >> So, if I'm using only xen, I may not want to install kvm, ovm etc.
> >
> >
> > I guess my confusion here stems from my time packaging for Debian proper.
> > You would never bundle a dependancy in a package. You would just build a
> > package for the dependancy, have your main package Depends on it, and let
> > APT handle it.
>
> That is correct, that's why we're hoping not to bundle any deps (oss or
> noss) with the binary releases.
> So, for example plugin-kvm can depend of cloud-agent etc.
>
> >
> > Can you clarify for me what your plan is in this regard?
>
> No plan, just proposal. And a proof of concept using a plugin for deb
> packaging:
> https://github.com/bhaisaab/incubator-cloudstack/tree/debs-maven
>
> > A sample list of
> > package names would probably be illustrative. Do you plan to have a main
> > deb package for "cloudstack" and then have a package for
> > "cloudstack-netapp" which actually bundles manageontap? The way I was
> > originally imagining it is that we would provide a single "cloudstack"
> deb,
>
> This is open for discussion, if we want a monolithic package or few
> monolithic packages or bundle everything in separate pkgs.
>
> For the list of debs and exactly what pkgs I'm proposing see below;
>
> > which includes all of the plugins, and then if the user wanted to
> actually
> > use the netapp plugin, they would install manageontap locally.
> >
> >
> >>> Sounds like a binary package should contain all of the plugins we ship,
> >>> just like a source release.
> >>
> >> Yes, the non-asf/nonoss plugins won't work unless user install the libs
> >> mentioned in 1.
> >
> >
> > I'm confused, because you seem to be agreeing, but in your previous
> > paragraph you seem to be suggesting that the plugins are bundled up along
> > with dependancies in separate packages. Please correct me if I am wrong!
>
> Let me define some terms;
> artifact: any jar, war or target created by maven
> submodule: a subproject, like api, agent
> plugins: they are sub projects and part of the cloudstack source code but
> they're separate out of the core logic
> deps/libs: used interchangeably, these are dependencies used by various
> cloudstack artifacts (jars, wars etc.) to reuse classes, evoke library
> functions and methods
> nonoss libs: such as icontrol, netscaler, vmware jars etc.
>
> Right now, these are the different packages built by the maven jdeb plugin;
>
> Cloudstack pkgs;
>
> ./agent/target/cloud-agent_4.0.0+SNAPSHOT.deb
> ./api/target/cloud-api_4.0.0+SNAPSHOT.deb
>
> ./client/target/cloud-client-ui-4.1.0-SNAPSHOT/target/cloud-client-ui_4.0.0+SNAPSHOT.deb
>
> ./client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/classes/scripts/target/cloud-scripts_4.0.0+SNAPSHOT.deb
> ./client/target/generated-webapp/target/cloud-client-ui_4.0.0+SNAPSHOT.deb
>
> ./client/target/generated-webapp/WEB-INF/classes/scripts/target/cloud-scripts_4.0.0+SNAPSHOT.deb
> ./core/target/cloud-core_4.0.0+SNAPSHOT.deb
> ./scripts/target/cloud-scripts_4.0.0+SNAPSHOT.deb
> ./server/target/cloud-server_4.0.0+SNAPSHOT.deb
> ./setup/target/cloud-client-ui_4.0.0+SNAPSHOT.deb
> ./target/scripts/target/cloud-scripts_4.0.0+SNAPSHOT.deb
> ./target/ui/target/cloud-client-ui_4.0.0+SNAPSHOT.deb
> ./ui/target/cloud-client-ui_4.0.0+SNAPSHOT.deb
>
> Deps, not available on a distr.'s repository bundled here (for example
> gson.jar is not available on ubuntu etc.):
> ./deps/target/cloud-deps_4.0.0+SNAPSHOT.deb
>
> Plugins, in plugins/ directory;
>
> ./deployment-planners/user-concentrated-pod/target/cloud-plugin-planner-user-concentrated-pod_4.0.0+SNAPSHOT.deb
>
> ./deployment-planners/user-dispersing/target/cloud-plugin-planner-user-dispersing_4.0.0+SNAPSHOT.deb
> ./file-systems/netapp/target/cloud-plugin-netapp_4.0.0+SNAPSHOT.deb
>
> ./host-allocators/random/target/cloud-plugin-host-allocator-random_4.0.0+SNAPSHOT.deb
> ./hypervisors/ovm/target/cloud-plugin-hypervisor-ovm_4.0.0+SNAPSHOT.deb
>
> ./hypervisors/vmware/target/cloud-plugin-hypervisor-vmware_4.0.0+SNAPSHOT.deb
> ./hypervisors/xen/target/cloud-plugin-hypervisor-xen_4.0.0+SNAPSHOT.deb
>
> ./network-elements/elastic-loadbalancer/target/cloud-plugin-network-elb_4.0.0+SNAPSHOT.deb
> ./network-elements/f5/target/cloud-plugin-network-f5_4.0.0+SNAPSHOT.deb
>
> ./network-elements/juniper-srx/target/cloud-plugin-network-srx_4.0.0+SNAPSHOT.deb
>
> ./network-elements/netscaler/target/cloud-plugin-network-netscaler_4.0.0+SNAPSHOT.deb
>
> ./network-elements/nicira-nvp/target/cloud-plugin-network-nvp_4.0.0+SNAPSHOT.deb
> ./network-elements/ovs/target/cloud-plugin-network-ovs_4.0.0+SNAPSHOT.deb
>
> ./storage-allocators/random/target/cloud-plugin-storage-allocator-random_4.0.0+SNAPSHOT.deb
>
> ./user-authenticators/ldap/target/cloud-plugin-user-authenticator-ldap_4.0.0+SNAPSHOT.deb
>
> ./user-authenticators/md5/target/cloud-plugin-user-authenticator-md5_4.0.0+SNAPSHOT.deb
>
> ./user-authenticators/plain-text/target/cloud-plugin-user-authenticator-plaintext_4.0.0+SNAPSHOT.deb
>
> >
> >
> >>> This confuses me in the context of the above paragraph. In the above
> >>> paragraph, I understand you to be talking about separating out the
> >> plugins
> >>> for for DEBs and RPMs. But here you seem to be talking about a setup
> >> where
> >>> build.apache.org is fetching 3rd party non-OS software, so that it can
> >>> prepare a binary build that contains all the plugins and is properly
> >> linked.
> >>
> >> You understand correct, my question is, will ASF allow such a process.
> >> It's just like installing gcc and libs and building code and removing
> >> gcc/libs; not that we use gcc or its libs.
> >
> >
> > We need to ask legal-discuss and infra. I have done that now.
>
> Thanks.
>
> On second though, what I'm proposing may become very complex to handle.
> So, I'm dropping the idea. (to be picked up by someone else :)
>
> Regards.
>
>
> >
> > Thanks,
> >
> > --
> > NS
>
>
--
NS
Re: [ASFCS40][DISCUSS] Binary packaging - another round of
discussions that I'd like us to come to a conclusion on.
Posted by Rohit Yadav <ro...@citrix.com>.
On 04-Oct-2012, at 3:59 PM, Noah Slater <ns...@tumbolia.org> wrote:
> Comments inline.
>
> On Thu, Oct 4, 2012 at 11:08 AM, Rohit Yadav <ro...@citrix.com> wrote:
>
>>
>> On 04-Oct-2012, at 2:45 PM, Noah Slater <ns...@tumbolia.org> wrote:
>>
>>> Can you outline your plan for both the source release and the binary
>>> packages?
>>
>> This is just for binary release. For source release, all the code that
>> needs to be shipped is already in the repository.
>
>
> We need to be clear that we are not making binary "releases".
I understand that we're making source releases now, I think I mentioned on IRC that I'm proposing this for post 4.0.
Sometimes in future we will be doing releases right?
>
>
>>> Will the source release contain the source for all the plugins? (My best
>>> guess is yes, and this sounds fine.)
>>
>> Yes, it already does, in plugins/ directory.
>
>
> Okay, cool.
>
>
>>> If you were providing a binary package, why separate out the plugins?
>>
>> If all plugins artifacts are in separate deb/rpm packages, user has more
>> power to decide which plugin she wants and which she does not.
>> So, if I'm using only xen, I may not want to install kvm, ovm etc.
>
>
> I guess my confusion here stems from my time packaging for Debian proper.
> You would never bundle a dependancy in a package. You would just build a
> package for the dependancy, have your main package Depends on it, and let
> APT handle it.
That is correct, that's why we're hoping not to bundle any deps (oss or noss) with the binary releases.
So, for example plugin-kvm can depend of cloud-agent etc.
>
> Can you clarify for me what your plan is in this regard?
No plan, just proposal. And a proof of concept using a plugin for deb packaging:
https://github.com/bhaisaab/incubator-cloudstack/tree/debs-maven
> A sample list of
> package names would probably be illustrative. Do you plan to have a main
> deb package for "cloudstack" and then have a package for
> "cloudstack-netapp" which actually bundles manageontap? The way I was
> originally imagining it is that we would provide a single "cloudstack" deb,
This is open for discussion, if we want a monolithic package or few monolithic packages or bundle everything in separate pkgs.
For the list of debs and exactly what pkgs I'm proposing see below;
> which includes all of the plugins, and then if the user wanted to actually
> use the netapp plugin, they would install manageontap locally.
>
>
>>> Sounds like a binary package should contain all of the plugins we ship,
>>> just like a source release.
>>
>> Yes, the non-asf/nonoss plugins won't work unless user install the libs
>> mentioned in 1.
>
>
> I'm confused, because you seem to be agreeing, but in your previous
> paragraph you seem to be suggesting that the plugins are bundled up along
> with dependancies in separate packages. Please correct me if I am wrong!
Let me define some terms;
artifact: any jar, war or target created by maven
submodule: a subproject, like api, agent
plugins: they are sub projects and part of the cloudstack source code but they're separate out of the core logic
deps/libs: used interchangeably, these are dependencies used by various cloudstack artifacts (jars, wars etc.) to reuse classes, evoke library functions and methods
nonoss libs: such as icontrol, netscaler, vmware jars etc.
Right now, these are the different packages built by the maven jdeb plugin;
Cloudstack pkgs;
./agent/target/cloud-agent_4.0.0+SNAPSHOT.deb
./api/target/cloud-api_4.0.0+SNAPSHOT.deb
./client/target/cloud-client-ui-4.1.0-SNAPSHOT/target/cloud-client-ui_4.0.0+SNAPSHOT.deb
./client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/classes/scripts/target/cloud-scripts_4.0.0+SNAPSHOT.deb
./client/target/generated-webapp/target/cloud-client-ui_4.0.0+SNAPSHOT.deb
./client/target/generated-webapp/WEB-INF/classes/scripts/target/cloud-scripts_4.0.0+SNAPSHOT.deb
./core/target/cloud-core_4.0.0+SNAPSHOT.deb
./scripts/target/cloud-scripts_4.0.0+SNAPSHOT.deb
./server/target/cloud-server_4.0.0+SNAPSHOT.deb
./setup/target/cloud-client-ui_4.0.0+SNAPSHOT.deb
./target/scripts/target/cloud-scripts_4.0.0+SNAPSHOT.deb
./target/ui/target/cloud-client-ui_4.0.0+SNAPSHOT.deb
./ui/target/cloud-client-ui_4.0.0+SNAPSHOT.deb
Deps, not available on a distr.'s repository bundled here (for example gson.jar is not available on ubuntu etc.):
./deps/target/cloud-deps_4.0.0+SNAPSHOT.deb
Plugins, in plugins/ directory;
./deployment-planners/user-concentrated-pod/target/cloud-plugin-planner-user-concentrated-pod_4.0.0+SNAPSHOT.deb
./deployment-planners/user-dispersing/target/cloud-plugin-planner-user-dispersing_4.0.0+SNAPSHOT.deb
./file-systems/netapp/target/cloud-plugin-netapp_4.0.0+SNAPSHOT.deb
./host-allocators/random/target/cloud-plugin-host-allocator-random_4.0.0+SNAPSHOT.deb
./hypervisors/ovm/target/cloud-plugin-hypervisor-ovm_4.0.0+SNAPSHOT.deb
./hypervisors/vmware/target/cloud-plugin-hypervisor-vmware_4.0.0+SNAPSHOT.deb
./hypervisors/xen/target/cloud-plugin-hypervisor-xen_4.0.0+SNAPSHOT.deb
./network-elements/elastic-loadbalancer/target/cloud-plugin-network-elb_4.0.0+SNAPSHOT.deb
./network-elements/f5/target/cloud-plugin-network-f5_4.0.0+SNAPSHOT.deb
./network-elements/juniper-srx/target/cloud-plugin-network-srx_4.0.0+SNAPSHOT.deb
./network-elements/netscaler/target/cloud-plugin-network-netscaler_4.0.0+SNAPSHOT.deb
./network-elements/nicira-nvp/target/cloud-plugin-network-nvp_4.0.0+SNAPSHOT.deb
./network-elements/ovs/target/cloud-plugin-network-ovs_4.0.0+SNAPSHOT.deb
./storage-allocators/random/target/cloud-plugin-storage-allocator-random_4.0.0+SNAPSHOT.deb
./user-authenticators/ldap/target/cloud-plugin-user-authenticator-ldap_4.0.0+SNAPSHOT.deb
./user-authenticators/md5/target/cloud-plugin-user-authenticator-md5_4.0.0+SNAPSHOT.deb
./user-authenticators/plain-text/target/cloud-plugin-user-authenticator-plaintext_4.0.0+SNAPSHOT.deb
>
>
>>> This confuses me in the context of the above paragraph. In the above
>>> paragraph, I understand you to be talking about separating out the
>> plugins
>>> for for DEBs and RPMs. But here you seem to be talking about a setup
>> where
>>> build.apache.org is fetching 3rd party non-OS software, so that it can
>>> prepare a binary build that contains all the plugins and is properly
>> linked.
>>
>> You understand correct, my question is, will ASF allow such a process.
>> It's just like installing gcc and libs and building code and removing
>> gcc/libs; not that we use gcc or its libs.
>
>
> We need to ask legal-discuss and infra. I have done that now.
Thanks.
On second though, what I'm proposing may become very complex to handle.
So, I'm dropping the idea. (to be picked up by someone else :)
Regards.
>
> Thanks,
>
> --
> NS
Re: [ASFCS40][DISCUSS] Binary packaging - another round of
discussions that I'd like us to come to a conclusion on.
Posted by Noah Slater <ns...@tumbolia.org>.
Comments inline.
On Thu, Oct 4, 2012 at 11:08 AM, Rohit Yadav <ro...@citrix.com> wrote:
>
> On 04-Oct-2012, at 2:45 PM, Noah Slater <ns...@tumbolia.org> wrote:
>
> > Can you outline your plan for both the source release and the binary
> > packages?
>
> This is just for binary release. For source release, all the code that
> needs to be shipped is already in the repository.
We need to be clear that we are not making binary "releases".
> > Will the source release contain the source for all the plugins? (My best
> > guess is yes, and this sounds fine.)
>
> Yes, it already does, in plugins/ directory.
Okay, cool.
> > If you were providing a binary package, why separate out the plugins?
>
> If all plugins artifacts are in separate deb/rpm packages, user has more
> power to decide which plugin she wants and which she does not.
> So, if I'm using only xen, I may not want to install kvm, ovm etc.
I guess my confusion here stems from my time packaging for Debian proper.
You would never bundle a dependancy in a package. You would just build a
package for the dependancy, have your main package Depends on it, and let
APT handle it.
Can you clarify for me what your plan is in this regard? A sample list of
package names would probably be illustrative. Do you plan to have a main
deb package for "cloudstack" and then have a package for
"cloudstack-netapp" which actually bundles manageontap? The way I was
originally imagining it is that we would provide a single "cloudstack" deb,
which includes all of the plugins, and then if the user wanted to actually
use the netapp plugin, they would install manageontap locally.
> > Sounds like a binary package should contain all of the plugins we ship,
> > just like a source release.
>
> Yes, the non-asf/nonoss plugins won't work unless user install the libs
> mentioned in 1.
I'm confused, because you seem to be agreeing, but in your previous
paragraph you seem to be suggesting that the plugins are bundled up along
with dependancies in separate packages. Please correct me if I am wrong!
> > This confuses me in the context of the above paragraph. In the above
> > paragraph, I understand you to be talking about separating out the
> plugins
> > for for DEBs and RPMs. But here you seem to be talking about a setup
> where
> > build.apache.org is fetching 3rd party non-OS software, so that it can
> > prepare a binary build that contains all the plugins and is properly
> linked.
>
> You understand correct, my question is, will ASF allow such a process.
> It's just like installing gcc and libs and building code and removing
> gcc/libs; not that we use gcc or its libs.
We need to ask legal-discuss and infra. I have done that now.
Thanks,
--
NS
Re: [ASFCS40][DISCUSS] Binary packaging - another round of
discussions that I'd like us to come to a conclusion on.
Posted by Rohit Yadav <ro...@citrix.com>.
On 04-Oct-2012, at 2:45 PM, Noah Slater <ns...@tumbolia.org> wrote:
> Comments inline.
>
> On Wed, Oct 3, 2012 at 7:40 AM, Rohit Yadav <ro...@citrix.com> wrote:
>
>> 2. While building these required jars are needed to be build against them,
>> linking means only class definitions are verified and the plugin is
>> compiled. No class is copied from these nonoss libs to these plugins. For
>> running these plugins, the above mentioned requirement/deps/jars should be
>> in their class path.
>>
>
> Sounds good.
>
>
>> My proposal is to have individual packages (rpms, debs) for these plugins
>> which won't have any of these non-ASF libs/jars. A user whose has rightful
>> ownership of these non-ASF jars will be just required to install them, and
>> install any of these plugins and configure them correctly in the conf files
>> mentioned in 3.
>>
>
> Confused by this bit.
>
> Can you outline your plan for both the source release and the binary
> packages?
This is just for binary release. For source release, all the code that needs to be shipped is already in the repository.
>
> Will the source release contain the source for all the plugins? (My best
> guess is yes, and this sounds fine.)
Yes, it already does, in plugins/ directory.
>
> If you were providing a binary package, why separate out the plugins?
If all plugins artifacts are in separate deb/rpm packages, user has more power to decide which plugin she wants and which she does not.
So, if I'm using only xen, I may not want to install kvm, ovm etc.
>
> Sounds like a binary package should contain all of the plugins we ship,
> just like a source release.
Yes, the non-asf/nonoss plugins won't work unless user install the libs mentioned in 1.
>
>
>> On build.apache.org, to build cloudstack, we can wget a patch which would
>> contain the non-ASF jars mentioned in 1. from non-ASF hosting, build these
>> CloudStack debs and rpms, and delete this patch.
>>
>
> This confuses me in the context of the above paragraph. In the above
> paragraph, I understand you to be talking about separating out the plugins
> for for DEBs and RPMs. But here you seem to be talking about a setup where
> build.apache.org is fetching 3rd party non-OS software, so that it can
> prepare a binary build that contains all the plugins and is properly linked.
You understand correct, my question is, will ASF allow such a process.
It's just like installing gcc and libs and building code and removing gcc/libs; not that we use gcc or its libs.
>
> Let me re-emphasize, the builds won't contain
>>
>
> Won't contain…?
The build/binary release, won't contain anything that is not compatible with the Apache license.
Thanks for replying,
Rohit
>
>
> --
> NS
Re: [ASFCS40][DISCUSS] Binary packaging - another round of
discussions that I'd like us to come to a conclusion on.
Posted by Noah Slater <ns...@tumbolia.org>.
Comments inline.
On Wed, Oct 3, 2012 at 7:40 AM, Rohit Yadav <ro...@citrix.com> wrote:
> 2. While building these required jars are needed to be build against them,
> linking means only class definitions are verified and the plugin is
> compiled. No class is copied from these nonoss libs to these plugins. For
> running these plugins, the above mentioned requirement/deps/jars should be
> in their class path.
>
Sounds good.
> My proposal is to have individual packages (rpms, debs) for these plugins
> which won't have any of these non-ASF libs/jars. A user whose has rightful
> ownership of these non-ASF jars will be just required to install them, and
> install any of these plugins and configure them correctly in the conf files
> mentioned in 3.
>
Confused by this bit.
Can you outline your plan for both the source release and the binary
packages?
Will the source release contain the source for all the plugins? (My best
guess is yes, and this sounds fine.)
If you were providing a binary package, why separate out the plugins?
Sounds like a binary package should contain all of the plugins we ship,
just like a source release.
> On build.apache.org, to build cloudstack, we can wget a patch which would
> contain the non-ASF jars mentioned in 1. from non-ASF hosting, build these
> CloudStack debs and rpms, and delete this patch.
>
This confuses me in the context of the above paragraph. In the above
paragraph, I understand you to be talking about separating out the plugins
for for DEBs and RPMs. But here you seem to be talking about a setup where
build.apache.org is fetching 3rd party non-OS software, so that it can
prepare a binary build that contains all the plugins and is properly linked.
Let me re-emphasize, the builds won't contain
>
Won't contain...?
--
NS
Re: [ASFCS40][DISCUSS] Binary packaging - another round of
discussions that I'd like us to come to a conclusion on.
Posted by Rohit Yadav <ro...@citrix.com>.
This is the workflow I'm suggesting: (non-ASF = not compatible with Apache license, may be open source or proprietary)
1. There are 5 plugins and vmware-base which are the only part of the source code which requires external/nonoss libs for building and runtime:
a. netapp, requires: manageontap
b. vmware, requires: vmware-{vim, vim25, apputils, jaxrpc}
c. srx, requires: icontrol
d. netscaler, requires: netscalar{,sdk}
e. f5, requires: icontrol
f. vmware-base, requires: vmware-{vim, vim25, apputils}
Note, these plugins and vmware-base are part of CloudStack and are under Apache License.
2. While building these required jars are needed to be build against them, linking means only class definitions are verified and the plugin is compiled. No class is copied from these nonoss libs to these plugins. For running these plugins, the above mentioned requirement/deps/jars should be in their class path.
3. These plugins must be activated in components.xml and class paths added in class path.conf
My proposal is to have individual packages (rpms, debs) for these plugins which won't have any of these non-ASF libs/jars. A user whose has rightful ownership of these non-ASF jars will be just required to install them, and install any of these plugins and configure them correctly in the conf files mentioned in 3.
On build.apache.org, to build cloudstack, we can wget a patch which would contain the non-ASF jars mentioned in 1. from non-ASF hosting, build these CloudStack debs and rpms, and delete this patch.
Let me re-emphasize, the builds won't contain
My question is, it possible to do all of the above?
Regards.
On 02-Oct-2012, at 2:09 PM, Noah Slater <ns...@tumbolia.org> wrote:
> (For clarity, in this email non-OS means "not compatible with the Apache
> license.")
>
> Can you clarify what "link" means in this context? You need to be careful
> with licenses such as the GPL, which expressly prohibit linking (in quite a
> vague sense) unless the your software is also GPL. (Which is what the LGPL
> was for.)
>
> But beyond that, as long as the source tarball that we release contains no
> binaries (of any sort) and nothing that is incompatible with our license,
> then we should be fine. (I am not sure about the build question. In
> general, I don't think it is problematic to have non-OS software on our
> systems. JIRA for example! But we would have to check the specifics with
> Infra.)
>
> Though that does make me wonder about how much non-OS stuff is required on
> the installation machine. I am presuming the core of will work, and it is
> just that some plugins will not work unless you have the required non-OS
> dependancies locally?
>
> In fact, to make doubly sure, is this the situation you're describing:
>
> 1. Build the source release of CloudStack with plugin sources that can
> only be compiled with non-OS software present (note that the compilation
> does not happen during the source release, we only ship the source of them.)
> 2. Prepare binary packages from the source release that compile the the
> non-OS plugins with the non-OS software present (and distribute these from
> non-ASF locations)
> 3. Users download the binary packages and use the non-OS plugins if they
> have that non-OS software locally
>
> For 1) what happens if you're installing form the source release, and you
> don't have the non-OS software present?
>
> For 2) do you need the non-OS software present to compile the plugins when
> preparing the binary package?
>
> For 3) what happens if you're installing from the binary package, and
> don't have the non-OS software present?
>
>
> On Tue, Oct 2, 2012 at 9:14 AM, Rohit Yadav <ro...@citrix.com> wrote:
>
>> Moving binary packaging discussion with Noah from another thread here;
>>
>>> Just a clarification here. It is fine to use, or depend on proprietary
>>> software that exists on the system. During the build, or after install.
>>> "For example, using a GPL'ed tool during the build is OK." [1] The
>>> stipulation is that we cannot ship anything WITH the build that is
>>> incompatible with our license.
>>>
>>> [1] http://www.apache.org/legal/resolved.html
>>
>> Thanks Noah, so if we build CloudStack against nonoss deps/libs (on
>> non-ASF infra, not likely but if possible on ASF infra) and publish the
>> binary (which won't have any non ASF compliant libs/deps/artifacts) on ASF
>> infra that will work?
>> Only the plugins (which are all ASF compliant) are linked against these
>> nonoss libs.
>> If we do this, we won't have to do separate builds, nonoss/oss, less
>> trouble for QA and a user will be just required to install nonoss libs/deps
>> to have the plugins work.
>>
>> Let's do this?
>>
>> Regards.
>>
>> ________________________________________
>> From: Noah Slater [nslater@tumbolia.org]
>> Sent: Sunday, September 30, 2012 11:10 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: [ASFCS40][DISCUSS] Binary packaging - another round of
>> discussions that I'd like us to come to a conclusion on.
>>
>> This all sounds good to me.
>>
>> What would be the difference between the src.tar.gz and the jar one?
>>
>> On Wed, Sep 12, 2012 at 8:55 PM, Chip Childers <chip.childers@sungard.com
>>> wrote:
>>
>>> All,
>>>
>>> This is another issue that we need to come to a consensus on (and I
>>> think we can do lazy consensus if required here) prior to 4.0 being
>>> released.
>>>
>>> We've variously been discussing how to best provide binary artifacts
>>> from the 4.0 release. Knowing that we are purely discussing
>>> convenience builds for users, and that ASF releases are source only,
>>> I'd like to propose the following approach.
>>>
>>> I propose that the project only publishes source tarballs to the ASF
>>> mirrors, and that we rely on the community at large to publish binary
>>> build artifacts.
>>>
>>> Wido has volunteered to host deb and rpm repos containing packages
>>> built from the source, and I know that (over time) we will see the
>>> actual distributions put cloudstack packages together. I would
>>> imagine (and am not speaking for Wido), that we could work with Wido
>>> to ensure that his hosted repos have the latest release in them. We
>>> would then be in a position where it's OK if a specific distro
>>> packaging community is a version or two behind the ASF releases. That
>>> scenario would allow us to point users that want the very latest
>>> release to the custom repo, but folks that want official distro
>>> packages can simply use the version being provided by their OS's
>>> packaging system.
>>>
>>> For the convenience of the community, I'd further propose that we
>>> provide a set of links to these community repos on our download page
>>> (including appropriate verbiage about the URLs not representing
>>> official ASF release artifacts). This would also include instructions
>>> for how to setup a RHEL/CentOS/Ubuntu system to pull from Wido's
>>> hosted repos.
>>>
>>> As for QA teams involved in the testing of ASF releases, I believe
>>> that we should continue to use jenkins.c.o (with Citrix's agreement
>>> and continued support) as the source for downloading packages for
>>> testing. This is because it can do it for us on a nightly schedule.
>>>
>>> There is one optional part of this proposal: we include a tarball of
>>> cloudstack jar files on the ASF mirrors. Although, I'm just not sure
>>> what value that provides to the community.
>>>
>>> Thoughts?
>>>
>>> -chip
>>>
>>
>>
>>
>> --
>> NS
>>
>
>
>
> --
> NS
Re: [ASFCS40][DISCUSS] Binary packaging - another round of
discussions that I'd like us to come to a conclusion on.
Posted by Noah Slater <ns...@tumbolia.org>.
(For clarity, in this email non-OS means "not compatible with the Apache
license.")
Can you clarify what "link" means in this context? You need to be careful
with licenses such as the GPL, which expressly prohibit linking (in quite a
vague sense) unless the your software is also GPL. (Which is what the LGPL
was for.)
But beyond that, as long as the source tarball that we release contains no
binaries (of any sort) and nothing that is incompatible with our license,
then we should be fine. (I am not sure about the build question. In
general, I don't think it is problematic to have non-OS software on our
systems. JIRA for example! But we would have to check the specifics with
Infra.)
Though that does make me wonder about how much non-OS stuff is required on
the installation machine. I am presuming the core of will work, and it is
just that some plugins will not work unless you have the required non-OS
dependancies locally?
In fact, to make doubly sure, is this the situation you're describing:
1. Build the source release of CloudStack with plugin sources that can
only be compiled with non-OS software present (note that the compilation
does not happen during the source release, we only ship the source of them.)
2. Prepare binary packages from the source release that compile the the
non-OS plugins with the non-OS software present (and distribute these from
non-ASF locations)
3. Users download the binary packages and use the non-OS plugins if they
have that non-OS software locally
For 1) what happens if you're installing form the source release, and you
don't have the non-OS software present?
For 2) do you need the non-OS software present to compile the plugins when
preparing the binary package?
For 3) what happens if you're installing from the binary package, and
don't have the non-OS software present?
On Tue, Oct 2, 2012 at 9:14 AM, Rohit Yadav <ro...@citrix.com> wrote:
> Moving binary packaging discussion with Noah from another thread here;
>
> >Just a clarification here. It is fine to use, or depend on proprietary
> >software that exists on the system. During the build, or after install.
> >"For example, using a GPL'ed tool during the build is OK." [1] The
> >stipulation is that we cannot ship anything WITH the build that is
> >incompatible with our license.
> >
> >[1] http://www.apache.org/legal/resolved.html
>
> Thanks Noah, so if we build CloudStack against nonoss deps/libs (on
> non-ASF infra, not likely but if possible on ASF infra) and publish the
> binary (which won't have any non ASF compliant libs/deps/artifacts) on ASF
> infra that will work?
> Only the plugins (which are all ASF compliant) are linked against these
> nonoss libs.
> If we do this, we won't have to do separate builds, nonoss/oss, less
> trouble for QA and a user will be just required to install nonoss libs/deps
> to have the plugins work.
>
> Let's do this?
>
> Regards.
>
> ________________________________________
> From: Noah Slater [nslater@tumbolia.org]
> Sent: Sunday, September 30, 2012 11:10 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ASFCS40][DISCUSS] Binary packaging - another round of
> discussions that I'd like us to come to a conclusion on.
>
> This all sounds good to me.
>
> What would be the difference between the src.tar.gz and the jar one?
>
> On Wed, Sep 12, 2012 at 8:55 PM, Chip Childers <chip.childers@sungard.com
> >wrote:
>
> > All,
> >
> > This is another issue that we need to come to a consensus on (and I
> > think we can do lazy consensus if required here) prior to 4.0 being
> > released.
> >
> > We've variously been discussing how to best provide binary artifacts
> > from the 4.0 release. Knowing that we are purely discussing
> > convenience builds for users, and that ASF releases are source only,
> > I'd like to propose the following approach.
> >
> > I propose that the project only publishes source tarballs to the ASF
> > mirrors, and that we rely on the community at large to publish binary
> > build artifacts.
> >
> > Wido has volunteered to host deb and rpm repos containing packages
> > built from the source, and I know that (over time) we will see the
> > actual distributions put cloudstack packages together. I would
> > imagine (and am not speaking for Wido), that we could work with Wido
> > to ensure that his hosted repos have the latest release in them. We
> > would then be in a position where it's OK if a specific distro
> > packaging community is a version or two behind the ASF releases. That
> > scenario would allow us to point users that want the very latest
> > release to the custom repo, but folks that want official distro
> > packages can simply use the version being provided by their OS's
> > packaging system.
> >
> > For the convenience of the community, I'd further propose that we
> > provide a set of links to these community repos on our download page
> > (including appropriate verbiage about the URLs not representing
> > official ASF release artifacts). This would also include instructions
> > for how to setup a RHEL/CentOS/Ubuntu system to pull from Wido's
> > hosted repos.
> >
> > As for QA teams involved in the testing of ASF releases, I believe
> > that we should continue to use jenkins.c.o (with Citrix's agreement
> > and continued support) as the source for downloading packages for
> > testing. This is because it can do it for us on a nightly schedule.
> >
> > There is one optional part of this proposal: we include a tarball of
> > cloudstack jar files on the ASF mirrors. Although, I'm just not sure
> > what value that provides to the community.
> >
> > Thoughts?
> >
> > -chip
> >
>
>
>
> --
> NS
>
--
NS
RE: [ASFCS40][DISCUSS] Binary packaging - another round of
discussions that I'd like us to come to a conclusion on.
Posted by Rohit Yadav <ro...@citrix.com>.
Moving binary packaging discussion with Noah from another thread here;
>Just a clarification here. It is fine to use, or depend on proprietary
>software that exists on the system. During the build, or after install.
>"For example, using a GPL'ed tool during the build is OK." [1] The
>stipulation is that we cannot ship anything WITH the build that is
>incompatible with our license.
>
>[1] http://www.apache.org/legal/resolved.html
Thanks Noah, so if we build CloudStack against nonoss deps/libs (on non-ASF infra, not likely but if possible on ASF infra) and publish the binary (which won't have any non ASF compliant libs/deps/artifacts) on ASF infra that will work?
Only the plugins (which are all ASF compliant) are linked against these nonoss libs.
If we do this, we won't have to do separate builds, nonoss/oss, less trouble for QA and a user will be just required to install nonoss libs/deps to have the plugins work.
Let's do this?
Regards.
________________________________________
From: Noah Slater [nslater@tumbolia.org]
Sent: Sunday, September 30, 2012 11:10 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [ASFCS40][DISCUSS] Binary packaging - another round of discussions that I'd like us to come to a conclusion on.
This all sounds good to me.
What would be the difference between the src.tar.gz and the jar one?
On Wed, Sep 12, 2012 at 8:55 PM, Chip Childers <ch...@sungard.com>wrote:
> All,
>
> This is another issue that we need to come to a consensus on (and I
> think we can do lazy consensus if required here) prior to 4.0 being
> released.
>
> We've variously been discussing how to best provide binary artifacts
> from the 4.0 release. Knowing that we are purely discussing
> convenience builds for users, and that ASF releases are source only,
> I'd like to propose the following approach.
>
> I propose that the project only publishes source tarballs to the ASF
> mirrors, and that we rely on the community at large to publish binary
> build artifacts.
>
> Wido has volunteered to host deb and rpm repos containing packages
> built from the source, and I know that (over time) we will see the
> actual distributions put cloudstack packages together. I would
> imagine (and am not speaking for Wido), that we could work with Wido
> to ensure that his hosted repos have the latest release in them. We
> would then be in a position where it's OK if a specific distro
> packaging community is a version or two behind the ASF releases. That
> scenario would allow us to point users that want the very latest
> release to the custom repo, but folks that want official distro
> packages can simply use the version being provided by their OS's
> packaging system.
>
> For the convenience of the community, I'd further propose that we
> provide a set of links to these community repos on our download page
> (including appropriate verbiage about the URLs not representing
> official ASF release artifacts). This would also include instructions
> for how to setup a RHEL/CentOS/Ubuntu system to pull from Wido's
> hosted repos.
>
> As for QA teams involved in the testing of ASF releases, I believe
> that we should continue to use jenkins.c.o (with Citrix's agreement
> and continued support) as the source for downloading packages for
> testing. This is because it can do it for us on a nightly schedule.
>
> There is one optional part of this proposal: we include a tarball of
> cloudstack jar files on the ASF mirrors. Although, I'm just not sure
> what value that provides to the community.
>
> Thoughts?
>
> -chip
>
--
NS
Re: [ASFCS40][DISCUSS] Binary packaging - another round of
discussions that I'd like us to come to a conclusion on.
Posted by Chip Childers <ch...@sungard.com>.
On Sun, Sep 30, 2012 at 1:40 PM, Noah Slater <ns...@tumbolia.org> wrote:
> This all sounds good to me.
>
> What would be the difference between the src.tar.gz and the jar one?
The jar archives would be the compiled source. The source build is source only.
I personally don't see any value in publishing compiled code via ASF
infra for now, but anybody can feel free to disagree!
> On Wed, Sep 12, 2012 at 8:55 PM, Chip Childers <ch...@sungard.com>wrote:
>
>> All,
>>
>> This is another issue that we need to come to a consensus on (and I
>> think we can do lazy consensus if required here) prior to 4.0 being
>> released.
>>
>> We've variously been discussing how to best provide binary artifacts
>> from the 4.0 release. Knowing that we are purely discussing
>> convenience builds for users, and that ASF releases are source only,
>> I'd like to propose the following approach.
>>
>> I propose that the project only publishes source tarballs to the ASF
>> mirrors, and that we rely on the community at large to publish binary
>> build artifacts.
>>
>> Wido has volunteered to host deb and rpm repos containing packages
>> built from the source, and I know that (over time) we will see the
>> actual distributions put cloudstack packages together. I would
>> imagine (and am not speaking for Wido), that we could work with Wido
>> to ensure that his hosted repos have the latest release in them. We
>> would then be in a position where it's OK if a specific distro
>> packaging community is a version or two behind the ASF releases. That
>> scenario would allow us to point users that want the very latest
>> release to the custom repo, but folks that want official distro
>> packages can simply use the version being provided by their OS's
>> packaging system.
>>
>> For the convenience of the community, I'd further propose that we
>> provide a set of links to these community repos on our download page
>> (including appropriate verbiage about the URLs not representing
>> official ASF release artifacts). This would also include instructions
>> for how to setup a RHEL/CentOS/Ubuntu system to pull from Wido's
>> hosted repos.
>>
>> As for QA teams involved in the testing of ASF releases, I believe
>> that we should continue to use jenkins.c.o (with Citrix's agreement
>> and continued support) as the source for downloading packages for
>> testing. This is because it can do it for us on a nightly schedule.
>>
>> There is one optional part of this proposal: we include a tarball of
>> cloudstack jar files on the ASF mirrors. Although, I'm just not sure
>> what value that provides to the community.
>>
>> Thoughts?
>>
>> -chip
>>
>
>
>
> --
> NS
Re: [ASFCS40][DISCUSS] Binary packaging - another round of
discussions that I'd like us to come to a conclusion on.
Posted by Noah Slater <ns...@tumbolia.org>.
This all sounds good to me.
What would be the difference between the src.tar.gz and the jar one?
On Wed, Sep 12, 2012 at 8:55 PM, Chip Childers <ch...@sungard.com>wrote:
> All,
>
> This is another issue that we need to come to a consensus on (and I
> think we can do lazy consensus if required here) prior to 4.0 being
> released.
>
> We've variously been discussing how to best provide binary artifacts
> from the 4.0 release. Knowing that we are purely discussing
> convenience builds for users, and that ASF releases are source only,
> I'd like to propose the following approach.
>
> I propose that the project only publishes source tarballs to the ASF
> mirrors, and that we rely on the community at large to publish binary
> build artifacts.
>
> Wido has volunteered to host deb and rpm repos containing packages
> built from the source, and I know that (over time) we will see the
> actual distributions put cloudstack packages together. I would
> imagine (and am not speaking for Wido), that we could work with Wido
> to ensure that his hosted repos have the latest release in them. We
> would then be in a position where it's OK if a specific distro
> packaging community is a version or two behind the ASF releases. That
> scenario would allow us to point users that want the very latest
> release to the custom repo, but folks that want official distro
> packages can simply use the version being provided by their OS's
> packaging system.
>
> For the convenience of the community, I'd further propose that we
> provide a set of links to these community repos on our download page
> (including appropriate verbiage about the URLs not representing
> official ASF release artifacts). This would also include instructions
> for how to setup a RHEL/CentOS/Ubuntu system to pull from Wido's
> hosted repos.
>
> As for QA teams involved in the testing of ASF releases, I believe
> that we should continue to use jenkins.c.o (with Citrix's agreement
> and continued support) as the source for downloading packages for
> testing. This is because it can do it for us on a nightly schedule.
>
> There is one optional part of this proposal: we include a tarball of
> cloudstack jar files on the ASF mirrors. Although, I'm just not sure
> what value that provides to the community.
>
> Thoughts?
>
> -chip
>
--
NS
Re: [ASFCS40][DISCUSS] Binary packaging - another round of discussions
that I'd like us to come to a conclusion on.
Posted by Wido den Hollander <wi...@widodh.nl>.
On 09/12/2012 09:55 PM, Chip Childers wrote:
> All,
>
> This is another issue that we need to come to a consensus on (and I
> think we can do lazy consensus if required here) prior to 4.0 being
> released.
>
> We've variously been discussing how to best provide binary artifacts
> from the 4.0 release. Knowing that we are purely discussing
> convenience builds for users, and that ASF releases are source only,
> I'd like to propose the following approach.
>
> I propose that the project only publishes source tarballs to the ASF
> mirrors, and that we rely on the community at large to publish binary
> build artifacts.
>
> Wido has volunteered to host deb and rpm repos containing packages
> built from the source, and I know that (over time) we will see the
> actual distributions put cloudstack packages together. I would
> imagine (and am not speaking for Wido), that we could work with Wido
> to ensure that his hosted repos have the latest release in them. We
> would then be in a position where it's OK if a specific distro
> packaging community is a version or two behind the ASF releases. That
> scenario would allow us to point users that want the very latest
> release to the custom repo, but folks that want official distro
> packages can simply use the version being provided by their OS's
> packaging system.
>
Getting the packages into the upstream repositories from Ubuntu, Debian
and CentOS will take a lot of time, also, their release cycles are
rather slow, so I think for CloudStack people will prefer packages build
when a new release comes out.
However, it would never hurt if the packages hit the mainstream repos.
> For the convenience of the community, I'd further propose that we
> provide a set of links to these community repos on our download page
> (including appropriate verbiage about the URLs not representing
> official ASF release artifacts). This would also include instructions
> for how to setup a RHEL/CentOS/Ubuntu system to pull from Wido's
> hosted repos.
>
My intention is indeed to modify the documentation and guide people
through installing CS with the repositories, that's much easier for
users and makes unattended installations with Puppet or Chef much easier.
For now I'll be uploading and building the packages manually, but later
on we could have a link with Jenkins so we can have daily or weekly builds.
Wido
> As for QA teams involved in the testing of ASF releases, I believe
> that we should continue to use jenkins.c.o (with Citrix's agreement
> and continued support) as the source for downloading packages for
> testing. This is because it can do it for us on a nightly schedule.
>
> There is one optional part of this proposal: we include a tarball of
> cloudstack jar files on the ASF mirrors. Although, I'm just not sure
> what value that provides to the community.
>
> Thoughts?
>
> -chip
>
Re: [ASFCS40][DISCUSS] Binary packaging - another round of
discussions that I'd like us to come to a conclusion on.
Posted by Chip Childers <ch...@sungard.com>.
On Wed, Sep 12, 2012 at 3:55 PM, Chip Childers
<ch...@sungard.com> wrote:
> All,
>
> This is another issue that we need to come to a consensus on (and I
> think we can do lazy consensus if required here) prior to 4.0 being
> released.
>
> We've variously been discussing how to best provide binary artifacts
> from the 4.0 release. Knowing that we are purely discussing
> convenience builds for users, and that ASF releases are source only,
> I'd like to propose the following approach.
>
> I propose that the project only publishes source tarballs to the ASF
> mirrors, and that we rely on the community at large to publish binary
> build artifacts.
>
> Wido has volunteered to host deb and rpm repos containing packages
> built from the source, and I know that (over time) we will see the
> actual distributions put cloudstack packages together. I would
> imagine (and am not speaking for Wido), that we could work with Wido
> to ensure that his hosted repos have the latest release in them. We
> would then be in a position where it's OK if a specific distro
> packaging community is a version or two behind the ASF releases. That
> scenario would allow us to point users that want the very latest
> release to the custom repo, but folks that want official distro
> packages can simply use the version being provided by their OS's
> packaging system.
>
> For the convenience of the community, I'd further propose that we
> provide a set of links to these community repos on our download page
> (including appropriate verbiage about the URLs not representing
> official ASF release artifacts). This would also include instructions
> for how to setup a RHEL/CentOS/Ubuntu system to pull from Wido's
> hosted repos.
David pointed out subversion does this:
http://subversion.apache.org/packages.html
>
> As for QA teams involved in the testing of ASF releases, I believe
> that we should continue to use jenkins.c.o (with Citrix's agreement
> and continued support) as the source for downloading packages for
> testing. This is because it can do it for us on a nightly schedule.
>
> There is one optional part of this proposal: we include a tarball of
> cloudstack jar files on the ASF mirrors. Although, I'm just not sure
> what value that provides to the community.
>
> Thoughts?
>
> -chip