You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Tellier Benoit <bt...@apache.org> on 2020/11/18 07:49:48 UTC
apache/james on docker hub.
Hello,
Following this thread:
I would like us to start as part as the release process to publish
convenience binaries under apache name, just like some other Apache
projects are doing: https://issues.apache.org/jira/browse/INFRA-19650
I propose to ask for rights on apache/james repository
I propose to use apache/james:flavor:version as a naming pattern.
Committers, I can include you in the request, so in case you are
interested communicate me your dockerhub id.
Cheers,
Benoit
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: apache/james on docker hub.
Posted by Jean Helou <je...@gmail.com>.
Hi benoit,
> This would look like what Juhan proposed in
> https://issues.apache.org/jira/browse/JAMES-3565 ...
>
> Thoughts?
>
interesting, I'll comment with ideas over there thanks
jean
Re: apache/james on docker hub.
Posted by Tellier Benoit <bt...@apache.org>.
Hello Jean,
Answer inlined...
Le 15/04/2021 à 19:01, Jean Helou a écrit :
>> Following the 3.6.0 release I experimented with dockerhub and pushed the
>> following images:
>>
> THANK YOU ! (yes with caps because that's how grateful I am !)
>
> I also propose to timely edit the existing configuration to:
>> - No longer use linagora repository for Apache James docker images
>> distribution
>>
> - Only rely on released docker images (no longer branch master) to
>> better fit in Apache release policies
>>
> I saw the corresponding PR :+1:
>
>
>> To be fairly honest building these images took me too much time. I would
>> highly appreciate automation of docker images construction as part of
>> the maven build. A way to do it is JIB. [1]
>
> That's what I used to build my pure SMTP relay server assembly, it's being
> polished but jib works great :)
>
> demonstrate building a james
>> server image variation for a tierce project so I propose to do something
>> similar, except without requiring a docker daemon. It includes CLI,
>> glowroot, etc... We had been using this JIB generated image on
>> production without problems. I propose we target something similar for
>> James docker image generation. As part of the release process we would
>> then need to load, then push the maven build results. This would lead to
>> the removal of /dockerfiles folder (more or less).
>>
> Since docker images are not considered release artifacts under apache
> policy (if I understand correctly) would it make sense to try and fully
> automate the image building post release ?
> add a piece to the jenkinsfile that monitors only tags, and builds the jib
> image downloading the artifacts from maven central
This argument make sense.
Maybe we could push automatically RCs to docker hub automatically upon
tagging (before the voting process), then once the vote pass just rename
the images?
That way:
- It is automatic and convenient
- We make it clear the artifact is not to be used yet
This would look like what Juhan proposed in
https://issues.apache.org/jira/browse/JAMES-3565 ...
Thoughts?
Cheers,
Benoit
>
>
>> [1]
>>
>> https://github.com/linagora/openpaas-james/tree/master/openpaas-james/apps/memory
>> README and pom.xml are of interest.
>>
>> Cheers,
>>
>> Benoit
>>
>> Le 11/12/2020 à 16:29, Tellier Benoit a écrit :
>>> You're right,
>>>
>>> I did not follow up on this.
>>>
>>> I just created the INFRA ticket.
>>> https://issues.apache.org/jira/browse/INFRA-21180
>>>
>>> As far as I understand, this is not an official release channel but
>>> rather a convenience one.
>>>
>>> Cheers,
>>>
>>> Benoit
>>>
>>> Le 11/12/2020 à 15:18, Jean Helou a écrit :
>>>>> I propose to ask for rights on apache/james repository
>>>> I'm revisiting this thread after seeing
>>>> https://www.docker.com/blog/supporting-open-source-projects-at-docker
>> which
>>>> reminded me of this effort and I was wondering if an INFRA ticket has
>> been
>>>> opened for james (of if there is a trace of the progress somewhere)
>>>> I'm not sur exactly how the program works but if it whitelists prefixes,
>>>> Apache is most likely already in it however in light of the work on CI
>>>> builds on apache infrastructure, I am wondering if/how the credentials
>> for
>>>> pushing form CI can be setup and I was hoping to drop a comment on the
>>>> corresponding ticket.
>>>>
>>>> jean
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>>> For additional commands, e-mail: server-dev-help@james.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-dev-help@james.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: apache/james on docker hub.
Posted by Jean Helou <je...@gmail.com>.
> Following the 3.6.0 release I experimented with dockerhub and pushed the
> following images:
>
THANK YOU ! (yes with caps because that's how grateful I am !)
I also propose to timely edit the existing configuration to:
> - No longer use linagora repository for Apache James docker images
> distribution
>
- Only rely on released docker images (no longer branch master) to
> better fit in Apache release policies
>
I saw the corresponding PR :+1:
> To be fairly honest building these images took me too much time. I would
> highly appreciate automation of docker images construction as part of
> the maven build. A way to do it is JIB. [1]
That's what I used to build my pure SMTP relay server assembly, it's being
polished but jib works great :)
demonstrate building a james
> server image variation for a tierce project so I propose to do something
> similar, except without requiring a docker daemon. It includes CLI,
> glowroot, etc... We had been using this JIB generated image on
> production without problems. I propose we target something similar for
> James docker image generation. As part of the release process we would
> then need to load, then push the maven build results. This would lead to
> the removal of /dockerfiles folder (more or less).
>
Since docker images are not considered release artifacts under apache
policy (if I understand correctly) would it make sense to try and fully
automate the image building post release ?
add a piece to the jenkinsfile that monitors only tags, and builds the jib
image downloading the artifacts from maven central
> [1]
>
> https://github.com/linagora/openpaas-james/tree/master/openpaas-james/apps/memory
> README and pom.xml are of interest.
>
> Cheers,
>
> Benoit
>
> Le 11/12/2020 à 16:29, Tellier Benoit a écrit :
> > You're right,
> >
> > I did not follow up on this.
> >
> > I just created the INFRA ticket.
> > https://issues.apache.org/jira/browse/INFRA-21180
> >
> > As far as I understand, this is not an official release channel but
> > rather a convenience one.
> >
> > Cheers,
> >
> > Benoit
> >
> > Le 11/12/2020 à 15:18, Jean Helou a écrit :
> >>> I propose to ask for rights on apache/james repository
> >>
> >> I'm revisiting this thread after seeing
> >> https://www.docker.com/blog/supporting-open-source-projects-at-docker
> which
> >> reminded me of this effort and I was wondering if an INFRA ticket has
> been
> >> opened for james (of if there is a trace of the progress somewhere)
> >> I'm not sur exactly how the program works but if it whitelists prefixes,
> >> Apache is most likely already in it however in light of the work on CI
> >> builds on apache infrastructure, I am wondering if/how the credentials
> for
> >> pushing form CI can be setup and I was hoping to drop a comment on the
> >> corresponding ticket.
> >>
> >> jean
> >>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> > For additional commands, e-mail: server-dev-help@james.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
Re: apache/james on docker hub.
Posted by Tellier Benoit <bt...@apache.org>.
Hello there,
Following the 3.6.0 release I experimented with dockerhub and pushed the
following images:
- apache/james:memory-3.x.x built from
https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/memory
- apache/james:jpa-3.x.x built from
https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/jpa
- apache/james:demo-3.x.x built from
https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/provisioned
- apache/james:cassandra-3.x.x build from
https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/cassandra
- apache/james:distributed-3.x.x built from
https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/cassandra-rabbitmq
I however do not have the rights to manage the repository, hence can't
add a description / overview just like apache/tika repo did. I opened
INFRA-21718 regarding this.
I also propose to timely edit the existing configuration to:
- No longer use linagora repository for Apache James docker images
distribution
- Only rely on released docker images (no longer branch master) to
better fit in Apache release policies
To be fairly honest building these images took me too much time. I would
highly appreciate automation of docker images construction as part of
the maven build. A way to do it is JIB. [1] demonstrate building a james
server image variation for a tierce project so I propose to do something
similar, except without requiring a docker daemon. It includes CLI,
glowroot, etc... We had been using this JIB generated image on
production without problems. I propose we target something similar for
James docker image generation. As part of the release process we would
then need to load, then push the maven build results. This would lead to
the removal of /dockerfiles folder (more or less).
[1]
https://github.com/linagora/openpaas-james/tree/master/openpaas-james/apps/memory
README and pom.xml are of interest.
Cheers,
Benoit
Le 11/12/2020 à 16:29, Tellier Benoit a écrit :
> You're right,
>
> I did not follow up on this.
>
> I just created the INFRA ticket.
> https://issues.apache.org/jira/browse/INFRA-21180
>
> As far as I understand, this is not an official release channel but
> rather a convenience one.
>
> Cheers,
>
> Benoit
>
> Le 11/12/2020 à 15:18, Jean Helou a écrit :
>>> I propose to ask for rights on apache/james repository
>>
>> I'm revisiting this thread after seeing
>> https://www.docker.com/blog/supporting-open-source-projects-at-docker which
>> reminded me of this effort and I was wondering if an INFRA ticket has been
>> opened for james (of if there is a trace of the progress somewhere)
>> I'm not sur exactly how the program works but if it whitelists prefixes,
>> Apache is most likely already in it however in light of the work on CI
>> builds on apache infrastructure, I am wondering if/how the credentials for
>> pushing form CI can be setup and I was hoping to drop a comment on the
>> corresponding ticket.
>>
>> jean
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: apache/james on docker hub.
Posted by Tellier Benoit <bt...@apache.org>.
You're right,
I did not follow up on this.
I just created the INFRA ticket.
https://issues.apache.org/jira/browse/INFRA-21180
As far as I understand, this is not an official release channel but
rather a convenience one.
Cheers,
Benoit
Le 11/12/2020 à 15:18, Jean Helou a écrit :
>>
>> I propose to ask for rights on apache/james repository
>
>
> I'm revisiting this thread after seeing
> https://www.docker.com/blog/supporting-open-source-projects-at-docker which
> reminded me of this effort and I was wondering if an INFRA ticket has been
> opened for james (of if there is a trace of the progress somewhere)
> I'm not sur exactly how the program works but if it whitelists prefixes,
> Apache is most likely already in it however in light of the work on CI
> builds on apache infrastructure, I am wondering if/how the credentials for
> pushing form CI can be setup and I was hoping to drop a comment on the
> corresponding ticket.
>
> jean
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: apache/james on docker hub.
Posted by Jean Helou <je...@gmail.com>.
>
> I propose to ask for rights on apache/james repository
I'm revisiting this thread after seeing
https://www.docker.com/blog/supporting-open-source-projects-at-docker which
reminded me of this effort and I was wondering if an INFRA ticket has been
opened for james (of if there is a trace of the progress somewhere)
I'm not sur exactly how the program works but if it whitelists prefixes,
Apache is most likely already in it however in light of the work on CI
builds on apache infrastructure, I am wondering if/how the credentials for
pushing form CI can be setup and I was hoping to drop a comment on the
corresponding ticket.
jean
Re: apache/james on docker hub.
Posted by Jean Helou <je...@gmail.com>.
>
> I like the idea, and I would be happy to defend the idea within
>> Linagora, but I need a working build on Apache infra first. Likely it
>> would be a few "dedicated servers", but it would also need internal
>> validation.
>
>
AWS also has this kind of program :
https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects/
> Jean
>
Re: apache/james on docker hub.
Posted by Tellier Benoit <bt...@apache.org>.
Le 18/11/2020 à 16:09, Jean Helou a écrit :
> [...]
>> I am not sure where other apache projects source the machines
>>
>> running the CI but at least https://github.com/apache/pulsar-helm-chart
>>> seems to have access to some serious compute power...
>> INFRA is by default not powerful (likely not enough). A way out is
>> "donating computing power for dedicated project builds".
>>
>> Hence we would need some individual/organization donating computing
>> power to the Apache foundation for Apache James usage.
>>
>> I like the idea, and I would be happy to defend the idea within
>> Linagora, but I need a working build on Apache infra first. Likely it
>> would be a few "dedicated servers", but it would also need internal
>> validation.
>>
>>
> I have asked a friend who may be able to help, I also found
> https://www.scaleway.com/en/about-us/open-source-program/ which seems
> promising. It starts by sending an email to opensource-program@scaleway.com
> Scaleway is where I intend to run my SMTP relay (using my own compute
> resources) once it is finished assembling, I started working on a helm
> chart that's deployed on scaleway Kapsule.
> Once it works reasonably well, I intend to contribute it back to
> james/apache but that's gonna take a while
Thanks for sharing!
>
> Jean
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: apache/james on docker hub.
Posted by Jean Helou <je...@gmail.com>.
>
> I would love to see this happening but I fail at seeing progress on the
> Apache level CI for several months already.
thanks for clarifying the context :/
Correlating things together would likely lead to getting nothing done.
Indeed
> I am not sure where other apache projects source the machines
>
> running the CI but at least https://github.com/apache/pulsar-helm-chart
> > seems to have access to some serious compute power...
>
> INFRA is by default not powerful (likely not enough). A way out is
> "donating computing power for dedicated project builds".
>
> Hence we would need some individual/organization donating computing
> power to the Apache foundation for Apache James usage.
>
> I like the idea, and I would be happy to defend the idea within
> Linagora, but I need a working build on Apache infra first. Likely it
> would be a few "dedicated servers", but it would also need internal
> validation.
>
>
I have asked a friend who may be able to help, I also found
https://www.scaleway.com/en/about-us/open-source-program/ which seems
promising. It starts by sending an email to opensource-program@scaleway.com
Scaleway is where I intend to run my SMTP relay (using my own compute
resources) once it is finished assembling, I started working on a helm
chart that's deployed on scaleway Kapsule.
Once it works reasonably well, I intend to contribute it back to
james/apache but that's gonna take a while
Jean
Re: apache/james on docker hub.
Posted by Tellier Benoit <bt...@apache.org>.
Le 18/11/2020 à 15:00, Jean Helou a écrit :
>> I would like us to start as part as the release process to publish
>> convenience binaries under apache name, just like some other Apache
>> projects are doing: https://issues.apache.org/jira/browse/INFRA-19650
>
>
> This is a bit of a shameless suggestion but wouldn't it make sense to use
> the opportunity to setup an automated public CI ?
I would love to see this happening but I fail at seeing progress on the
Apache level CI for several months already.
Correlating things together would likely lead to getting nothing done.
I am willing to add publishing docker images to the release process, but
will not find the resources to make this automated public CI happen.
Note that asking dockerhub access is not incompatible with CI work.
> Something that
> automatically publishes release versions from master, and builds PRs would
> be nice.
Something that automatically builds master branch and peoples PR should
IMO have a higher priority.
BTW given
http://www.apache.org/legal/release-policy.html#approving-a-release a
two stage process would likely be needed.
> I am not sure where other apache projects source the machines
> running the CI but at least https://github.com/apache/pulsar-helm-chart
> seems to have access to some serious compute power...
INFRA is by default not powerful (likely not enough). A way out is
"donating computing power for dedicated project builds".
Hence we would need some individual/organization donating computing
power to the Apache foundation for Apache James usage.
I like the idea, and I would be happy to defend the idea within
Linagora, but I need a working build on Apache infra first. Likely it
would be a few "dedicated servers", but it would also need internal
validation.
Benoit
> with a bit of luck
> that could also benefit from shared credentials to push apache docker
> images without needing any single user to have specific rights>
> jean
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: apache/james on docker hub.
Posted by Jean Helou <je...@gmail.com>.
> I would like us to start as part as the release process to publish
> convenience binaries under apache name, just like some other Apache
> projects are doing: https://issues.apache.org/jira/browse/INFRA-19650
This is a bit of a shameless suggestion but wouldn't it make sense to use
the opportunity to setup an automated public CI ? Something that
automatically publishes release versions from master, and builds PRs would
be nice. I am not sure where other apache projects source the machines
running the CI but at least https://github.com/apache/pulsar-helm-chart
seems to have access to some serious compute power...with a bit of luck
that could also benefit from shared credentials to push apache docker
images without needing any single user to have specific rights
jean