You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Alex B." <ab...@nflabs.com> on 2015/03/23 04:51:45 UTC
Docker Images for Zeppelin (as release artifacts)
Subj changed, was "Introduction"
AFAIK by apache release policy nothing, except the source code, is
considered to be an 'official release'.
That been said, anything that project finds to be useful to provide to it's
users (without license violations of course) could be done, no special vote
needed, be that 'docker image' or 'convenience binary' - that is up to the
project itself (us).
Using that 'Organization' on docker hub shoudl be fine too, as it looks
like it follows naming conventions for other projects
<http://mail-archives.apache.org/mod_mbox/stratos-dev/201412.mbox/%3CCAGhM-MY6=oTh370Q_5M4VOei41F51Txyew7=TUnKusHU7cR1WA@mail.gmail.com%3E>
On Mon, Mar 23, 2015 at 12:40 PM, moon soo Lee <mo...@apache.org> wrote:
> Some time ago i have created organization 'zeppelin' on docker hub.
> https://registry.hub.docker.com/repos/zeppelin/
> What do you think, Is it good idea to provide docker image through this
> account?
>
> By the way, i'm little bit curious about whether publishing docker image is
> going be a problem with Apache's release policy
> <http://incubator.apache.org/guides/releasemanagement.html> or not. If
> providing docker image is considered as release, could we publish docker
> image with SNAPSHOT suffixes without release vote? Could one of our
> mentor clarify it?
>
> Thanks,
> moon
>
> On Mon, Mar 23, 2015 at 12:18 PM Anthony Corbacho <
> anthonycorbacho@apache.org> wrote:
>
> > Hi,
> >
> > I did one long ago for centOS.
> > I am willing to update it and provide images for different spark version
> as
> > well :)
> >
> > On Mon, Mar 23, 2015 at 12:14 PM, Jongyoul Lee <jo...@gmail.com>
> wrote:
> >
> > > RJ Nowling,
> > >
> > > I make a PR for Integrating Bigtop, I hope it will help Bigtop and
> > > Zeppelin.
> > >
> > > Alex, Anthony Corbacho,
> > >
> > > I made a simple docker container for making debian package. If anyone
> > > thinks it's useful, I'm willing to take mroe effort to publish
> generally.
> > > Give me an opinion.
> > >
> > > Regards,
> > > Jongyoul Lee
> > >
> > >
> > > On Mon, Mar 23, 2015 at 10:07 AM, Anthony Corbacho <
> > > anthonycorbacho@apache.org> wrote:
> > >
> > > > Hey,
> > > >
> > > > I am really interested in providing docker containers too.
> > > > If you guys wants to team up let me know :)
> > > >
> > > >
> > > > On Mon, Mar 23, 2015 at 10:04 AM Alex <ab...@nflabs.com> wrote:
> > > >
> > > > > Jongyoul Lee, RJ Nowling,
> > > > >
> > > > > It is so great to see you guys interested and contributing to
> > Zeppelin,
> > > > > thank you very much!
> > > > >
> > > > > BigTop integration is definitely something we all are very
> interested
> > > in,
> > > > > and having a Docker container for demo purpose with different
> > > > Spark/Hadoop
> > > > > versions is equally important.
> > > > >
> > > > > And we definitely consider all opinions here.
> > > > >
> > > > > Please let me finish migration to Jira today and let's have those
> and
> > > > > others potential issues/ideas logged there.
> > > > >
> > > > > --
> > > > > Kind regards,
> > > > > Alexander
> > > > >
> > > > > > On 23 Mar 2015, at 00:04, Jongyoul Lee <jo...@gmail.com>
> wrote:
> > > > > >
> > > > > > Hi, I'm Jongyoul Lee.
> > > > > >
> > > > > > Youngwoo Kim, who is also a committer on BigTop, already issued
> > > BigTop
> > > > > > integration when I submitted a PR about DEB package, and he will
> > help
> > > > me
> > > > > > when I try to integrate Zeppelin to BigTop. After repo moves to
> > ASF,
> > > > I'll
> > > > > > do the task. Do you consider my opinion? I'm very interested in
> the
> > > > > > Integration.
> > > > > >
> > > > > > Regards,
> > > > > > Jongyoul Lee
> > > > > >
> > > > > >> On Sun, Mar 22, 2015 at 11:37 PM, RJ Nowling <
> rnowling@gmail.com>
> > > > > wrote:
> > > > > >>
> > > > > >> Hi All,
> > > > > >>
> > > > > >> I'm a software engineer in Emerging Technologies (Big Data
> focus)
> > at
> > > > Red
> > > > > >> Hat and committer on BigTop. I'd like to get involved with
> > > developing
> > > > > >> Zeppelin and growing the community.
> > > > > >>
> > > > > >> I can help with BigTop packaging, for example, if no one is
> > > currently
> > > > > >> tackling that. (Once migration is complete, I can go through
> JIRA
> > > > > instead.)
> > > > > >>
> > > > > >> Currently working on getting Zeppelin working (see user list
> > thread)
> > > > > >> locally. I'm going to start looking at Docker containers and
> such
> > to
> > > > > see if
> > > > > >> I'm missing something.
> > > > > >>
> > > > > >> Thanks!
> > > > > >> RJ
> > > > > >
> > > > > >
> > > > > > --
> > > > > > 이종열, Jongyoul Lee, 李宗烈
> > > > > > http://madeng.net
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > 이종열, Jongyoul Lee, 李宗烈
> > > http://madeng.net
> > >
> >
>
--
--
Kind regards,
Alexander.
Re: Docker Images for Zeppelin (as release artifacts)
Posted by Konstantin Boudnik <co...@apache.org>.
On Wed, Mar 25, 2015 at 02:20PM, Roman Shaposhnik wrote:
> On Mon, Mar 23, 2015 at 8:32 PM, moon soo Lee <mo...@apache.org> wrote:
> > Thanks Roman for information about ASF-wide docker index.
> >
> > And, about binary release,
> >> AFAIK by apache release policy nothing, except the source code, is
> >> considered to be an 'official release'.
> >
> > I think Apache's release policy has some guide lines for providing binary
> > package.
> > According to http://www.apache.org/dev/release.html#what, binary package
> > must have the same version number to source release, and unreleased source
> > can not be linked/distributed to the public.
Actually you can linked unreleased source to whoever. What you absolutely CAN
NOT do is to call it a "release" until IPMC has voted on it. If you need to
provide a link to a particular git-tree and call it 'latest stable dev
version' - just do it.
> With binaries the line gets blurry. With things like Docker even more so.
> Keeping those types of guidelines in mind is always useful, but you also
> have to be able to provide software to your users.
>
> Consider Docker: every Docker image typically has a base OS that
> is licensed under variety of different licenses, but GPL is deffintely
> one of them. All of sudden you have a binary 'release' that is under GPL.
> Not longer ALv2.
>
> > So isn't it reasonable to think binary that came from unreleased source
> > code can not be distributed ?
>
> This depends on what distribution means. Like I said in case of Docker
> there's no clear answer and in fact you guys can help shape the outcome.
> Keep an eye on general@incubator and dev@community. A docker discussion
> is coming there very soon.
On top of what Roman said: The main issue with binaries vs source is
that it is hard to guarantee license compliance in case of a binary assembly.
Hence, ASF release is _always_ a release of source code, which ASF legally
stands behind with all rigorous RAT checking, voting, etc. While ASF projects
can and often do provide convenience binary artifacts they CAN NOT have an
official release status because of the above.
Cos
Re: Docker Images for Zeppelin (as release artifacts)
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, Mar 23, 2015 at 8:32 PM, moon soo Lee <mo...@apache.org> wrote:
> Thanks Roman for information about ASF-wide docker index.
>
> And, about binary release,
>> AFAIK by apache release policy nothing, except the source code, is
>> considered to be an 'official release'.
>
> I think Apache's release policy has some guide lines for providing binary
> package.
> According to http://www.apache.org/dev/release.html#what, binary package
> must have the same version number to source release, and unreleased source
> can not be linked/distributed to the public.
With binaries the line gets blurry. With things like Docker even more so.
Keeping those types of guidelines in mind is always useful, but you also
have to be able to provide software to your users.
Consider Docker: every Docker image typically has a base OS that
is licensed under variety of different licenses, but GPL is deffintely
one of them. All of sudden you have a binary 'release' that is under GPL.
Not longer ALv2.
> So isn't it reasonable to think binary that came from unreleased source
> code can not be distributed ?
This depends on what distribution means. Like I said in case of Docker
there's no clear answer and in fact you guys can help shape the outcome.
Keep an eye on general@incubator and dev@community. A docker discussion
is coming there very soon.
Thanks,
Roman.
Re: Docker Images for Zeppelin (as release artifacts)
Posted by moon soo Lee <mo...@apache.org>.
Thanks Roman for information about ASF-wide docker index.
And, about binary release,
> AFAIK by apache release policy nothing, except the source code, is
> considered to be an 'official release'.
I think Apache's release policy has some guide lines for providing binary
package.
According to http://www.apache.org/dev/release.html#what, binary package
must have the same version number to source release, and unreleased source
can not be linked/distributed to the public.
So isn't it reasonable to think binary that came from unreleased source
code can not be distributed ?
Best,
moon
On Tue, Mar 24, 2015 at 3:39 AM Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> FYI: ASF is considering what it would take to have ASF-wide docker index
> presence (and analogy is what we do with github.com). If any of you guys
> plan to be at ApacheCON -- look up Ross Gardlers's talk and make sure
> to drop by.
>
> Thanks,
> Roman.
>
> On Sun, Mar 22, 2015 at 8:51 PM, Alex B. <ab...@nflabs.com> wrote:
> > Subj changed, was "Introduction"
> >
> > AFAIK by apache release policy nothing, except the source code, is
> > considered to be an 'official release'.
> >
> > That been said, anything that project finds to be useful to provide to
> it's
> > users (without license violations of course) could be done, no special
> vote
> > needed, be that 'docker image' or 'convenience binary' - that is up to
> the
> > project itself (us).
> >
> >
> > Using that 'Organization' on docker hub shoudl be fine too, as it looks
> > like it follows naming conventions for other projects
> > <http://mail-archives.apache.org/mod_mbox/stratos-dev/
> 201412.mbox/%3CCAGhM-MY6=oTh370Q_5M4VOei41F51Txyew7=
> TUnKusHU7cR1WA@mail.gmail.com%3E>
> >
> >
> >
> > On Mon, Mar 23, 2015 at 12:40 PM, moon soo Lee <mo...@apache.org> wrote:
> >
> >> Some time ago i have created organization 'zeppelin' on docker hub.
> >> https://registry.hub.docker.com/repos/zeppelin/
> >> What do you think, Is it good idea to provide docker image through this
> >> account?
> >>
> >> By the way, i'm little bit curious about whether publishing docker
> image is
> >> going be a problem with Apache's release policy
> >> <http://incubator.apache.org/guides/releasemanagement.html> or not. If
> >> providing docker image is considered as release, could we publish docker
> >> image with SNAPSHOT suffixes without release vote? Could one of our
> >> mentor clarify it?
> >>
> >> Thanks,
> >> moon
> >>
> >> On Mon, Mar 23, 2015 at 12:18 PM Anthony Corbacho <
> >> anthonycorbacho@apache.org> wrote:
> >>
> >> > Hi,
> >> >
> >> > I did one long ago for centOS.
> >> > I am willing to update it and provide images for different spark
> version
> >> as
> >> > well :)
> >> >
> >> > On Mon, Mar 23, 2015 at 12:14 PM, Jongyoul Lee <jo...@gmail.com>
> >> wrote:
> >> >
> >> > > RJ Nowling,
> >> > >
> >> > > I make a PR for Integrating Bigtop, I hope it will help Bigtop and
> >> > > Zeppelin.
> >> > >
> >> > > Alex, Anthony Corbacho,
> >> > >
> >> > > I made a simple docker container for making debian package. If
> anyone
> >> > > thinks it's useful, I'm willing to take mroe effort to publish
> >> generally.
> >> > > Give me an opinion.
> >> > >
> >> > > Regards,
> >> > > Jongyoul Lee
> >> > >
> >> > >
> >> > > On Mon, Mar 23, 2015 at 10:07 AM, Anthony Corbacho <
> >> > > anthonycorbacho@apache.org> wrote:
> >> > >
> >> > > > Hey,
> >> > > >
> >> > > > I am really interested in providing docker containers too.
> >> > > > If you guys wants to team up let me know :)
> >> > > >
> >> > > >
> >> > > > On Mon, Mar 23, 2015 at 10:04 AM Alex <ab...@nflabs.com>
> wrote:
> >> > > >
> >> > > > > Jongyoul Lee, RJ Nowling,
> >> > > > >
> >> > > > > It is so great to see you guys interested and contributing to
> >> > Zeppelin,
> >> > > > > thank you very much!
> >> > > > >
> >> > > > > BigTop integration is definitely something we all are very
> >> interested
> >> > > in,
> >> > > > > and having a Docker container for demo purpose with different
> >> > > > Spark/Hadoop
> >> > > > > versions is equally important.
> >> > > > >
> >> > > > > And we definitely consider all opinions here.
> >> > > > >
> >> > > > > Please let me finish migration to Jira today and let's have
> those
> >> and
> >> > > > > others potential issues/ideas logged there.
> >> > > > >
> >> > > > > --
> >> > > > > Kind regards,
> >> > > > > Alexander
> >> > > > >
> >> > > > > > On 23 Mar 2015, at 00:04, Jongyoul Lee <jo...@gmail.com>
> >> wrote:
> >> > > > > >
> >> > > > > > Hi, I'm Jongyoul Lee.
> >> > > > > >
> >> > > > > > Youngwoo Kim, who is also a committer on BigTop, already
> issued
> >> > > BigTop
> >> > > > > > integration when I submitted a PR about DEB package, and he
> will
> >> > help
> >> > > > me
> >> > > > > > when I try to integrate Zeppelin to BigTop. After repo moves
> to
> >> > ASF,
> >> > > > I'll
> >> > > > > > do the task. Do you consider my opinion? I'm very interested
> in
> >> the
> >> > > > > > Integration.
> >> > > > > >
> >> > > > > > Regards,
> >> > > > > > Jongyoul Lee
> >> > > > > >
> >> > > > > >> On Sun, Mar 22, 2015 at 11:37 PM, RJ Nowling <
> >> rnowling@gmail.com>
> >> > > > > wrote:
> >> > > > > >>
> >> > > > > >> Hi All,
> >> > > > > >>
> >> > > > > >> I'm a software engineer in Emerging Technologies (Big Data
> >> focus)
> >> > at
> >> > > > Red
> >> > > > > >> Hat and committer on BigTop. I'd like to get involved with
> >> > > developing
> >> > > > > >> Zeppelin and growing the community.
> >> > > > > >>
> >> > > > > >> I can help with BigTop packaging, for example, if no one is
> >> > > currently
> >> > > > > >> tackling that. (Once migration is complete, I can go through
> >> JIRA
> >> > > > > instead.)
> >> > > > > >>
> >> > > > > >> Currently working on getting Zeppelin working (see user list
> >> > thread)
> >> > > > > >> locally. I'm going to start looking at Docker containers and
> >> such
> >> > to
> >> > > > > see if
> >> > > > > >> I'm missing something.
> >> > > > > >>
> >> > > > > >> Thanks!
> >> > > > > >> RJ
> >> > > > > >
> >> > > > > >
> >> > > > > > --
> >> > > > > > 이종열, Jongyoul Lee, 李宗烈
> >> > > > > > http://madeng.net
> >> > > > >
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > 이종열, Jongyoul Lee, 李宗烈
> >> > > http://madeng.net
> >> > >
> >> >
> >>
> >
> >
> >
> > --
> > --
> > Kind regards,
> > Alexander.
>
Re: Docker Images for Zeppelin (as release artifacts)
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
FYI: ASF is considering what it would take to have ASF-wide docker index
presence (and analogy is what we do with github.com). If any of you guys
plan to be at ApacheCON -- look up Ross Gardlers's talk and make sure
to drop by.
Thanks,
Roman.
On Sun, Mar 22, 2015 at 8:51 PM, Alex B. <ab...@nflabs.com> wrote:
> Subj changed, was "Introduction"
>
> AFAIK by apache release policy nothing, except the source code, is
> considered to be an 'official release'.
>
> That been said, anything that project finds to be useful to provide to it's
> users (without license violations of course) could be done, no special vote
> needed, be that 'docker image' or 'convenience binary' - that is up to the
> project itself (us).
>
>
> Using that 'Organization' on docker hub shoudl be fine too, as it looks
> like it follows naming conventions for other projects
> <http://mail-archives.apache.org/mod_mbox/stratos-dev/201412.mbox/%3CCAGhM-MY6=oTh370Q_5M4VOei41F51Txyew7=TUnKusHU7cR1WA@mail.gmail.com%3E>
>
>
>
> On Mon, Mar 23, 2015 at 12:40 PM, moon soo Lee <mo...@apache.org> wrote:
>
>> Some time ago i have created organization 'zeppelin' on docker hub.
>> https://registry.hub.docker.com/repos/zeppelin/
>> What do you think, Is it good idea to provide docker image through this
>> account?
>>
>> By the way, i'm little bit curious about whether publishing docker image is
>> going be a problem with Apache's release policy
>> <http://incubator.apache.org/guides/releasemanagement.html> or not. If
>> providing docker image is considered as release, could we publish docker
>> image with SNAPSHOT suffixes without release vote? Could one of our
>> mentor clarify it?
>>
>> Thanks,
>> moon
>>
>> On Mon, Mar 23, 2015 at 12:18 PM Anthony Corbacho <
>> anthonycorbacho@apache.org> wrote:
>>
>> > Hi,
>> >
>> > I did one long ago for centOS.
>> > I am willing to update it and provide images for different spark version
>> as
>> > well :)
>> >
>> > On Mon, Mar 23, 2015 at 12:14 PM, Jongyoul Lee <jo...@gmail.com>
>> wrote:
>> >
>> > > RJ Nowling,
>> > >
>> > > I make a PR for Integrating Bigtop, I hope it will help Bigtop and
>> > > Zeppelin.
>> > >
>> > > Alex, Anthony Corbacho,
>> > >
>> > > I made a simple docker container for making debian package. If anyone
>> > > thinks it's useful, I'm willing to take mroe effort to publish
>> generally.
>> > > Give me an opinion.
>> > >
>> > > Regards,
>> > > Jongyoul Lee
>> > >
>> > >
>> > > On Mon, Mar 23, 2015 at 10:07 AM, Anthony Corbacho <
>> > > anthonycorbacho@apache.org> wrote:
>> > >
>> > > > Hey,
>> > > >
>> > > > I am really interested in providing docker containers too.
>> > > > If you guys wants to team up let me know :)
>> > > >
>> > > >
>> > > > On Mon, Mar 23, 2015 at 10:04 AM Alex <ab...@nflabs.com> wrote:
>> > > >
>> > > > > Jongyoul Lee, RJ Nowling,
>> > > > >
>> > > > > It is so great to see you guys interested and contributing to
>> > Zeppelin,
>> > > > > thank you very much!
>> > > > >
>> > > > > BigTop integration is definitely something we all are very
>> interested
>> > > in,
>> > > > > and having a Docker container for demo purpose with different
>> > > > Spark/Hadoop
>> > > > > versions is equally important.
>> > > > >
>> > > > > And we definitely consider all opinions here.
>> > > > >
>> > > > > Please let me finish migration to Jira today and let's have those
>> and
>> > > > > others potential issues/ideas logged there.
>> > > > >
>> > > > > --
>> > > > > Kind regards,
>> > > > > Alexander
>> > > > >
>> > > > > > On 23 Mar 2015, at 00:04, Jongyoul Lee <jo...@gmail.com>
>> wrote:
>> > > > > >
>> > > > > > Hi, I'm Jongyoul Lee.
>> > > > > >
>> > > > > > Youngwoo Kim, who is also a committer on BigTop, already issued
>> > > BigTop
>> > > > > > integration when I submitted a PR about DEB package, and he will
>> > help
>> > > > me
>> > > > > > when I try to integrate Zeppelin to BigTop. After repo moves to
>> > ASF,
>> > > > I'll
>> > > > > > do the task. Do you consider my opinion? I'm very interested in
>> the
>> > > > > > Integration.
>> > > > > >
>> > > > > > Regards,
>> > > > > > Jongyoul Lee
>> > > > > >
>> > > > > >> On Sun, Mar 22, 2015 at 11:37 PM, RJ Nowling <
>> rnowling@gmail.com>
>> > > > > wrote:
>> > > > > >>
>> > > > > >> Hi All,
>> > > > > >>
>> > > > > >> I'm a software engineer in Emerging Technologies (Big Data
>> focus)
>> > at
>> > > > Red
>> > > > > >> Hat and committer on BigTop. I'd like to get involved with
>> > > developing
>> > > > > >> Zeppelin and growing the community.
>> > > > > >>
>> > > > > >> I can help with BigTop packaging, for example, if no one is
>> > > currently
>> > > > > >> tackling that. (Once migration is complete, I can go through
>> JIRA
>> > > > > instead.)
>> > > > > >>
>> > > > > >> Currently working on getting Zeppelin working (see user list
>> > thread)
>> > > > > >> locally. I'm going to start looking at Docker containers and
>> such
>> > to
>> > > > > see if
>> > > > > >> I'm missing something.
>> > > > > >>
>> > > > > >> Thanks!
>> > > > > >> RJ
>> > > > > >
>> > > > > >
>> > > > > > --
>> > > > > > 이종열, Jongyoul Lee, 李宗烈
>> > > > > > http://madeng.net
>> > > > >
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > 이종열, Jongyoul Lee, 李宗烈
>> > > http://madeng.net
>> > >
>> >
>>
>
>
>
> --
> --
> Kind regards,
> Alexander.