You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Alex Huang <Al...@citrix.com> on 2013/02/08 04:45:39 UTC
[DISCUSS] Binary downloads....
>
> Because providing 'binaries' isn't necessarily problematic, but making
> yum and apt repos work in the ASF mirror system seems a bit more of an
> issue. Plus, Wido stepped up to do the work, no one else has offered
> any other alternatives.
>
David,
I apologize if this has all been discussed. And this is off-topic from packaging so I changed the subject.
RPMs don't necessarily have to be from yum repo right? Why can't it just be downloaded from the page along with the source package? Don't get me wrong. Very grateful to Wido for stepping up to help. Not questioning that. It's just that when I visit the download page, it just has a bunch of rpms but nothing to offer in terms of directions on what to do to install. It makes it difficult for new users to get started. What can we do in that area to make it easier?
--Alex
Re: [DISCUSS] Binary downloads....
Posted by Wido den Hollander <wi...@widodh.nl>.
On 02/08/2013 04:56 AM, Alex Huang wrote:
>
>
>> -----Original Message-----
>> From: Alex Huang [mailto:Alex.Huang@citrix.com]
>> Sent: Thursday, February 07, 2013 7:46 PM
>> To: David Nalley
>> Cc: cloudstack-dev@incubator.apache.org
>> Subject: [DISCUSS] Binary downloads....
>>
>>>
>>> Because providing 'binaries' isn't necessarily problematic, but making
>>> yum and apt repos work in the ASF mirror system seems a bit more of an
>>> issue. Plus, Wido stepped up to do the work, no one else has offered
>>> any other alternatives.
>>>
>> David,
>>
>> I apologize if this has all been discussed. And this is off-topic from packaging
>> so I changed the subject.
>>
>> RPMs don't necessarily have to be from yum repo right? Why can't it just be
>> downloaded from the page along with the source package? Don't get me
>> wrong. Very grateful to Wido for stepping up to help. Not questioning that.
>> It's just that when I visit the download page, it just has a bunch of rpms but
>> nothing to offer in terms of directions on what to do to install. It makes it
>> difficult for new users to get started. What can we do in that area to make it
>> easier?
>
> The reason I bring this up is that CloudStack is a mostly java based web app. It's not a given that someone who understands java/j2ee understands linux and yum/apt repos. For them it is somewhat difficult and we should lower that bar. That's where I'm coming from on this.
>
> I do understand packaging into rpms and debs. There's lots of great benefits and of course is a prerequisite to getting into distros but I look forward to the day where we just have a few wars zipped up in tar.gz or .zip and people just download them and deploy them as they would any webapp.
>
That would be a completely different way of packaging.
Right now we expect people to read the docs on how to install from the
repo, we even point to the docs: "Instructions for using these community
provided repositories can be found in the Configure package repository
section of the Installation Guide."
I'm not sure what we should do to package the WAR and JAR files in a
nice way?
Wido
> --Alex
>
Re: [DISCUSS] Binary downloads....
Posted by David Nalley <da...@gnsa.us>.
On Mon, Feb 11, 2013 at 10:52 AM, Hugo Trippaers
<HT...@schubergphilis.com> wrote:
>
>> -----Original Message-----
>> From: David Nalley [mailto:david@gnsa.us]
>> Sent: Monday, February 11, 2013 4:14 PM
>> To: Chip Childers
>> Cc: Alex Huang; Hugo Trippaers; cloudstack-dev@incubator.apache.org
>> Subject: Re: [DISCUSS] Binary downloads....
>>
>> On Mon, Feb 11, 2013 at 10:06 AM, Chip Childers
>> <ch...@sungard.com> wrote:
>> > On Mon, Feb 11, 2013 at 07:00:10AM -0800, Alex Huang wrote:
>> >> > This is done automagically. Everytime we do a successful build on
>> >> > the ASF Jenkins server the resulting artifacts will be uploaded to the ASF
>> repository.
>> >> > This is controlled by the apache master pom that we include in our
>> >> > project. A lot of our artifacts are already there at the moment. We
>> >> > only have publisched SNAPSHOT release though as from a maven point
>> >> > of view we have not made a release yet I think. (This requires
>> >> > triggering a build with a release tag from the Jenkins system afaik).
>> >> >
>> >> > The main think would be to discuss how we want the artifacts to
>> >> > look like. At the moment only the management server is in a shape
>> >> > that it can be distributed as a complete entity. Just pick up the
>> >> > war file and drop it in some java web container. Works for tomcat and
>> jetty at least.
>> >> >
>> >>
>> >> Nice! Thanks Hugo. Then we should be at least be able to make the
>> management server war a downloadable option on our website? Even that
>> would be nice.
>> >>
>> >> --Alex
>> >
>> > I'll try to sort out how to correctly publish 4.1.0-incubating's war
>> > file as part of the release process.
>>
>> I've figured out the maven side of this, just haven't had the cycles to
>> document it.
>>
>> I'm not sure if jenkins will magically publish non-SNAPSHOT artifactos.
>>
>> --David
>
> There is some magic in the maven release plugin. So far I haven't been able to test or use it. But according to specs it should automagically create a signed release, strip the -SNAPSHOT part and publish the release on the listed artifact server. The artifact server will recognize that it is a release (or actually that it is not a snapshot) and make it available on the release artifact store.
Yeah - there is something in the release plugin that does this.
--David
RE: [DISCUSS] Binary downloads....
Posted by Hugo Trippaers <HT...@schubergphilis.com>.
> -----Original Message-----
> From: David Nalley [mailto:david@gnsa.us]
> Sent: Monday, February 11, 2013 4:14 PM
> To: Chip Childers
> Cc: Alex Huang; Hugo Trippaers; cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Binary downloads....
>
> On Mon, Feb 11, 2013 at 10:06 AM, Chip Childers
> <ch...@sungard.com> wrote:
> > On Mon, Feb 11, 2013 at 07:00:10AM -0800, Alex Huang wrote:
> >> > This is done automagically. Everytime we do a successful build on
> >> > the ASF Jenkins server the resulting artifacts will be uploaded to the ASF
> repository.
> >> > This is controlled by the apache master pom that we include in our
> >> > project. A lot of our artifacts are already there at the moment. We
> >> > only have publisched SNAPSHOT release though as from a maven point
> >> > of view we have not made a release yet I think. (This requires
> >> > triggering a build with a release tag from the Jenkins system afaik).
> >> >
> >> > The main think would be to discuss how we want the artifacts to
> >> > look like. At the moment only the management server is in a shape
> >> > that it can be distributed as a complete entity. Just pick up the
> >> > war file and drop it in some java web container. Works for tomcat and
> jetty at least.
> >> >
> >>
> >> Nice! Thanks Hugo. Then we should be at least be able to make the
> management server war a downloadable option on our website? Even that
> would be nice.
> >>
> >> --Alex
> >
> > I'll try to sort out how to correctly publish 4.1.0-incubating's war
> > file as part of the release process.
>
> I've figured out the maven side of this, just haven't had the cycles to
> document it.
>
> I'm not sure if jenkins will magically publish non-SNAPSHOT artifactos.
>
> --David
There is some magic in the maven release plugin. So far I haven't been able to test or use it. But according to specs it should automagically create a signed release, strip the -SNAPSHOT part and publish the release on the listed artifact server. The artifact server will recognize that it is a release (or actually that it is not a snapshot) and make it available on the release artifact store.
Re: [DISCUSS] Binary downloads....
Posted by Chip Childers <ch...@sungard.com>.
On Mon, Feb 11, 2013 at 10:14:19AM -0500, David Nalley wrote:
> On Mon, Feb 11, 2013 at 10:06 AM, Chip Childers
> <ch...@sungard.com> wrote:
> > On Mon, Feb 11, 2013 at 07:00:10AM -0800, Alex Huang wrote:
> >> > This is done automagically. Everytime we do a successful build on the ASF
> >> > Jenkins server the resulting artifacts will be uploaded to the ASF repository.
> >> > This is controlled by the apache master pom that we include in our project. A
> >> > lot of our artifacts are already there at the moment. We only have publisched
> >> > SNAPSHOT release though as from a maven point of view we have not made
> >> > a release yet I think. (This requires triggering a build with a release tag from
> >> > the Jenkins system afaik).
> >> >
> >> > The main think would be to discuss how we want the artifacts to look like. At
> >> > the moment only the management server is in a shape that it can be
> >> > distributed as a complete entity. Just pick up the war file and drop it in some
> >> > java web container. Works for tomcat and jetty at least.
> >> >
> >>
> >> Nice! Thanks Hugo. Then we should be at least be able to make the management server war a downloadable option on our website? Even that would be nice.
> >>
> >> --Alex
> >
> > I'll try to sort out how to correctly publish 4.1.0-incubating's war
> > file as part of the release process.
>
> I've figured out the maven side of this, just haven't had the cycles
> to document it.
>
> I'm not sure if jenkins will magically publish non-SNAPSHOT artifactos.
>
> --David
>
It would be awesome if you could... Like I said, I'd love to "do it
right" for 4.1.0.
Re: [DISCUSS] Binary downloads....
Posted by David Nalley <da...@gnsa.us>.
On Mon, Feb 11, 2013 at 10:06 AM, Chip Childers
<ch...@sungard.com> wrote:
> On Mon, Feb 11, 2013 at 07:00:10AM -0800, Alex Huang wrote:
>> > This is done automagically. Everytime we do a successful build on the ASF
>> > Jenkins server the resulting artifacts will be uploaded to the ASF repository.
>> > This is controlled by the apache master pom that we include in our project. A
>> > lot of our artifacts are already there at the moment. We only have publisched
>> > SNAPSHOT release though as from a maven point of view we have not made
>> > a release yet I think. (This requires triggering a build with a release tag from
>> > the Jenkins system afaik).
>> >
>> > The main think would be to discuss how we want the artifacts to look like. At
>> > the moment only the management server is in a shape that it can be
>> > distributed as a complete entity. Just pick up the war file and drop it in some
>> > java web container. Works for tomcat and jetty at least.
>> >
>>
>> Nice! Thanks Hugo. Then we should be at least be able to make the management server war a downloadable option on our website? Even that would be nice.
>>
>> --Alex
>
> I'll try to sort out how to correctly publish 4.1.0-incubating's war
> file as part of the release process.
I've figured out the maven side of this, just haven't had the cycles
to document it.
I'm not sure if jenkins will magically publish non-SNAPSHOT artifactos.
--David
Re: [DISCUSS] Binary downloads....
Posted by Chip Childers <ch...@sungard.com>.
On Mon, Feb 11, 2013 at 07:00:10AM -0800, Alex Huang wrote:
> > This is done automagically. Everytime we do a successful build on the ASF
> > Jenkins server the resulting artifacts will be uploaded to the ASF repository.
> > This is controlled by the apache master pom that we include in our project. A
> > lot of our artifacts are already there at the moment. We only have publisched
> > SNAPSHOT release though as from a maven point of view we have not made
> > a release yet I think. (This requires triggering a build with a release tag from
> > the Jenkins system afaik).
> >
> > The main think would be to discuss how we want the artifacts to look like. At
> > the moment only the management server is in a shape that it can be
> > distributed as a complete entity. Just pick up the war file and drop it in some
> > java web container. Works for tomcat and jetty at least.
> >
>
> Nice! Thanks Hugo. Then we should be at least be able to make the management server war a downloadable option on our website? Even that would be nice.
>
> --Alex
I'll try to sort out how to correctly publish 4.1.0-incubating's war
file as part of the release process.
RE: [DISCUSS] Binary downloads....
Posted by Alex Huang <Al...@citrix.com>.
> This is done automagically. Everytime we do a successful build on the ASF
> Jenkins server the resulting artifacts will be uploaded to the ASF repository.
> This is controlled by the apache master pom that we include in our project. A
> lot of our artifacts are already there at the moment. We only have publisched
> SNAPSHOT release though as from a maven point of view we have not made
> a release yet I think. (This requires triggering a build with a release tag from
> the Jenkins system afaik).
>
> The main think would be to discuss how we want the artifacts to look like. At
> the moment only the management server is in a shape that it can be
> distributed as a complete entity. Just pick up the war file and drop it in some
> java web container. Works for tomcat and jetty at least.
>
Nice! Thanks Hugo. Then we should be at least be able to make the management server war a downloadable option on our website? Even that would be nice.
--Alex
RE: [DISCUSS] Binary downloads....
Posted by Hugo Trippaers <HT...@schubergphilis.com>.
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Friday, February 08, 2013 3:27 PM
> To: Alex Huang
> Cc: David Nalley; cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Binary downloads....
>
> On Thu, Feb 07, 2013 at 07:56:16PM -0800, Alex Huang wrote:
> >
> >
> > > -----Original Message-----
> > > From: Alex Huang [mailto:Alex.Huang@citrix.com]
> > > Sent: Thursday, February 07, 2013 7:46 PM
> > > To: David Nalley
> > > Cc: cloudstack-dev@incubator.apache.org
> > > Subject: [DISCUSS] Binary downloads....
> > >
> > > >
> > > > Because providing 'binaries' isn't necessarily problematic, but
> > > > making yum and apt repos work in the ASF mirror system seems a bit
> > > > more of an issue. Plus, Wido stepped up to do the work, no one
> > > > else has offered any other alternatives.
> > > >
> > > David,
> > >
> > > I apologize if this has all been discussed. And this is off-topic
> > > from packaging so I changed the subject.
> > >
> > > RPMs don't necessarily have to be from yum repo right? Why can't it
> > > just be downloaded from the page along with the source package?
> > > Don't get me wrong. Very grateful to Wido for stepping up to help. Not
> questioning that.
> > > It's just that when I visit the download page, it just has a bunch
> > > of rpms but nothing to offer in terms of directions on what to do to
> > > install. It makes it difficult for new users to get started. What
> > > can we do in that area to make it easier?
> >
> > The reason I bring this up is that CloudStack is a mostly java based web app.
> It's not a given that someone who understands java/j2ee understands linux
> and yum/apt repos. For them it is somewhat difficult and we should lower
> that bar. That's where I'm coming from on this.
> >
> > I do understand packaging into rpms and debs. There's lots of great
> benefits and of course is a prerequisite to getting into distros but I look
> forward to the day where we just have a few wars zipped up in tar.gz or .zip
> and people just download them and deploy them as they would any
> webapp.
> >
> > --Alex
> >
>
> You could sort out how to publish the jars and wars to the ASF maven repo as
> a starting point for this.
>
> -chip
This is done automagically. Everytime we do a successful build on the ASF Jenkins server the resulting artifacts will be uploaded to the ASF repository. This is controlled by the apache master pom that we include in our project. A lot of our artifacts are already there at the moment. We only have publisched SNAPSHOT release though as from a maven point of view we have not made a release yet I think. (This requires triggering a build with a release tag from the Jenkins system afaik).
The main think would be to discuss how we want the artifacts to look like. At the moment only the management server is in a shape that it can be distributed as a complete entity. Just pick up the war file and drop it in some java web container. Works for tomcat and jetty at least.
Cheers,
Hugo
Re: [DISCUSS] Binary downloads....
Posted by Chip Childers <ch...@sungard.com>.
On Thu, Feb 07, 2013 at 07:56:16PM -0800, Alex Huang wrote:
>
>
> > -----Original Message-----
> > From: Alex Huang [mailto:Alex.Huang@citrix.com]
> > Sent: Thursday, February 07, 2013 7:46 PM
> > To: David Nalley
> > Cc: cloudstack-dev@incubator.apache.org
> > Subject: [DISCUSS] Binary downloads....
> >
> > >
> > > Because providing 'binaries' isn't necessarily problematic, but making
> > > yum and apt repos work in the ASF mirror system seems a bit more of an
> > > issue. Plus, Wido stepped up to do the work, no one else has offered
> > > any other alternatives.
> > >
> > David,
> >
> > I apologize if this has all been discussed. And this is off-topic from packaging
> > so I changed the subject.
> >
> > RPMs don't necessarily have to be from yum repo right? Why can't it just be
> > downloaded from the page along with the source package? Don't get me
> > wrong. Very grateful to Wido for stepping up to help. Not questioning that.
> > It's just that when I visit the download page, it just has a bunch of rpms but
> > nothing to offer in terms of directions on what to do to install. It makes it
> > difficult for new users to get started. What can we do in that area to make it
> > easier?
>
> The reason I bring this up is that CloudStack is a mostly java based web app. It's not a given that someone who understands java/j2ee understands linux and yum/apt repos. For them it is somewhat difficult and we should lower that bar. That's where I'm coming from on this.
>
> I do understand packaging into rpms and debs. There's lots of great benefits and of course is a prerequisite to getting into distros but I look forward to the day where we just have a few wars zipped up in tar.gz or .zip and people just download them and deploy them as they would any webapp.
>
> --Alex
>
You could sort out how to publish the jars and wars to the ASF maven
repo as a starting point for this.
-chip
RE: [DISCUSS] Binary downloads....
Posted by Alex Huang <Al...@citrix.com>.
> -----Original Message-----
> From: Alex Huang [mailto:Alex.Huang@citrix.com]
> Sent: Thursday, February 07, 2013 7:46 PM
> To: David Nalley
> Cc: cloudstack-dev@incubator.apache.org
> Subject: [DISCUSS] Binary downloads....
>
> >
> > Because providing 'binaries' isn't necessarily problematic, but making
> > yum and apt repos work in the ASF mirror system seems a bit more of an
> > issue. Plus, Wido stepped up to do the work, no one else has offered
> > any other alternatives.
> >
> David,
>
> I apologize if this has all been discussed. And this is off-topic from packaging
> so I changed the subject.
>
> RPMs don't necessarily have to be from yum repo right? Why can't it just be
> downloaded from the page along with the source package? Don't get me
> wrong. Very grateful to Wido for stepping up to help. Not questioning that.
> It's just that when I visit the download page, it just has a bunch of rpms but
> nothing to offer in terms of directions on what to do to install. It makes it
> difficult for new users to get started. What can we do in that area to make it
> easier?
The reason I bring this up is that CloudStack is a mostly java based web app. It's not a given that someone who understands java/j2ee understands linux and yum/apt repos. For them it is somewhat difficult and we should lower that bar. That's where I'm coming from on this.
I do understand packaging into rpms and debs. There's lots of great benefits and of course is a prerequisite to getting into distros but I look forward to the day where we just have a few wars zipped up in tar.gz or .zip and people just download them and deploy them as they would any webapp.
--Alex