Ignite | Webconsole Dockerfile unifications in 2.4

[vveider]

Hi, Igniters!


In order to correctly process Apache Ignite 2.4 release, I've implemented
several changes in Apache Ignite's and Web Console's docker build procedure
[1].
My main motivation was to:
1. Unify approach to docker image architecture. Previously, Apache Ignite
docker image build procedure was designed for DockerHub autobuild. Yet,
there are plans for a) moving Apache Ignite docker image to official docker
repository [2] and b) including docker image building into release procedure
(+ QA, release binaries are tested before release). Now the architecture is
common with Web Console's one - Dockerfile redesigned to build image from
locally acquired Apache Ignite's binary archive.
2. Unify approach for container deliveries. I've replaced Web Console's
custom build script with instructions about how to obtain necessary files
for docker image, thus simplifying it and making more transparent. Now
images are constructed from built sources in almost single command.

Need help with review [3] and merge to master and ignite-2.4 branches - so
it will be possible to create and upload docker release images without pain.
Corresponding documentations is in preparation.


[1] https://issues.apache.org/jira/browse/IGNITE-7821
[2] https://hub.docker.com/explore
[3] https://github.com/apache/ignite/pull/3574



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[dmagda]

Peter,

Thanks for keep automating and improving Ignite build/release environment!
Igniters, who can review the changes?

However, I guess that it's too late to merge the changes into 2.4 branch
which is frozen for merges.

Considering this, could you prepare docker as well as cloud images (AWS,
google compute engine) for 2.4 manually?

--
Denis


On Tue, Feb 27, 2018 at 4:16 AM, vveider <[hidden email]> wrote:

> Hi, Igniters!
>
>
> In order to correctly process Apache Ignite 2.4 release, I've implemented
> several changes in Apache Ignite's and Web Console's docker build procedure
> [1].
> My main motivation was to:
> 1. Unify approach to docker image architecture. Previously, Apache Ignite
> docker image build procedure was designed for DockerHub autobuild. Yet,
> there are plans for a) moving Apache Ignite docker image to official docker
> repository [2] and b) including docker image building into release
> procedure
> (+ QA, release binaries are tested before release). Now the architecture is
> common with Web Console's one - Dockerfile redesigned to build image from
> locally acquired Apache Ignite's binary archive.
> 2. Unify approach for container deliveries. I've replaced Web Console's
> custom build script with instructions about how to obtain necessary files
> for docker image, thus simplifying it and making more transparent. Now
> images are constructed from built sources in almost single command.
>
> Need help with review [3] and merge to master and ignite-2.4 branches - so
> it will be possible to create and upload docker release images without
> pain.
> Corresponding documentations is in preparation.
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-7821
> [2] https://hub.docker.com/explore
> [3] https://github.com/apache/ignite/pull/3574
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[vveider]

Hi, Denis.


I guess I’ll be able to cherry-pick my changes to release tag and use resulting project state to build and create docker images, however that won’t be 100% binary compatible with what was tested and release (uploaded to ASF). Though that must not be a problem currently, and at 2.5 I’d like to add docker image creation to release procedure.

> On 28 Feb 2018, at 07:20, Denis Magda <[hidden email]> wrote:
>
> Peter,
>
> Thanks for keep automating and improving Ignite build/release environment!
> Igniters, who can review the changes?
>
> However, I guess that it's too late to merge the changes into 2.4 branch
> which is frozen for merges.
>
> Considering this, could you prepare docker as well as cloud images (AWS,
> google compute engine) for 2.4 manually?
>
> --
> Denis
>
>
> On Tue, Feb 27, 2018 at 4:16 AM, vveider <[hidden email]> wrote:
>
>> Hi, Igniters!
>>
>>
>> In order to correctly process Apache Ignite 2.4 release, I've implemented
>> several changes in Apache Ignite's and Web Console's docker build procedure
>> [1].
>> My main motivation was to:
>> 1. Unify approach to docker image architecture. Previously, Apache Ignite
>> docker image build procedure was designed for DockerHub autobuild. Yet,
>> there are plans for a) moving Apache Ignite docker image to official docker
>> repository [2] and b) including docker image building into release
>> procedure
>> (+ QA, release binaries are tested before release). Now the architecture is
>> common with Web Console's one - Dockerfile redesigned to build image from
>> locally acquired Apache Ignite's binary archive.
>> 2. Unify approach for container deliveries. I've replaced Web Console's
>> custom build script with instructions about how to obtain necessary files
>> for docker image, thus simplifying it and making more transparent. Now
>> images are constructed from built sources in almost single command.
>>
>> Need help with review [3] and merge to master and ignite-2.4 branches - so
>> it will be possible to create and upload docker release images without
>> pain.
>> Corresponding documentations is in preparation.
>>
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-7821
>> [2] https://hub.docker.com/explore
>> [3] https://github.com/apache/ignite/pull/3574
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>>