Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

Dmitriy, thanks!
Fixed that typo.




> On 4 Jun 2018, at 17:09, Dmitriy Setrakyan  wrote:
> 
> Peter, can you please fix the text below to point to "log", not "lib"?
> 
> log directory is at /var/lib/apache-ignite (mapped to
>> /var/lib/apache-ignite/log)
> 
> 
> On Mon, Jun 4, 2018 at 7:07 AM, Petr Ivanov  wrote:
> 
>> Log directory is directly at /var/log/apache-ignite and mapped via symlink
>> to /var/lib/apache-ignite/log because /var/lib/apache-ignite/ (main work
>> dir which in its turn is mapped via symlink to
>> /usr/share/apache—ignite/work) is the place where running node of Apache
>> Ignite will write it’s logs.
>> 
>> 
>> 
>>> On 4 Jun 2018, at 16:56, Dmitriy Setrakyan 
>> wrote:
>>> 
>>> Thanks, Petr!
>>> 
>>> I think the log directory should be at /var/log, not /var/lib, right?
>>> 
>>> D.
>>> 
>>> On Mon, Jun 4, 2018 at 5:04 AM, Petr Ivanov  wrote:
>>> 
 Dmitriy,
 
 
 I’ve added requested information (see [1]).
 Can you check that this information is enough, please?
 
 
 [1] https://issues.apache.org/jira/browse/IGNITE-8671?focusedCom
 mentId=16500123=com.atlassian.jira.plugin.system.
 issuetabpanels:comment-tabpanel#comment-16500123
 
 
 
 
> On 3 Jun 2018, at 10:24, Dmitriy Setrakyan 
 wrote:
> 
> Peter,
> 
> I think what is really missing is the installation structure, i.e.
>> where
 is
> the bin, config, lib, work folders. Is IGNITE_HOME pointing somewhere
>> as
 a
> result of the installation? I think, if you explain it to users, there
 will
> be more understanding from the user stand point.
> 
> Can you please add that?
> 
> D.
> 
> On Sat, Jun 2, 2018 at 12:39 PM, Petr Ivanov 
 wrote:
> 
>> Dmitriy,
>> 
>> 
>> I've added warning snippet in the bottom of the Alternative
>> Installation
>> Options section with reference on how to start Apache Ignite installed
 from
>> RPM or DEB packages as standalone Java application (see [1]).
>> Hope it will be enough.
>> 
>> 
>> [1] https://issues.apache.org/jira/browse/IGNITE-8671?
>> focusedCommentId=16499157=com.atlassian.jira.
>> plugin.system.issuetabpanels:comment-tabpanel#comment-16499157
>> 
>> 
>> 
>> 
>>> On 2 Jun 2018, at 21:57, Dmitriy Setrakyan 
>> wrote:
>>> 
>>> Peter,
>>> 
>>> We cannot have a distribution that works sometimes.
>>> 
>>> I think you should read the ticket carefully. I don't beleive we need
 to
>>> make any changes to the release, it is a matter of fixing the
>>> documentation.
>>> 
>>> Can you confirm this?
>>> 
>>> D.
>>> 
>>> 
>>> On Jun 2, 2018 11:44, "Peter Ivanov"  wrote:
>>> 
>>> Dmitriy,
>>> 
>>> 
>>> You suggest removing fully working under corresponding Linux
 distributive
>>> RPM and DEB packages entirely from apache.org/dist/ignite only
>> because
>> they
>>> do not work in highly unlikely scenario (Windows 10 WSL) as service?
>>> 
>>> I will certainly add reference about running Apache Ignite from the
>>> packages as standalone Java application (with corresponding
>> permissions
>>> note) but I’d like to hear community opinion on the whole matter -
>>> everything that was done, was done with review and approve from lots
>> of
>>> Apache Ignite commiters and PMCs, including PMC chair.
>>> 
>>> 
>>> On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan <
>> dsetrak...@apache.org>
>>> wrote:
>>> 
>>> 
 Peter,
 
 I have reopened this ticket:
 https://issues.apache.org/jira/browse/IGNITE-8671
 
 I changed the priority to blocker. At this point I suggest the
>> following:
 - we either remove the DEB and RPM packages from the website and
 readme
 - or we fix this issue ASAP as stated in the ticket.
 
 I will leave it up to you to decide.
 
 D.
 
 On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov >> 
 wrote:
 
> Dmitriy,
> 
> 
> SystemD supports running multiple instances of one service – this
>> is
>> done
> through @-like syntax: 'sudo systemctl start apache-ignite@
>>  file name>', so that with every unique command string there will be
> started
> / stopped unique instance of Apache Ignite. And all instances can
>> be
> restarted / stopped / enabled on boot / etc. simultaneously through
>> 'sudo
> systemctl  apache-ignite@*'.
> 
> Still, I can add a note about possibility of starting Apache Ignite
> manually through ignite.sh with a reference to corresponding
>>> documentation
> section, information where to look for the root of Apache Ignite
> installation and how to correctly start Apache Ignite 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

Peter, can you please fix the text below to point to "log", not "lib"?

log directory is at /var/lib/apache-ignite (mapped to
> /var/lib/apache-ignite/log)


On Mon, Jun 4, 2018 at 7:07 AM, Petr Ivanov  wrote:

> Log directory is directly at /var/log/apache-ignite and mapped via symlink
> to /var/lib/apache-ignite/log because /var/lib/apache-ignite/ (main work
> dir which in its turn is mapped via symlink to
> /usr/share/apache—ignite/work) is the place where running node of Apache
> Ignite will write it’s logs.
>
>
>
> > On 4 Jun 2018, at 16:56, Dmitriy Setrakyan 
> wrote:
> >
> > Thanks, Petr!
> >
> > I think the log directory should be at /var/log, not /var/lib, right?
> >
> > D.
> >
> > On Mon, Jun 4, 2018 at 5:04 AM, Petr Ivanov  wrote:
> >
> >> Dmitriy,
> >>
> >>
> >> I’ve added requested information (see [1]).
> >> Can you check that this information is enough, please?
> >>
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-8671?focusedCom
> >> mentId=16500123=com.atlassian.jira.plugin.system.
> >> issuetabpanels:comment-tabpanel#comment-16500123
> >>
> >>
> >>
> >>
> >>> On 3 Jun 2018, at 10:24, Dmitriy Setrakyan 
> >> wrote:
> >>>
> >>> Peter,
> >>>
> >>> I think what is really missing is the installation structure, i.e.
> where
> >> is
> >>> the bin, config, lib, work folders. Is IGNITE_HOME pointing somewhere
> as
> >> a
> >>> result of the installation? I think, if you explain it to users, there
> >> will
> >>> be more understanding from the user stand point.
> >>>
> >>> Can you please add that?
> >>>
> >>> D.
> >>>
> >>> On Sat, Jun 2, 2018 at 12:39 PM, Petr Ivanov 
> >> wrote:
> >>>
>  Dmitriy,
> 
> 
>  I've added warning snippet in the bottom of the Alternative
> Installation
>  Options section with reference on how to start Apache Ignite installed
> >> from
>  RPM or DEB packages as standalone Java application (see [1]).
>  Hope it will be enough.
> 
> 
>  [1] https://issues.apache.org/jira/browse/IGNITE-8671?
>  focusedCommentId=16499157=com.atlassian.jira.
>  plugin.system.issuetabpanels:comment-tabpanel#comment-16499157
> 
> 
> 
> 
> > On 2 Jun 2018, at 21:57, Dmitriy Setrakyan 
>  wrote:
> >
> > Peter,
> >
> > We cannot have a distribution that works sometimes.
> >
> > I think you should read the ticket carefully. I don't beleive we need
> >> to
> > make any changes to the release, it is a matter of fixing the
> > documentation.
> >
> > Can you confirm this?
> >
> > D.
> >
> >
> > On Jun 2, 2018 11:44, "Peter Ivanov"  wrote:
> >
> > Dmitriy,
> >
> >
> > You suggest removing fully working under corresponding Linux
> >> distributive
> > RPM and DEB packages entirely from apache.org/dist/ignite only
> because
>  they
> > do not work in highly unlikely scenario (Windows 10 WSL) as service?
> >
> > I will certainly add reference about running Apache Ignite from the
> > packages as standalone Java application (with corresponding
> permissions
> > note) but I’d like to hear community opinion on the whole matter -
> > everything that was done, was done with review and approve from lots
> of
> > Apache Ignite commiters and PMCs, including PMC chair.
> >
> >
> > On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> >
> >> Peter,
> >>
> >> I have reopened this ticket:
> >> https://issues.apache.org/jira/browse/IGNITE-8671
> >>
> >> I changed the priority to blocker. At this point I suggest the
>  following:
> >> - we either remove the DEB and RPM packages from the website and
> >> readme
> >> - or we fix this issue ASAP as stated in the ticket.
> >>
> >> I will leave it up to you to decide.
> >>
> >> D.
> >>
> >> On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov  >
> >> wrote:
> >>
> >>> Dmitriy,
> >>>
> >>>
> >>> SystemD supports running multiple instances of one service – this
> is
>  done
> >>> through @-like syntax: 'sudo systemctl start apache-ignite@
>   >>> file name>', so that with every unique command string there will be
> >>> started
> >>> / stopped unique instance of Apache Ignite. And all instances can
> be
> >>> restarted / stopped / enabled on boot / etc. simultaneously through
>  'sudo
> >>> systemctl  apache-ignite@*'.
> >>>
> >>> Still, I can add a note about possibility of starting Apache Ignite
> >>> manually through ignite.sh with a reference to corresponding
> > documentation
> >>> section, information where to look for the root of Apache Ignite
> >>> installation and how to correctly start Apache Ignite in terms of
> >>> permissions.
> >>>
> >>> File the documentation updates ticket?
> >>>
> >>>
> >>> On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan <
> >> 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

Log directory is directly at /var/log/apache-ignite and mapped via symlink to 
/var/lib/apache-ignite/log because /var/lib/apache-ignite/ (main work dir which 
in its turn is mapped via symlink to /usr/share/apache—ignite/work) is the 
place where running node of Apache Ignite will write it’s logs.



> On 4 Jun 2018, at 16:56, Dmitriy Setrakyan  wrote:
> 
> Thanks, Petr!
> 
> I think the log directory should be at /var/log, not /var/lib, right?
> 
> D.
> 
> On Mon, Jun 4, 2018 at 5:04 AM, Petr Ivanov  wrote:
> 
>> Dmitriy,
>> 
>> 
>> I’ve added requested information (see [1]).
>> Can you check that this information is enough, please?
>> 
>> 
>> [1] https://issues.apache.org/jira/browse/IGNITE-8671?focusedCom
>> mentId=16500123=com.atlassian.jira.plugin.system.
>> issuetabpanels:comment-tabpanel#comment-16500123
>> 
>> 
>> 
>> 
>>> On 3 Jun 2018, at 10:24, Dmitriy Setrakyan 
>> wrote:
>>> 
>>> Peter,
>>> 
>>> I think what is really missing is the installation structure, i.e. where
>> is
>>> the bin, config, lib, work folders. Is IGNITE_HOME pointing somewhere as
>> a
>>> result of the installation? I think, if you explain it to users, there
>> will
>>> be more understanding from the user stand point.
>>> 
>>> Can you please add that?
>>> 
>>> D.
>>> 
>>> On Sat, Jun 2, 2018 at 12:39 PM, Petr Ivanov 
>> wrote:
>>> 
 Dmitriy,
 
 
 I've added warning snippet in the bottom of the Alternative Installation
 Options section with reference on how to start Apache Ignite installed
>> from
 RPM or DEB packages as standalone Java application (see [1]).
 Hope it will be enough.
 
 
 [1] https://issues.apache.org/jira/browse/IGNITE-8671?
 focusedCommentId=16499157=com.atlassian.jira.
 plugin.system.issuetabpanels:comment-tabpanel#comment-16499157
 
 
 
 
> On 2 Jun 2018, at 21:57, Dmitriy Setrakyan 
 wrote:
> 
> Peter,
> 
> We cannot have a distribution that works sometimes.
> 
> I think you should read the ticket carefully. I don't beleive we need
>> to
> make any changes to the release, it is a matter of fixing the
> documentation.
> 
> Can you confirm this?
> 
> D.
> 
> 
> On Jun 2, 2018 11:44, "Peter Ivanov"  wrote:
> 
> Dmitriy,
> 
> 
> You suggest removing fully working under corresponding Linux
>> distributive
> RPM and DEB packages entirely from apache.org/dist/ignite only because
 they
> do not work in highly unlikely scenario (Windows 10 WSL) as service?
> 
> I will certainly add reference about running Apache Ignite from the
> packages as standalone Java application (with corresponding permissions
> note) but I’d like to hear community opinion on the whole matter -
> everything that was done, was done with review and approve from lots of
> Apache Ignite commiters and PMCs, including PMC chair.
> 
> 
> On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan 
> wrote:
> 
> 
>> Peter,
>> 
>> I have reopened this ticket:
>> https://issues.apache.org/jira/browse/IGNITE-8671
>> 
>> I changed the priority to blocker. At this point I suggest the
 following:
>> - we either remove the DEB and RPM packages from the website and
>> readme
>> - or we fix this issue ASAP as stated in the ticket.
>> 
>> I will leave it up to you to decide.
>> 
>> D.
>> 
>> On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov 
>> wrote:
>> 
>>> Dmitriy,
>>> 
>>> 
>>> SystemD supports running multiple instances of one service – this is
 done
>>> through @-like syntax: 'sudo systemctl start apache-ignite@
 >> file name>', so that with every unique command string there will be
>>> started
>>> / stopped unique instance of Apache Ignite. And all instances can be
>>> restarted / stopped / enabled on boot / etc. simultaneously through
 'sudo
>>> systemctl  apache-ignite@*'.
>>> 
>>> Still, I can add a note about possibility of starting Apache Ignite
>>> manually through ignite.sh with a reference to corresponding
> documentation
>>> section, information where to look for the root of Apache Ignite
>>> installation and how to correctly start Apache Ignite in terms of
>>> permissions.
>>> 
>>> File the documentation updates ticket?
>>> 
>>> 
>>> On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan <
>> dsetrak...@apache.org>
>>> wrote:
>>> 
 Petr,
 
 Most of the users will download and install Ignite so they can
>> develop
>>> with
 it. This means that they will be starting more than one node, which
>> is
 impossible if Ignite is a service. We should provide instructions to
 do
 both.
 
 D.
 
 On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov 
>>> wrote:
 
> Dmitriy,
> 
> 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

Thanks, Petr!

I think the log directory should be at /var/log, not /var/lib, right?

D.

On Mon, Jun 4, 2018 at 5:04 AM, Petr Ivanov  wrote:

> Dmitriy,
>
>
> I’ve added requested information (see [1]).
> Can you check that this information is enough, please?
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8671?focusedCom
> mentId=16500123=com.atlassian.jira.plugin.system.
> issuetabpanels:comment-tabpanel#comment-16500123
>
>
>
>
> > On 3 Jun 2018, at 10:24, Dmitriy Setrakyan 
> wrote:
> >
> > Peter,
> >
> > I think what is really missing is the installation structure, i.e. where
> is
> > the bin, config, lib, work folders. Is IGNITE_HOME pointing somewhere as
> a
> > result of the installation? I think, if you explain it to users, there
> will
> > be more understanding from the user stand point.
> >
> > Can you please add that?
> >
> > D.
> >
> > On Sat, Jun 2, 2018 at 12:39 PM, Petr Ivanov 
> wrote:
> >
> >> Dmitriy,
> >>
> >>
> >> I've added warning snippet in the bottom of the Alternative Installation
> >> Options section with reference on how to start Apache Ignite installed
> from
> >> RPM or DEB packages as standalone Java application (see [1]).
> >> Hope it will be enough.
> >>
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-8671?
> >> focusedCommentId=16499157=com.atlassian.jira.
> >> plugin.system.issuetabpanels:comment-tabpanel#comment-16499157
> >>
> >>
> >>
> >>
> >>> On 2 Jun 2018, at 21:57, Dmitriy Setrakyan 
> >> wrote:
> >>>
> >>> Peter,
> >>>
> >>> We cannot have a distribution that works sometimes.
> >>>
> >>> I think you should read the ticket carefully. I don't beleive we need
> to
> >>> make any changes to the release, it is a matter of fixing the
> >>> documentation.
> >>>
> >>> Can you confirm this?
> >>>
> >>> D.
> >>>
> >>>
> >>> On Jun 2, 2018 11:44, "Peter Ivanov"  wrote:
> >>>
> >>> Dmitriy,
> >>>
> >>>
> >>> You suggest removing fully working under corresponding Linux
> distributive
> >>> RPM and DEB packages entirely from apache.org/dist/ignite only because
> >> they
> >>> do not work in highly unlikely scenario (Windows 10 WSL) as service?
> >>>
> >>> I will certainly add reference about running Apache Ignite from the
> >>> packages as standalone Java application (with corresponding permissions
> >>> note) but I’d like to hear community opinion on the whole matter -
> >>> everything that was done, was done with review and approve from lots of
> >>> Apache Ignite commiters and PMCs, including PMC chair.
> >>>
> >>>
> >>> On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan 
> >>> wrote:
> >>>
> >>>
>  Peter,
> 
>  I have reopened this ticket:
>  https://issues.apache.org/jira/browse/IGNITE-8671
> 
>  I changed the priority to blocker. At this point I suggest the
> >> following:
>  - we either remove the DEB and RPM packages from the website and
> readme
>  - or we fix this issue ASAP as stated in the ticket.
> 
>  I will leave it up to you to decide.
> 
>  D.
> 
>  On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov 
>  wrote:
> 
> > Dmitriy,
> >
> >
> > SystemD supports running multiple instances of one service – this is
> >> done
> > through @-like syntax: 'sudo systemctl start apache-ignite@
> >>  > file name>', so that with every unique command string there will be
> > started
> > / stopped unique instance of Apache Ignite. And all instances can be
> > restarted / stopped / enabled on boot / etc. simultaneously through
> >> 'sudo
> > systemctl  apache-ignite@*'.
> >
> > Still, I can add a note about possibility of starting Apache Ignite
> > manually through ignite.sh with a reference to corresponding
> >>> documentation
> > section, information where to look for the root of Apache Ignite
> > installation and how to correctly start Apache Ignite in terms of
> > permissions.
> >
> > File the documentation updates ticket?
> >
> >
> > On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> >> Petr,
> >>
> >> Most of the users will download and install Ignite so they can
> develop
> > with
> >> it. This means that they will be starting more than one node, which
> is
> >> impossible if Ignite is a service. We should provide instructions to
> >> do
> >> both.
> >>
> >> D.
> >>
> >> On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov 
> > wrote:
> >>
> >>> Dmitriy,
> >>>
> >>>
> >>> Current packages design (both RPM and DEB) was reviewed and
> approved
> > by
> >>> community. I do not quite remember why service-based startup was
> > chosen
> >> but
> >>> it seems rather logical and Unix-compliant – under Linux almost
> every
> >>> service software is packed this way, which gives some benefits like
> >> service
> >>> autostart on reboot, centralized running nodes management (through
> 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

Dmitriy,


I’ve added requested information (see [1]).
Can you check that this information is enough, please?


[1] 
https://issues.apache.org/jira/browse/IGNITE-8671?focusedCommentId=16500123=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16500123




> On 3 Jun 2018, at 10:24, Dmitriy Setrakyan  wrote:
> 
> Peter,
> 
> I think what is really missing is the installation structure, i.e. where is
> the bin, config, lib, work folders. Is IGNITE_HOME pointing somewhere as a
> result of the installation? I think, if you explain it to users, there will
> be more understanding from the user stand point.
> 
> Can you please add that?
> 
> D.
> 
> On Sat, Jun 2, 2018 at 12:39 PM, Petr Ivanov  wrote:
> 
>> Dmitriy,
>> 
>> 
>> I've added warning snippet in the bottom of the Alternative Installation
>> Options section with reference on how to start Apache Ignite installed from
>> RPM or DEB packages as standalone Java application (see [1]).
>> Hope it will be enough.
>> 
>> 
>> [1] https://issues.apache.org/jira/browse/IGNITE-8671?
>> focusedCommentId=16499157=com.atlassian.jira.
>> plugin.system.issuetabpanels:comment-tabpanel#comment-16499157
>> 
>> 
>> 
>> 
>>> On 2 Jun 2018, at 21:57, Dmitriy Setrakyan 
>> wrote:
>>> 
>>> Peter,
>>> 
>>> We cannot have a distribution that works sometimes.
>>> 
>>> I think you should read the ticket carefully. I don't beleive we need to
>>> make any changes to the release, it is a matter of fixing the
>>> documentation.
>>> 
>>> Can you confirm this?
>>> 
>>> D.
>>> 
>>> 
>>> On Jun 2, 2018 11:44, "Peter Ivanov"  wrote:
>>> 
>>> Dmitriy,
>>> 
>>> 
>>> You suggest removing fully working under corresponding Linux distributive
>>> RPM and DEB packages entirely from apache.org/dist/ignite only because
>> they
>>> do not work in highly unlikely scenario (Windows 10 WSL) as service?
>>> 
>>> I will certainly add reference about running Apache Ignite from the
>>> packages as standalone Java application (with corresponding permissions
>>> note) but I’d like to hear community opinion on the whole matter -
>>> everything that was done, was done with review and approve from lots of
>>> Apache Ignite commiters and PMCs, including PMC chair.
>>> 
>>> 
>>> On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan 
>>> wrote:
>>> 
>>> 
 Peter,
 
 I have reopened this ticket:
 https://issues.apache.org/jira/browse/IGNITE-8671
 
 I changed the priority to blocker. At this point I suggest the
>> following:
 - we either remove the DEB and RPM packages from the website and readme
 - or we fix this issue ASAP as stated in the ticket.
 
 I will leave it up to you to decide.
 
 D.
 
 On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov 
 wrote:
 
> Dmitriy,
> 
> 
> SystemD supports running multiple instances of one service – this is
>> done
> through @-like syntax: 'sudo systemctl start apache-ignite@
>>  file name>', so that with every unique command string there will be
> started
> / stopped unique instance of Apache Ignite. And all instances can be
> restarted / stopped / enabled on boot / etc. simultaneously through
>> 'sudo
> systemctl  apache-ignite@*'.
> 
> Still, I can add a note about possibility of starting Apache Ignite
> manually through ignite.sh with a reference to corresponding
>>> documentation
> section, information where to look for the root of Apache Ignite
> installation and how to correctly start Apache Ignite in terms of
> permissions.
> 
> File the documentation updates ticket?
> 
> 
> On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan 
> wrote:
> 
>> Petr,
>> 
>> Most of the users will download and install Ignite so they can develop
> with
>> it. This means that they will be starting more than one node, which is
>> impossible if Ignite is a service. We should provide instructions to
>> do
>> both.
>> 
>> D.
>> 
>> On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov 
> wrote:
>> 
>>> Dmitriy,
>>> 
>>> 
>>> Current packages design (both RPM and DEB) was reviewed and approved
> by
>>> community. I do not quite remember why service-based startup was
> chosen
>> but
>>> it seems rather logical and Unix-compliant – under Linux almost every
>>> service software is packed this way, which gives some benefits like
>> service
>>> autostart on reboot, centralized running nodes management (through
>>> systemctl), etc. There is no point in packing binary into Linux
> packages
>> if
>>> it then will be used as standalone executable.
>>> Yet, current design does not limit advanced user from running Apache
>> Ignite
>>> as standalone process – executing
> /usr/share/apache-ignite/bin/ignite.sh
>>> with parameters will start Apache Ignite node as if it was delivered
> by
>>> binary archive.
>>> 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

Peter,

I think what is really missing is the installation structure, i.e. where is
the bin, config, lib, work folders. Is IGNITE_HOME pointing somewhere as a
result of the installation? I think, if you explain it to users, there will
be more understanding from the user stand point.

Can you please add that?

D.

On Sat, Jun 2, 2018 at 12:39 PM, Petr Ivanov  wrote:

> Dmitriy,
>
>
> I've added warning snippet in the bottom of the Alternative Installation
> Options section with reference on how to start Apache Ignite installed from
> RPM or DEB packages as standalone Java application (see [1]).
> Hope it will be enough.
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8671?
> focusedCommentId=16499157=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-16499157
>
>
>
>
> > On 2 Jun 2018, at 21:57, Dmitriy Setrakyan 
> wrote:
> >
> > Peter,
> >
> > We cannot have a distribution that works sometimes.
> >
> > I think you should read the ticket carefully. I don't beleive we need to
> > make any changes to the release, it is a matter of fixing the
> > documentation.
> >
> > Can you confirm this?
> >
> > D.
> >
> >
> > On Jun 2, 2018 11:44, "Peter Ivanov"  wrote:
> >
> > Dmitriy,
> >
> >
> > You suggest removing fully working under corresponding Linux distributive
> > RPM and DEB packages entirely from apache.org/dist/ignite only because
> they
> > do not work in highly unlikely scenario (Windows 10 WSL) as service?
> >
> > I will certainly add reference about running Apache Ignite from the
> > packages as standalone Java application (with corresponding permissions
> > note) but I’d like to hear community opinion on the whole matter -
> > everything that was done, was done with review and approve from lots of
> > Apache Ignite commiters and PMCs, including PMC chair.
> >
> >
> > On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan 
> > wrote:
> >
> >
> >> Peter,
> >>
> >> I have reopened this ticket:
> >> https://issues.apache.org/jira/browse/IGNITE-8671
> >>
> >> I changed the priority to blocker. At this point I suggest the
> following:
> >> - we either remove the DEB and RPM packages from the website and readme
> >> - or we fix this issue ASAP as stated in the ticket.
> >>
> >> I will leave it up to you to decide.
> >>
> >> D.
> >>
> >> On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov 
> >> wrote:
> >>
> >>> Dmitriy,
> >>>
> >>>
> >>> SystemD supports running multiple instances of one service – this is
> done
> >>> through @-like syntax: 'sudo systemctl start apache-ignite@
>  >>> file name>', so that with every unique command string there will be
> >>> started
> >>> / stopped unique instance of Apache Ignite. And all instances can be
> >>> restarted / stopped / enabled on boot / etc. simultaneously through
> 'sudo
> >>> systemctl  apache-ignite@*'.
> >>>
> >>> Still, I can add a note about possibility of starting Apache Ignite
> >>> manually through ignite.sh with a reference to corresponding
> > documentation
> >>> section, information where to look for the root of Apache Ignite
> >>> installation and how to correctly start Apache Ignite in terms of
> >>> permissions.
> >>>
> >>> File the documentation updates ticket?
> >>>
> >>>
> >>> On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan 
> >>> wrote:
> >>>
>  Petr,
> 
>  Most of the users will download and install Ignite so they can develop
> >>> with
>  it. This means that they will be starting more than one node, which is
>  impossible if Ignite is a service. We should provide instructions to
> do
>  both.
> 
>  D.
> 
>  On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov 
> >>> wrote:
> 
> > Dmitriy,
> >
> >
> > Current packages design (both RPM and DEB) was reviewed and approved
> >>> by
> > community. I do not quite remember why service-based startup was
> >>> chosen
>  but
> > it seems rather logical and Unix-compliant – under Linux almost every
> > service software is packed this way, which gives some benefits like
>  service
> > autostart on reboot, centralized running nodes management (through
> > systemctl), etc. There is no point in packing binary into Linux
> >>> packages
>  if
> > it then will be used as standalone executable.
> > Yet, current design does not limit advanced user from running Apache
>  Ignite
> > as standalone process – executing
> >>> /usr/share/apache-ignite/bin/ignite.sh
> > with parameters will start Apache Ignite node as if it was delivered
> >>> by
> > binary archive.
> >
> >
> >
> > On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan <
> >>> dsetrak...@apache.org>
> > wrote:
> >
> >> Petr,
> >>
> >> Why do we even suggest starting Ignite as a service? Why not just
> >>> start
> >> Ignite instance as a stand-alone process? This should work, no?
> >>
> >> D.
> >>
> >> On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov 
> > wrote:
> >>
> >>> 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Ilya Kasnacheev]

Hello again!

Oops, sorry, what I was meaning to say that I was siding with Petr.

We can surely add a disclaimer to downloads page, but it will be across the
lines of "caution, may contain water which is wet"

Regards.

-- 
Ilya Kasnacheev

2018-06-02 23:10 GMT+03:00 Ilya Kasnacheev :

> Hello!
>
> I have to side with Dmitriy here. If you install a Debian package for
> server software, you would expect that a daemon of that software to be ran
> with default configuration using sysctl-flavour services.
>
> You can certainly also run the installed software in all kinds of other
> ways manually, but as a user of Debian package I won't expect this to be a
> primary mode of operation. For a long time user of Linux, packaged daemon
> that can't be brought up as a service is a broken package.
>
> Ditto for RPM, through they have less agressive autostart habits (you will
> usually need to enable service first with sysctl).
>
> Moreover you don't expect to have to tinker with software installed as
> package, DEB/RPM is not like IKEA in this regard.
>
> Disclaimer: I have reviewed multiple iterations of RPM/DEB packaging of
> Apache Ignite.
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-06-02 22:39 GMT+03:00 Petr Ivanov :
>
>> Dmitriy,
>>
>>
>> I've added warning snippet in the bottom of the Alternative Installation
>> Options section with reference on how to start Apache Ignite installed from
>> RPM or DEB packages as standalone Java application (see [1]).
>> Hope it will be enough.
>>
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-8671?focusedCom
>> mentId=16499157=com.atlassian.jira.plugin.system.
>> issuetabpanels:comment-tabpanel#comment-16499157
>>
>>
>>
>>
>> > On 2 Jun 2018, at 21:57, Dmitriy Setrakyan 
>> wrote:
>> >
>> > Peter,
>> >
>> > We cannot have a distribution that works sometimes.
>> >
>> > I think you should read the ticket carefully. I don't beleive we need to
>> > make any changes to the release, it is a matter of fixing the
>> > documentation.
>> >
>> > Can you confirm this?
>> >
>> > D.
>> >
>> >
>> > On Jun 2, 2018 11:44, "Peter Ivanov"  wrote:
>> >
>> > Dmitriy,
>> >
>> >
>> > You suggest removing fully working under corresponding Linux
>> distributive
>> > RPM and DEB packages entirely from apache.org/dist/ignite only because
>> they
>> > do not work in highly unlikely scenario (Windows 10 WSL) as service?
>> >
>> > I will certainly add reference about running Apache Ignite from the
>> > packages as standalone Java application (with corresponding permissions
>> > note) but I’d like to hear community opinion on the whole matter -
>> > everything that was done, was done with review and approve from lots of
>> > Apache Ignite commiters and PMCs, including PMC chair.
>> >
>> >
>> > On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan 
>> > wrote:
>> >
>> >
>> >> Peter,
>> >>
>> >> I have reopened this ticket:
>> >> https://issues.apache.org/jira/browse/IGNITE-8671
>> >>
>> >> I changed the priority to blocker. At this point I suggest the
>> following:
>> >> - we either remove the DEB and RPM packages from the website and readme
>> >> - or we fix this issue ASAP as stated in the ticket.
>> >>
>> >> I will leave it up to you to decide.
>> >>
>> >> D.
>> >>
>> >> On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov 
>> >> wrote:
>> >>
>> >>> Dmitriy,
>> >>>
>> >>>
>> >>> SystemD supports running multiple instances of one service – this is
>> done
>> >>> through @-like syntax: 'sudo systemctl start apache-ignite@
>> > >>> file name>', so that with every unique command string there will be
>> >>> started
>> >>> / stopped unique instance of Apache Ignite. And all instances can be
>> >>> restarted / stopped / enabled on boot / etc. simultaneously through
>> 'sudo
>> >>> systemctl  apache-ignite@*'.
>> >>>
>> >>> Still, I can add a note about possibility of starting Apache Ignite
>> >>> manually through ignite.sh with a reference to corresponding
>> > documentation
>> >>> section, information where to look for the root of Apache Ignite
>> >>> installation and how to correctly start Apache Ignite in terms of
>> >>> permissions.
>> >>>
>> >>> File the documentation updates ticket?
>> >>>
>> >>>
>> >>> On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan > >
>> >>> wrote:
>> >>>
>>  Petr,
>> 
>>  Most of the users will download and install Ignite so they can
>> develop
>> >>> with
>>  it. This means that they will be starting more than one node, which
>> is
>>  impossible if Ignite is a service. We should provide instructions to
>> do
>>  both.
>> 
>>  D.
>> 
>>  On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov 
>> >>> wrote:
>> 
>> > Dmitriy,
>> >
>> >
>> > Current packages design (both RPM and DEB) was reviewed and approved
>> >>> by
>> > community. I do not quite remember why service-based startup was
>> >>> chosen
>>  but
>> > it seems rather logical and Unix-compliant – under Linux almost
>> every
>> > service software is packed this 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Ilya Kasnacheev]

Hello!

I have to side with Dmitriy here. If you install a Debian package for
server software, you would expect that a daemon of that software to be ran
with default configuration using sysctl-flavour services.

You can certainly also run the installed software in all kinds of other
ways manually, but as a user of Debian package I won't expect this to be a
primary mode of operation. For a long time user of Linux, packaged daemon
that can't be brought up as a service is a broken package.

Ditto for RPM, through they have less agressive autostart habits (you will
usually need to enable service first with sysctl).

Moreover you don't expect to have to tinker with software installed as
package, DEB/RPM is not like IKEA in this regard.

Disclaimer: I have reviewed multiple iterations of RPM/DEB packaging of
Apache Ignite.

Regards,

-- 
Ilya Kasnacheev

2018-06-02 22:39 GMT+03:00 Petr Ivanov :

> Dmitriy,
>
>
> I've added warning snippet in the bottom of the Alternative Installation
> Options section with reference on how to start Apache Ignite installed from
> RPM or DEB packages as standalone Java application (see [1]).
> Hope it will be enough.
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8671?
> focusedCommentId=16499157=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-16499157
>
>
>
>
> > On 2 Jun 2018, at 21:57, Dmitriy Setrakyan 
> wrote:
> >
> > Peter,
> >
> > We cannot have a distribution that works sometimes.
> >
> > I think you should read the ticket carefully. I don't beleive we need to
> > make any changes to the release, it is a matter of fixing the
> > documentation.
> >
> > Can you confirm this?
> >
> > D.
> >
> >
> > On Jun 2, 2018 11:44, "Peter Ivanov"  wrote:
> >
> > Dmitriy,
> >
> >
> > You suggest removing fully working under corresponding Linux distributive
> > RPM and DEB packages entirely from apache.org/dist/ignite only because
> they
> > do not work in highly unlikely scenario (Windows 10 WSL) as service?
> >
> > I will certainly add reference about running Apache Ignite from the
> > packages as standalone Java application (with corresponding permissions
> > note) but I’d like to hear community opinion on the whole matter -
> > everything that was done, was done with review and approve from lots of
> > Apache Ignite commiters and PMCs, including PMC chair.
> >
> >
> > On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan 
> > wrote:
> >
> >
> >> Peter,
> >>
> >> I have reopened this ticket:
> >> https://issues.apache.org/jira/browse/IGNITE-8671
> >>
> >> I changed the priority to blocker. At this point I suggest the
> following:
> >> - we either remove the DEB and RPM packages from the website and readme
> >> - or we fix this issue ASAP as stated in the ticket.
> >>
> >> I will leave it up to you to decide.
> >>
> >> D.
> >>
> >> On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov 
> >> wrote:
> >>
> >>> Dmitriy,
> >>>
> >>>
> >>> SystemD supports running multiple instances of one service – this is
> done
> >>> through @-like syntax: 'sudo systemctl start apache-ignite@
>  >>> file name>', so that with every unique command string there will be
> >>> started
> >>> / stopped unique instance of Apache Ignite. And all instances can be
> >>> restarted / stopped / enabled on boot / etc. simultaneously through
> 'sudo
> >>> systemctl  apache-ignite@*'.
> >>>
> >>> Still, I can add a note about possibility of starting Apache Ignite
> >>> manually through ignite.sh with a reference to corresponding
> > documentation
> >>> section, information where to look for the root of Apache Ignite
> >>> installation and how to correctly start Apache Ignite in terms of
> >>> permissions.
> >>>
> >>> File the documentation updates ticket?
> >>>
> >>>
> >>> On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan 
> >>> wrote:
> >>>
>  Petr,
> 
>  Most of the users will download and install Ignite so they can develop
> >>> with
>  it. This means that they will be starting more than one node, which is
>  impossible if Ignite is a service. We should provide instructions to
> do
>  both.
> 
>  D.
> 
>  On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov 
> >>> wrote:
> 
> > Dmitriy,
> >
> >
> > Current packages design (both RPM and DEB) was reviewed and approved
> >>> by
> > community. I do not quite remember why service-based startup was
> >>> chosen
>  but
> > it seems rather logical and Unix-compliant – under Linux almost every
> > service software is packed this way, which gives some benefits like
>  service
> > autostart on reboot, centralized running nodes management (through
> > systemctl), etc. There is no point in packing binary into Linux
> >>> packages
>  if
> > it then will be used as standalone executable.
> > Yet, current design does not limit advanced user from running Apache
>  Ignite
> > as standalone process – executing
> >>> /usr/share/apache-ignite/bin/ignite.sh
> > with 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

Dmitriy,


I've added warning snippet in the bottom of the Alternative Installation 
Options section with reference on how to start Apache Ignite installed from RPM 
or DEB packages as standalone Java application (see [1]).
Hope it will be enough.


[1] 
https://issues.apache.org/jira/browse/IGNITE-8671?focusedCommentId=16499157=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16499157




> On 2 Jun 2018, at 21:57, Dmitriy Setrakyan  wrote:
> 
> Peter,
> 
> We cannot have a distribution that works sometimes.
> 
> I think you should read the ticket carefully. I don't beleive we need to
> make any changes to the release, it is a matter of fixing the
> documentation.
> 
> Can you confirm this?
> 
> D.
> 
> 
> On Jun 2, 2018 11:44, "Peter Ivanov"  wrote:
> 
> Dmitriy,
> 
> 
> You suggest removing fully working under corresponding Linux distributive
> RPM and DEB packages entirely from apache.org/dist/ignite only because they
> do not work in highly unlikely scenario (Windows 10 WSL) as service?
> 
> I will certainly add reference about running Apache Ignite from the
> packages as standalone Java application (with corresponding permissions
> note) but I’d like to hear community opinion on the whole matter -
> everything that was done, was done with review and approve from lots of
> Apache Ignite commiters and PMCs, including PMC chair.
> 
> 
> On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan 
> wrote:
> 
> 
>> Peter,
>> 
>> I have reopened this ticket:
>> https://issues.apache.org/jira/browse/IGNITE-8671
>> 
>> I changed the priority to blocker. At this point I suggest the following:
>> - we either remove the DEB and RPM packages from the website and readme
>> - or we fix this issue ASAP as stated in the ticket.
>> 
>> I will leave it up to you to decide.
>> 
>> D.
>> 
>> On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov 
>> wrote:
>> 
>>> Dmitriy,
>>> 
>>> 
>>> SystemD supports running multiple instances of one service – this is done
>>> through @-like syntax: 'sudo systemctl start apache-ignite@>> file name>', so that with every unique command string there will be
>>> started
>>> / stopped unique instance of Apache Ignite. And all instances can be
>>> restarted / stopped / enabled on boot / etc. simultaneously through 'sudo
>>> systemctl  apache-ignite@*'.
>>> 
>>> Still, I can add a note about possibility of starting Apache Ignite
>>> manually through ignite.sh with a reference to corresponding
> documentation
>>> section, information where to look for the root of Apache Ignite
>>> installation and how to correctly start Apache Ignite in terms of
>>> permissions.
>>> 
>>> File the documentation updates ticket?
>>> 
>>> 
>>> On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan 
>>> wrote:
>>> 
 Petr,
 
 Most of the users will download and install Ignite so they can develop
>>> with
 it. This means that they will be starting more than one node, which is
 impossible if Ignite is a service. We should provide instructions to do
 both.
 
 D.
 
 On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov 
>>> wrote:
 
> Dmitriy,
> 
> 
> Current packages design (both RPM and DEB) was reviewed and approved
>>> by
> community. I do not quite remember why service-based startup was
>>> chosen
 but
> it seems rather logical and Unix-compliant – under Linux almost every
> service software is packed this way, which gives some benefits like
 service
> autostart on reboot, centralized running nodes management (through
> systemctl), etc. There is no point in packing binary into Linux
>>> packages
 if
> it then will be used as standalone executable.
> Yet, current design does not limit advanced user from running Apache
 Ignite
> as standalone process – executing
>>> /usr/share/apache-ignite/bin/ignite.sh
> with parameters will start Apache Ignite node as if it was delivered
>>> by
> binary archive.
> 
> 
> 
> On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan <
>>> dsetrak...@apache.org>
> wrote:
> 
>> Petr,
>> 
>> Why do we even suggest starting Ignite as a service? Why not just
>>> start
>> Ignite instance as a stand-alone process? This should work, no?
>> 
>> D.
>> 
>> On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov 
> wrote:
>> 
>>> Unfortunately, it seems to be impossible (at least for now) —
> [1].
>>> So we can say that current package design is for native Linux
>> installation
>>> only.
>>> 
>>> 
>>> https://issues.apache.org/jira/browse/IGNITE-8671?
>>> focusedCommentId=16496813=com.atlassian.jira.
>>> plugin.system.issuetabpanels:comment-tabpanel#comment-16496813
>>> 
>>> 
 On 31 May 2018, at 18:22, Petr Ivanov 
>>> wrote:
 
 Filed https://issues.apache.org/jira/browse/IGNITE-8671 <
>>> https://issues.apache.org/jira/browse/IGNITE-8671>
 
 
 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

Peter,

We cannot have a distribution that works sometimes.

I think you should read the ticket carefully. I don't beleive we need to
make any changes to the release, it is a matter of fixing the
documentation.

Can you confirm this?

D.


On Jun 2, 2018 11:44, "Peter Ivanov"  wrote:

Dmitriy,


You suggest removing fully working under corresponding Linux distributive
RPM and DEB packages entirely from apache.org/dist/ignite only because they
do not work in highly unlikely scenario (Windows 10 WSL) as service?

I will certainly add reference about running Apache Ignite from the
packages as standalone Java application (with corresponding permissions
note) but I’d like to hear community opinion on the whole matter -
everything that was done, was done with review and approve from lots of
Apache Ignite commiters and PMCs, including PMC chair.


On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan 
wrote:


> Peter,
>
> I have reopened this ticket:
> https://issues.apache.org/jira/browse/IGNITE-8671
>
> I changed the priority to blocker. At this point I suggest the following:
> - we either remove the DEB and RPM packages from the website and readme
> - or we fix this issue ASAP as stated in the ticket.
>
> I will leave it up to you to decide.
>
> D.
>
> On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov 
> wrote:
>
>> Dmitriy,
>>
>>
>> SystemD supports running multiple instances of one service – this is done
>> through @-like syntax: 'sudo systemctl start apache-ignite@> file name>', so that with every unique command string there will be
>> started
>> / stopped unique instance of Apache Ignite. And all instances can be
>> restarted / stopped / enabled on boot / etc. simultaneously through 'sudo
>> systemctl  apache-ignite@*'.
>>
>> Still, I can add a note about possibility of starting Apache Ignite
>> manually through ignite.sh with a reference to corresponding
documentation
>> section, information where to look for the root of Apache Ignite
>> installation and how to correctly start Apache Ignite in terms of
>> permissions.
>>
>> File the documentation updates ticket?
>>
>>
>> On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan 
>> wrote:
>>
>> > Petr,
>> >
>> > Most of the users will download and install Ignite so they can develop
>> with
>> > it. This means that they will be starting more than one node, which is
>> > impossible if Ignite is a service. We should provide instructions to do
>> > both.
>> >
>> > D.
>> >
>> > On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov 
>> wrote:
>> >
>> > > Dmitriy,
>> > >
>> > >
>> > > Current packages design (both RPM and DEB) was reviewed and approved
>> by
>> > > community. I do not quite remember why service-based startup was
>> chosen
>> > but
>> > > it seems rather logical and Unix-compliant – under Linux almost every
>> > > service software is packed this way, which gives some benefits like
>> > service
>> > > autostart on reboot, centralized running nodes management (through
>> > > systemctl), etc. There is no point in packing binary into Linux
>> packages
>> > if
>> > > it then will be used as standalone executable.
>> > > Yet, current design does not limit advanced user from running Apache
>> > Ignite
>> > > as standalone process – executing
>> /usr/share/apache-ignite/bin/ignite.sh
>> > > with parameters will start Apache Ignite node as if it was delivered
>> by
>> > > binary archive.
>> > >
>> > >
>> > >
>> > > On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan <
>> dsetrak...@apache.org>
>> > > wrote:
>> > >
>> > > > Petr,
>> > > >
>> > > > Why do we even suggest starting Ignite as a service? Why not just
>> start
>> > > > Ignite instance as a stand-alone process? This should work, no?
>> > > >
>> > > > D.
>> > > >
>> > > > On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov 
>> > > wrote:
>> > > >
>> > > > > Unfortunately, it seems to be impossible (at least for now) —
[1].
>> > > > > So we can say that current package design is for native Linux
>> > > > installation
>> > > > > only.
>> > > > >
>> > > > >
>> > > > > https://issues.apache.org/jira/browse/IGNITE-8671?
>> > > > > focusedCommentId=16496813=com.atlassian.jira.
>> > > > > plugin.system.issuetabpanels:comment-tabpanel#comment-16496813
>> > > > >
>> > > > >
>> > > > > > On 31 May 2018, at 18:22, Petr Ivanov 
>> wrote:
>> > > > > >
>> > > > > > Filed https://issues.apache.org/jira/browse/IGNITE-8671 <
>> > > > > https://issues.apache.org/jira/browse/IGNITE-8671>
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >> On 31 May 2018, at 17:56, Dmitriy Setrakyan <
>> > dsetrak...@apache.org
>> > > > > > wrote:
>> > > > > >>
>> > > > > >> On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov <
>> mr.wei...@gmail.com
>> > > > > > wrote:
>> > > > > >>
>> > > > > >>> I’ll start the investigation.
>> > > > > >>>
>> > > > > >>
>> > > > > >> Can you please file a ticket so we can track it?
>> > > > > >
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Peter Ivanov]

Dmitriy,


You suggest removing fully working under corresponding Linux distributive
RPM and DEB packages entirely from apache.org/dist/ignite only because they
do not work in highly unlikely scenario (Windows 10 WSL) as service?

I will certainly add reference about running Apache Ignite from the
packages as standalone Java application (with corresponding permissions
note) but I’d like to hear community opinion on the whole matter -
everything that was done, was done with review and approve from lots of
Apache Ignite commiters and PMCs, including PMC chair.


On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan 
wrote:

> Peter,
>
> I have reopened this ticket:
> https://issues.apache.org/jira/browse/IGNITE-8671
>
> I changed the priority to blocker. At this point I suggest the following:
> - we either remove the DEB and RPM packages from the website and readme
> - or we fix this issue ASAP as stated in the ticket.
>
> I will leave it up to you to decide.
>
> D.
>
> On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov 
> wrote:
>
>> Dmitriy,
>>
>>
>> SystemD supports running multiple instances of one service – this is done
>> through @-like syntax: 'sudo systemctl start apache-ignite@> file name>', so that with every unique command string there will be
>> started
>> / stopped unique instance of Apache Ignite. And all instances can be
>> restarted / stopped / enabled on boot / etc. simultaneously through 'sudo
>> systemctl  apache-ignite@*'.
>>
>> Still, I can add a note about possibility of starting Apache Ignite
>> manually through ignite.sh with a reference to corresponding documentation
>> section, information where to look for the root of Apache Ignite
>> installation and how to correctly start Apache Ignite in terms of
>> permissions.
>>
>> File the documentation updates ticket?
>>
>>
>> On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan 
>> wrote:
>>
>> > Petr,
>> >
>> > Most of the users will download and install Ignite so they can develop
>> with
>> > it. This means that they will be starting more than one node, which is
>> > impossible if Ignite is a service. We should provide instructions to do
>> > both.
>> >
>> > D.
>> >
>> > On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov 
>> wrote:
>> >
>> > > Dmitriy,
>> > >
>> > >
>> > > Current packages design (both RPM and DEB) was reviewed and approved
>> by
>> > > community. I do not quite remember why service-based startup was
>> chosen
>> > but
>> > > it seems rather logical and Unix-compliant – under Linux almost every
>> > > service software is packed this way, which gives some benefits like
>> > service
>> > > autostart on reboot, centralized running nodes management (through
>> > > systemctl), etc. There is no point in packing binary into Linux
>> packages
>> > if
>> > > it then will be used as standalone executable.
>> > > Yet, current design does not limit advanced user from running Apache
>> > Ignite
>> > > as standalone process – executing
>> /usr/share/apache-ignite/bin/ignite.sh
>> > > with parameters will start Apache Ignite node as if it was delivered
>> by
>> > > binary archive.
>> > >
>> > >
>> > >
>> > > On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan <
>> dsetrak...@apache.org>
>> > > wrote:
>> > >
>> > > > Petr,
>> > > >
>> > > > Why do we even suggest starting Ignite as a service? Why not just
>> start
>> > > > Ignite instance as a stand-alone process? This should work, no?
>> > > >
>> > > > D.
>> > > >
>> > > > On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov 
>> > > wrote:
>> > > >
>> > > > > Unfortunately, it seems to be impossible (at least for now) — [1].
>> > > > > So we can say that current package design is for native Linux
>> > > > installation
>> > > > > only.
>> > > > >
>> > > > >
>> > > > > https://issues.apache.org/jira/browse/IGNITE-8671?
>> > > > > focusedCommentId=16496813=com.atlassian.jira.
>> > > > > plugin.system.issuetabpanels:comment-tabpanel#comment-16496813
>> > > > >
>> > > > >
>> > > > > > On 31 May 2018, at 18:22, Petr Ivanov 
>> wrote:
>> > > > > >
>> > > > > > Filed https://issues.apache.org/jira/browse/IGNITE-8671 <
>> > > > > https://issues.apache.org/jira/browse/IGNITE-8671>
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >> On 31 May 2018, at 17:56, Dmitriy Setrakyan <
>> > dsetrak...@apache.org
>> > > > > > wrote:
>> > > > > >>
>> > > > > >> On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov <
>> mr.wei...@gmail.com
>> > > > > > wrote:
>> > > > > >>
>> > > > > >>> I’ll start the investigation.
>> > > > > >>>
>> > > > > >>
>> > > > > >> Can you please file a ticket so we can track it?
>> > > > > >
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

Peter,

I have reopened this ticket:
https://issues.apache.org/jira/browse/IGNITE-8671

I changed the priority to blocker. At this point I suggest the following:
- we either remove the DEB and RPM packages from the website and readme
- or we fix this issue ASAP as stated in the ticket.

I will leave it up to you to decide.

D.

On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov  wrote:

> Dmitriy,
>
>
> SystemD supports running multiple instances of one service – this is done
> through @-like syntax: 'sudo systemctl start apache-ignite@ file name>', so that with every unique command string there will be started
> / stopped unique instance of Apache Ignite. And all instances can be
> restarted / stopped / enabled on boot / etc. simultaneously through 'sudo
> systemctl  apache-ignite@*'.
>
> Still, I can add a note about possibility of starting Apache Ignite
> manually through ignite.sh with a reference to corresponding documentation
> section, information where to look for the root of Apache Ignite
> installation and how to correctly start Apache Ignite in terms of
> permissions.
>
> File the documentation updates ticket?
>
>
> On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan 
> wrote:
>
> > Petr,
> >
> > Most of the users will download and install Ignite so they can develop
> with
> > it. This means that they will be starting more than one node, which is
> > impossible if Ignite is a service. We should provide instructions to do
> > both.
> >
> > D.
> >
> > On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov 
> wrote:
> >
> > > Dmitriy,
> > >
> > >
> > > Current packages design (both RPM and DEB) was reviewed and approved by
> > > community. I do not quite remember why service-based startup was chosen
> > but
> > > it seems rather logical and Unix-compliant – under Linux almost every
> > > service software is packed this way, which gives some benefits like
> > service
> > > autostart on reboot, centralized running nodes management (through
> > > systemctl), etc. There is no point in packing binary into Linux
> packages
> > if
> > > it then will be used as standalone executable.
> > > Yet, current design does not limit advanced user from running Apache
> > Ignite
> > > as standalone process – executing /usr/share/apache-ignite/bin/
> ignite.sh
> > > with parameters will start Apache Ignite node as if it was delivered by
> > > binary archive.
> > >
> > >
> > >
> > > On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan  >
> > > wrote:
> > >
> > > > Petr,
> > > >
> > > > Why do we even suggest starting Ignite as a service? Why not just
> start
> > > > Ignite instance as a stand-alone process? This should work, no?
> > > >
> > > > D.
> > > >
> > > > On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov 
> > > wrote:
> > > >
> > > > > Unfortunately, it seems to be impossible (at least for now) — [1].
> > > > > So we can say that current package design is for native Linux
> > > > installation
> > > > > only.
> > > > >
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-8671?
> > > > > focusedCommentId=16496813=com.atlassian.jira.
> > > > > plugin.system.issuetabpanels:comment-tabpanel#comment-16496813
> > > > >
> > > > >
> > > > > > On 31 May 2018, at 18:22, Petr Ivanov 
> wrote:
> > > > > >
> > > > > > Filed https://issues.apache.org/jira/browse/IGNITE-8671 <
> > > > > https://issues.apache.org/jira/browse/IGNITE-8671>
> > > > > >
> > > > > >
> > > > > >
> > > > > >> On 31 May 2018, at 17:56, Dmitriy Setrakyan <
> > dsetrak...@apache.org
> > > > > > wrote:
> > > > > >>
> > > > > >> On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov <
> mr.wei...@gmail.com
> > > > > > wrote:
> > > > > >>
> > > > > >>> I’ll start the investigation.
> > > > > >>>
> > > > > >>
> > > > > >> Can you please file a ticket so we can track it?
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Peter Ivanov]

Dmitriy,


SystemD supports running multiple instances of one service – this is done
through @-like syntax: 'sudo systemctl start apache-ignite@', so that with every unique command string there will be started
/ stopped unique instance of Apache Ignite. And all instances can be
restarted / stopped / enabled on boot / etc. simultaneously through 'sudo
systemctl  apache-ignite@*'.

Still, I can add a note about possibility of starting Apache Ignite
manually through ignite.sh with a reference to corresponding documentation
section, information where to look for the root of Apache Ignite
installation and how to correctly start Apache Ignite in terms of
permissions.

File the documentation updates ticket?


On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan 
wrote:

> Petr,
>
> Most of the users will download and install Ignite so they can develop with
> it. This means that they will be starting more than one node, which is
> impossible if Ignite is a service. We should provide instructions to do
> both.
>
> D.
>
> On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov  wrote:
>
> > Dmitriy,
> >
> >
> > Current packages design (both RPM and DEB) was reviewed and approved by
> > community. I do not quite remember why service-based startup was chosen
> but
> > it seems rather logical and Unix-compliant – under Linux almost every
> > service software is packed this way, which gives some benefits like
> service
> > autostart on reboot, centralized running nodes management (through
> > systemctl), etc. There is no point in packing binary into Linux packages
> if
> > it then will be used as standalone executable.
> > Yet, current design does not limit advanced user from running Apache
> Ignite
> > as standalone process – executing /usr/share/apache-ignite/bin/ignite.sh
> > with parameters will start Apache Ignite node as if it was delivered by
> > binary archive.
> >
> >
> >
> > On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan 
> > wrote:
> >
> > > Petr,
> > >
> > > Why do we even suggest starting Ignite as a service? Why not just start
> > > Ignite instance as a stand-alone process? This should work, no?
> > >
> > > D.
> > >
> > > On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov 
> > wrote:
> > >
> > > > Unfortunately, it seems to be impossible (at least for now) — [1].
> > > > So we can say that current package design is for native Linux
> > > installation
> > > > only.
> > > >
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-8671?
> > > > focusedCommentId=16496813=com.atlassian.jira.
> > > > plugin.system.issuetabpanels:comment-tabpanel#comment-16496813
> > > >
> > > >
> > > > > On 31 May 2018, at 18:22, Petr Ivanov  wrote:
> > > > >
> > > > > Filed https://issues.apache.org/jira/browse/IGNITE-8671 <
> > > > https://issues.apache.org/jira/browse/IGNITE-8671>
> > > > >
> > > > >
> > > > >
> > > > >> On 31 May 2018, at 17:56, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > > > > wrote:
> > > > >>
> > > > >> On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov  > > > > wrote:
> > > > >>
> > > > >>> I’ll start the investigation.
> > > > >>>
> > > > >>
> > > > >> Can you please file a ticket so we can track it?
> > > > >
> > > >
> > > >
> > >
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

Petr,

Most of the users will download and install Ignite so they can develop with
it. This means that they will be starting more than one node, which is
impossible if Ignite is a service. We should provide instructions to do
both.

D.

On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov  wrote:

> Dmitriy,
>
>
> Current packages design (both RPM and DEB) was reviewed and approved by
> community. I do not quite remember why service-based startup was chosen but
> it seems rather logical and Unix-compliant – under Linux almost every
> service software is packed this way, which gives some benefits like service
> autostart on reboot, centralized running nodes management (through
> systemctl), etc. There is no point in packing binary into Linux packages if
> it then will be used as standalone executable.
> Yet, current design does not limit advanced user from running Apache Ignite
> as standalone process – executing /usr/share/apache-ignite/bin/ignite.sh
> with parameters will start Apache Ignite node as if it was delivered by
> binary archive.
>
>
>
> On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan 
> wrote:
>
> > Petr,
> >
> > Why do we even suggest starting Ignite as a service? Why not just start
> > Ignite instance as a stand-alone process? This should work, no?
> >
> > D.
> >
> > On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov 
> wrote:
> >
> > > Unfortunately, it seems to be impossible (at least for now) — [1].
> > > So we can say that current package design is for native Linux
> > installation
> > > only.
> > >
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-8671?
> > > focusedCommentId=16496813=com.atlassian.jira.
> > > plugin.system.issuetabpanels:comment-tabpanel#comment-16496813
> > >
> > >
> > > > On 31 May 2018, at 18:22, Petr Ivanov  wrote:
> > > >
> > > > Filed https://issues.apache.org/jira/browse/IGNITE-8671 <
> > > https://issues.apache.org/jira/browse/IGNITE-8671>
> > > >
> > > >
> > > >
> > > >> On 31 May 2018, at 17:56, Dmitriy Setrakyan  > > > wrote:
> > > >>
> > > >> On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov  > > > wrote:
> > > >>
> > > >>> I’ll start the investigation.
> > > >>>
> > > >>
> > > >> Can you please file a ticket so we can track it?
> > > >
> > >
> > >
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Peter Ivanov]

Dmitriy,


Current packages design (both RPM and DEB) was reviewed and approved by
community. I do not quite remember why service-based startup was chosen but
it seems rather logical and Unix-compliant – under Linux almost every
service software is packed this way, which gives some benefits like service
autostart on reboot, centralized running nodes management (through
systemctl), etc. There is no point in packing binary into Linux packages if
it then will be used as standalone executable.
Yet, current design does not limit advanced user from running Apache Ignite
as standalone process – executing /usr/share/apache-ignite/bin/ignite.sh
with parameters will start Apache Ignite node as if it was delivered by
binary archive.



On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan 
wrote:

> Petr,
>
> Why do we even suggest starting Ignite as a service? Why not just start
> Ignite instance as a stand-alone process? This should work, no?
>
> D.
>
> On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov  wrote:
>
> > Unfortunately, it seems to be impossible (at least for now) — [1].
> > So we can say that current package design is for native Linux
> installation
> > only.
> >
> >
> > https://issues.apache.org/jira/browse/IGNITE-8671?
> > focusedCommentId=16496813=com.atlassian.jira.
> > plugin.system.issuetabpanels:comment-tabpanel#comment-16496813
> >
> >
> > > On 31 May 2018, at 18:22, Petr Ivanov  wrote:
> > >
> > > Filed https://issues.apache.org/jira/browse/IGNITE-8671 <
> > https://issues.apache.org/jira/browse/IGNITE-8671>
> > >
> > >
> > >
> > >> On 31 May 2018, at 17:56, Dmitriy Setrakyan  > > wrote:
> > >>
> > >> On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov  > > wrote:
> > >>
> > >>> I’ll start the investigation.
> > >>>
> > >>
> > >> Can you please file a ticket so we can track it?
> > >
> >
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

Petr,

Why do we even suggest starting Ignite as a service? Why not just start
Ignite instance as a stand-alone process? This should work, no?

D.

On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov  wrote:

> Unfortunately, it seems to be impossible (at least for now) — [1].
> So we can say that current package design is for native Linux installation
> only.
>
>
> https://issues.apache.org/jira/browse/IGNITE-8671?
> focusedCommentId=16496813=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-16496813
>
>
> > On 31 May 2018, at 18:22, Petr Ivanov  wrote:
> >
> > Filed https://issues.apache.org/jira/browse/IGNITE-8671 <
> https://issues.apache.org/jira/browse/IGNITE-8671>
> >
> >
> >
> >> On 31 May 2018, at 17:56, Dmitriy Setrakyan  > wrote:
> >>
> >> On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov  > wrote:
> >>
> >>> I’ll start the investigation.
> >>>
> >>
> >> Can you please file a ticket so we can track it?
> >
>
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

Unfortunately, it seems to be impossible (at least for now) — [1].
So we can say that current package design is for native Linux installation only.


https://issues.apache.org/jira/browse/IGNITE-8671?focusedCommentId=16496813=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16496813


> On 31 May 2018, at 18:22, Petr Ivanov  wrote:
> 
> Filed https://issues.apache.org/jira/browse/IGNITE-8671 
> 
> 
> 
> 
>> On 31 May 2018, at 17:56, Dmitriy Setrakyan > > wrote:
>> 
>> On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov > > wrote:
>> 
>>> I’ll start the investigation.
>>> 
>> 
>> Can you please file a ticket so we can track it?
> 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

Filed https://issues.apache.org/jira/browse/IGNITE-8671 




> On 31 May 2018, at 17:56, Dmitriy Setrakyan  wrote:
> 
> On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov  wrote:
> 
>> I’ll start the investigation.
>> 
> 
> Can you please file a ticket so we can track it?

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov  wrote:

> I’ll start the investigation.
>

Can you please file a ticket so we can track it?

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

I’ll start the investigation.



> On 31 May 2018, at 17:44, Dmitriy Setrakyan  wrote:
> 
> Petr,
> 
> I still get errors, see below... The worst part here is that I get an error
> message to look in the log, but I have no idea where the log file is
> located.
> 
> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> *d@DmitriyPC:~$ sudo service dbus start[sudo] password for d: * Starting
>> system message bus dbus
>> 
>> [ OK ]d@DmitriyPC:~$ sudo systemctl start
>> apache-ignite@default-config.xmlFailed to start
>> apache-ign...@default-config.xml.service: Launch helper exited with unknown
>> return code 1See system logs and 'systemctl status
>> apache-ign...@default-config.xml.service' for details.d@DmitriyPC:~$ sudo
>> systemctl status apache-ign...@default-config.xml.serviceFailed to get
>> properties: Launch helper exited with unknown return code 1d@DmitriyPC:~$*
> 
> 
> 
> On Wed, May 30, 2018 at 10:27 PM, Peter Ivanov  wrote:
> 
>> Dmitriy,
>> 
>> Can you try starting dbus manually? sudo service dbus start
>> 
>> If it still does not work, I will have to held an investigation on running
>> systemd services on Windows 10 WSL
>> 
>> 
>> On Thu, 31 May 2018 at 00:31, Dmitriy Setrakyan 
>> wrote:
>> 
>>> On Wed, May 30, 2018 at 2:09 PM, Peter Ivanov 
>> wrote:
>>> 
 Dmitriy,
 
 What kind of Ubuntu installation do you have (and what version)?
 Is it WSL under Windows 10 or containerized (docker)?
 
 
>>> Windows Ubuntu App -
>>> https://docs.microsoft.com/en-us/windows/wsl/install-win10
>>> 
>>> D.
>>> 
>> 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

Petr,

I still get errors, see below... The worst part here is that I get an error
message to look in the log, but I have no idea where the log file is
located.


>
>
>
>
>
>
>
>
> *d@DmitriyPC:~$ sudo service dbus start[sudo] password for d: * Starting
> system message bus dbus
>
>  [ OK ]d@DmitriyPC:~$ sudo systemctl start
> apache-ignite@default-config.xmlFailed to start
> apache-ign...@default-config.xml.service: Launch helper exited with unknown
> return code 1See system logs and 'systemctl status
> apache-ign...@default-config.xml.service' for details.d@DmitriyPC:~$ sudo
> systemctl status apache-ign...@default-config.xml.serviceFailed to get
> properties: Launch helper exited with unknown return code 1d@DmitriyPC:~$*



On Wed, May 30, 2018 at 10:27 PM, Peter Ivanov  wrote:

> Dmitriy,
>
> Can you try starting dbus manually? sudo service dbus start
>
> If it still does not work, I will have to held an investigation on running
> systemd services on Windows 10 WSL
>
>
> On Thu, 31 May 2018 at 00:31, Dmitriy Setrakyan 
> wrote:
>
> > On Wed, May 30, 2018 at 2:09 PM, Peter Ivanov 
> wrote:
> >
> > > Dmitriy,
> > >
> > > What kind of Ubuntu installation do you have (and what version)?
> > > Is it WSL under Windows 10 or containerized (docker)?
> > >
> > >
> > Windows Ubuntu App -
> > https://docs.microsoft.com/en-us/windows/wsl/install-win10
> >
> > D.
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Peter Ivanov]

Dmitriy,

Can you try starting dbus manually? sudo service dbus start

If it still does not work, I will have to held an investigation on running
systemd services on Windows 10 WSL


On Thu, 31 May 2018 at 00:31, Dmitriy Setrakyan 
wrote:

> On Wed, May 30, 2018 at 2:09 PM, Peter Ivanov  wrote:
>
> > Dmitriy,
> >
> > What kind of Ubuntu installation do you have (and what version)?
> > Is it WSL under Windows 10 or containerized (docker)?
> >
> >
> Windows Ubuntu App -
> https://docs.microsoft.com/en-us/windows/wsl/install-win10
>
> D.
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Denis Magda]

Folks,

We've completed and closed all the pending 2.5 documentation tickets.
Thanks to everyone involved for speeding the process up.

I'm going to prepare a 2.5 blog on https://blogs.apache.org tomorrow
listing all the major improvements and will send an official announcement
right after that.

--
Denis

On Wed, May 30, 2018 at 2:30 PM, Dmitriy Setrakyan 
wrote:

> On Wed, May 30, 2018 at 2:09 PM, Peter Ivanov  wrote:
>
> > Dmitriy,
> >
> > What kind of Ubuntu installation do you have (and what version)?
> > Is it WSL under Windows 10 or containerized (docker)?
> >
> >
> Windows Ubuntu App -
> https://docs.microsoft.com/en-us/windows/wsl/install-win10
>
> D.
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

On Wed, May 30, 2018 at 2:09 PM, Peter Ivanov  wrote:

> Dmitriy,
>
> What kind of Ubuntu installation do you have (and what version)?
> Is it WSL under Windows 10 or containerized (docker)?
>
>
Windows Ubuntu App -
https://docs.microsoft.com/en-us/windows/wsl/install-win10

D.

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Peter Ivanov]

Dmitriy,

What kind of Ubuntu installation do you have (and what version)?
Is it WSL under Windows 10 or containerized (docker)?


On Wed, 30 May 2018 at 19:52, Dmitriy Setrakyan 
wrote:

> Petr,
>
> I have finally was able to install Ignite Debian package. But then I got
> stuck at the very next instruction:
>
>
> > *d@DmitriyPC:~$ sudo systemctl start
> > apache-ignite@default-config.xmlFailed to connect to bus: No such file
> or
> > directory*
>
>
> D.
>
> On Wed, May 30, 2018 at 7:40 AM, Petr Ivanov  wrote:
>
> > Sometimes Ubuntu with requested and dependency packages recommends
> > additional packages (which is controlled by corresponding directive in
> > package).
> > This option --no-install-recommends makes sure that these packages will
> be
> > skipped and overall installation will be more compact and precise.
> >
> > There is no such option for YUM (as far as I am aware of).
> >
> >
> >
> > > On 30 May 2018, at 17:16, Dmitriy Setrakyan 
> > wrote:
> > >
> > > Petr,
> > >
> > > Can you tell me what this flag does: "--no-install-recommends"?
> > >
> > > I am seeing that it is set for Debian, but not for RPM.
> > >
> > > D.
> > >
> > > On Wed, May 30, 2018 at 7:07 AM, Petr Ivanov 
> > wrote:
> > >
> > >> Of course: https://apacheignite.readme.io/docs/getting-started#
> > >> alternative-installation-options  > >> io/docs/getting-started#alternative-installation-options>
> > >> Snippet "DEB repository setup"
> > >>
> > >>
> > >>
> > >>
> > >>> On 30 May 2018, at 16:59, Dmitriy Setrakyan 
> > >> wrote:
> > >>>
> > >>> Petr, can you provide a link to the Debian snippet on readme.io? I
> > >> cannot
> > >>> find it.
> > >>>
> > >>> On Wed, May 30, 2018 at 6:16 AM, Petr Ivanov 
> > >> wrote:
> > >>>
> >  Docker images for Apache Ignite [1] and Web Console [2] 2.5.0 are
> > >> uploaded.
> > 
> > 
> >  [1] https://hub.docker.com/r/apacheignite/ignite/tags
> >  [2] https://hub.docker.com/r/apacheignite/web-console-
> > standalone/tags/
> > 
> > 
> > 
> > > On 30 May 2018, at 06:55, Petr Ivanov  wrote:
> > >
> > > Instructions for RPM Package Installation (snippet with repository
> >  configuration) at ignite.apache.org  are
> >  obsolete and should be replaced by apacheignite.readme.io <
> >  http://apacheignite.readme.io/> snippet.
> > >
> > >
> > >
> > >> On 30 May 2018, at 02:57, Prachi Garg   >  pg...@gridgain.com>> wrote:
> > >>
> > >> Peter,
> > >>
> > >> I updated the RPM and DEB description on the downloads page[1]
> >  (following the instructions on the documentation [2]). Please check
> > that
> >  the repositories and installation instructions are up-to-date.
> > >>
> > >> [1] https://ignite.apache.org/download.cgi#rpm-package <
> >  https://ignite.apache.org/download.cgi#rpm-package>
> > >> [2] https://apacheignite.readme.io/docs/getting-started#
> >  section-rpm-deb-packages-installation  >  io/docs/getting-started#section-rpm-deb-packages-installation>
> > >>
> > >> On Tue, May 29, 2018 at 4:47 PM, Dmitriy Setrakyan <
> >  dsetrak...@apache.org > wrote:
> > >> I just tried the Debian install. This is what I got after
> executing
> >  "sudo
> > >> apt get" command:
> > >>
> > >>
> > >>>
> > >>> *E: The repository 'https://apache.org/dist/ignite/deb <
> >  https://apache.org/dist/ignite/deb>
> > >>>  >  ignite/deb>> apache-ignite Release' does not have a
> > >>> Release file.N: Updating from such a repository can't be done
> >  securely, and
> > >>> is therefore disabled by default.N: See apt-secure(8) manpage for
> > >>> repository creation and user configuration details.*
> > >>
> > >>
> > >> D.
> > >>
> > >> On Tue, May 29, 2018 at 4:42 PM, Denis Magda  >  > wrote:
> > >>
> > >>> Andrey,
> > >>>
> > >>> Please help to generate 2.5 release HTML file and add it to
> Ignite
> >  website
> > >>> SVN. Sergey K and Ilya S. should be able to assist with this.
> > >>>
> > >>> Sergey Chugunov and Ivan R., finalize the docs as soon as you
> can.
> > We
> > >>> can't announce the release and close it without having the docs
> > done.
> > >>>
> > >>> --
> > >>> Denis
> > >>>
> > >>>
> > >>> On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  >  > wrote:
> > >>>
> >  Folks,
> > 
> >  I have released 2.5 documentation on readme.io <
> http://readme.io/
> > >.
> >  Also, the downloads page
> >  on
> >  the website is updated with 2.5 release. Mauricio will work on
> >  updating
> >  the
> >  latest doc reference.
> > 
> > 
> 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

Petr,

I have finally was able to install Ignite Debian package. But then I got
stuck at the very next instruction:


> *d@DmitriyPC:~$ sudo systemctl start
> apache-ignite@default-config.xmlFailed to connect to bus: No such file or
> directory*


D.

On Wed, May 30, 2018 at 7:40 AM, Petr Ivanov  wrote:

> Sometimes Ubuntu with requested and dependency packages recommends
> additional packages (which is controlled by corresponding directive in
> package).
> This option --no-install-recommends makes sure that these packages will be
> skipped and overall installation will be more compact and precise.
>
> There is no such option for YUM (as far as I am aware of).
>
>
>
> > On 30 May 2018, at 17:16, Dmitriy Setrakyan 
> wrote:
> >
> > Petr,
> >
> > Can you tell me what this flag does: "--no-install-recommends"?
> >
> > I am seeing that it is set for Debian, but not for RPM.
> >
> > D.
> >
> > On Wed, May 30, 2018 at 7:07 AM, Petr Ivanov 
> wrote:
> >
> >> Of course: https://apacheignite.readme.io/docs/getting-started#
> >> alternative-installation-options  >> io/docs/getting-started#alternative-installation-options>
> >> Snippet "DEB repository setup"
> >>
> >>
> >>
> >>
> >>> On 30 May 2018, at 16:59, Dmitriy Setrakyan 
> >> wrote:
> >>>
> >>> Petr, can you provide a link to the Debian snippet on readme.io? I
> >> cannot
> >>> find it.
> >>>
> >>> On Wed, May 30, 2018 at 6:16 AM, Petr Ivanov 
> >> wrote:
> >>>
>  Docker images for Apache Ignite [1] and Web Console [2] 2.5.0 are
> >> uploaded.
> 
> 
>  [1] https://hub.docker.com/r/apacheignite/ignite/tags
>  [2] https://hub.docker.com/r/apacheignite/web-console-
> standalone/tags/
> 
> 
> 
> > On 30 May 2018, at 06:55, Petr Ivanov  wrote:
> >
> > Instructions for RPM Package Installation (snippet with repository
>  configuration) at ignite.apache.org  are
>  obsolete and should be replaced by apacheignite.readme.io <
>  http://apacheignite.readme.io/> snippet.
> >
> >
> >
> >> On 30 May 2018, at 02:57, Prachi Garg   pg...@gridgain.com>> wrote:
> >>
> >> Peter,
> >>
> >> I updated the RPM and DEB description on the downloads page[1]
>  (following the instructions on the documentation [2]). Please check
> that
>  the repositories and installation instructions are up-to-date.
> >>
> >> [1] https://ignite.apache.org/download.cgi#rpm-package <
>  https://ignite.apache.org/download.cgi#rpm-package>
> >> [2] https://apacheignite.readme.io/docs/getting-started#
>  section-rpm-deb-packages-installation   io/docs/getting-started#section-rpm-deb-packages-installation>
> >>
> >> On Tue, May 29, 2018 at 4:47 PM, Dmitriy Setrakyan <
>  dsetrak...@apache.org > wrote:
> >> I just tried the Debian install. This is what I got after executing
>  "sudo
> >> apt get" command:
> >>
> >>
> >>>
> >>> *E: The repository 'https://apache.org/dist/ignite/deb <
>  https://apache.org/dist/ignite/deb>
> >>>   ignite/deb>> apache-ignite Release' does not have a
> >>> Release file.N: Updating from such a repository can't be done
>  securely, and
> >>> is therefore disabled by default.N: See apt-secure(8) manpage for
> >>> repository creation and user configuration details.*
> >>
> >>
> >> D.
> >>
> >> On Tue, May 29, 2018 at 4:42 PM, Denis Magda   > wrote:
> >>
> >>> Andrey,
> >>>
> >>> Please help to generate 2.5 release HTML file and add it to Ignite
>  website
> >>> SVN. Sergey K and Ilya S. should be able to assist with this.
> >>>
> >>> Sergey Chugunov and Ivan R., finalize the docs as soon as you can.
> We
> >>> can't announce the release and close it without having the docs
> done.
> >>>
> >>> --
> >>> Denis
> >>>
> >>>
> >>> On Tue, May 29, 2018 at 4:20 PM, Prachi Garg   > wrote:
> >>>
>  Folks,
> 
>  I have released 2.5 documentation on readme.io  >.
>  Also, the downloads page
>  on
>  the website is updated with 2.5 release. Mauricio will work on
>  updating
>  the
>  latest doc reference.
> 
> 
>  Andrey,
> 
>  The following still needs attention:
> 
>   1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/ <
>  http://ignite.apache.org/releases/2.5.0/>
>   2. Zookeper documentation -
>   https://issues.apache.org/jira/browse/IGNITE-7900 <
>  https://issues.apache.org/jira/browse/IGNITE-7900>
>   3. Consistency check utilities docs -
>   https://issues.apache.org/jira/browse/IGNITE-8524 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

Sometimes Ubuntu with requested and dependency packages recommends additional 
packages (which is controlled by corresponding directive in package).
This option --no-install-recommends makes sure that these packages will be 
skipped and overall installation will be more compact and precise.

There is no such option for YUM (as far as I am aware of).



> On 30 May 2018, at 17:16, Dmitriy Setrakyan  wrote:
> 
> Petr,
> 
> Can you tell me what this flag does: "--no-install-recommends"?
> 
> I am seeing that it is set for Debian, but not for RPM.
> 
> D.
> 
> On Wed, May 30, 2018 at 7:07 AM, Petr Ivanov  wrote:
> 
>> Of course: https://apacheignite.readme.io/docs/getting-started#
>> alternative-installation-options > io/docs/getting-started#alternative-installation-options>
>> Snippet "DEB repository setup"
>> 
>> 
>> 
>> 
>>> On 30 May 2018, at 16:59, Dmitriy Setrakyan 
>> wrote:
>>> 
>>> Petr, can you provide a link to the Debian snippet on readme.io? I
>> cannot
>>> find it.
>>> 
>>> On Wed, May 30, 2018 at 6:16 AM, Petr Ivanov 
>> wrote:
>>> 
 Docker images for Apache Ignite [1] and Web Console [2] 2.5.0 are
>> uploaded.
 
 
 [1] https://hub.docker.com/r/apacheignite/ignite/tags
 [2] https://hub.docker.com/r/apacheignite/web-console-standalone/tags/
 
 
 
> On 30 May 2018, at 06:55, Petr Ivanov  wrote:
> 
> Instructions for RPM Package Installation (snippet with repository
 configuration) at ignite.apache.org  are
 obsolete and should be replaced by apacheignite.readme.io <
 http://apacheignite.readme.io/> snippet.
> 
> 
> 
>> On 30 May 2018, at 02:57, Prachi Garg >>> pg...@gridgain.com>> wrote:
>> 
>> Peter,
>> 
>> I updated the RPM and DEB description on the downloads page[1]
 (following the instructions on the documentation [2]). Please check that
 the repositories and installation instructions are up-to-date.
>> 
>> [1] https://ignite.apache.org/download.cgi#rpm-package <
 https://ignite.apache.org/download.cgi#rpm-package>
>> [2] https://apacheignite.readme.io/docs/getting-started#
 section-rpm-deb-packages-installation 
>> 
>> On Tue, May 29, 2018 at 4:47 PM, Dmitriy Setrakyan <
 dsetrak...@apache.org > wrote:
>> I just tried the Debian install. This is what I got after executing
 "sudo
>> apt get" command:
>> 
>> 
>>> 
>>> *E: The repository 'https://apache.org/dist/ignite/deb <
 https://apache.org/dist/ignite/deb>
>>> > apache-ignite Release' does not have a
>>> Release file.N: Updating from such a repository can't be done
 securely, and
>>> is therefore disabled by default.N: See apt-secure(8) manpage for
>>> repository creation and user configuration details.*
>> 
>> 
>> D.
>> 
>> On Tue, May 29, 2018 at 4:42 PM, Denis Magda >>> > wrote:
>> 
>>> Andrey,
>>> 
>>> Please help to generate 2.5 release HTML file and add it to Ignite
 website
>>> SVN. Sergey K and Ilya S. should be able to assist with this.
>>> 
>>> Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
>>> can't announce the release and close it without having the docs done.
>>> 
>>> --
>>> Denis
>>> 
>>> 
>>> On Tue, May 29, 2018 at 4:20 PM, Prachi Garg >>> > wrote:
>>> 
 Folks,
 
 I have released 2.5 documentation on readme.io .
 Also, the downloads page
 on
 the website is updated with 2.5 release. Mauricio will work on
 updating
 the
 latest doc reference.
 
 
 Andrey,
 
 The following still needs attention:
 
  1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/ <
 http://ignite.apache.org/releases/2.5.0/>
  2. Zookeper documentation -
  https://issues.apache.org/jira/browse/IGNITE-7900 <
 https://issues.apache.org/jira/browse/IGNITE-7900>
  3. Consistency check utilities docs -
  https://issues.apache.org/jira/browse/IGNITE-8524 <
 https://issues.apache.org/jira/browse/IGNITE-8524>
 
 
 Thanks,
 -Prachi
 
 On Tue, May 29, 2018 at 2:08 PM, Andrey Gura >>> > wrote:
 
> Pavel,
> 
> Thanks a lot!
> 
> 
> 
> вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn >>> >:
> 
>> NuGet (.NET) packages pushed:
>> https://www.nuget.org/packages?q=Apache.Ignite <
 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

Petr,

Can you tell me what this flag does: "--no-install-recommends"?

I am seeing that it is set for Debian, but not for RPM.

D.

On Wed, May 30, 2018 at 7:07 AM, Petr Ivanov  wrote:

> Of course: https://apacheignite.readme.io/docs/getting-started#
> alternative-installation-options  io/docs/getting-started#alternative-installation-options>
> Snippet "DEB repository setup"
>
>
>
>
> > On 30 May 2018, at 16:59, Dmitriy Setrakyan 
> wrote:
> >
> > Petr, can you provide a link to the Debian snippet on readme.io? I
> cannot
> > find it.
> >
> > On Wed, May 30, 2018 at 6:16 AM, Petr Ivanov 
> wrote:
> >
> >> Docker images for Apache Ignite [1] and Web Console [2] 2.5.0 are
> uploaded.
> >>
> >>
> >> [1] https://hub.docker.com/r/apacheignite/ignite/tags
> >> [2] https://hub.docker.com/r/apacheignite/web-console-standalone/tags/
> >>
> >>
> >>
> >>> On 30 May 2018, at 06:55, Petr Ivanov  wrote:
> >>>
> >>> Instructions for RPM Package Installation (snippet with repository
> >> configuration) at ignite.apache.org  are
> >> obsolete and should be replaced by apacheignite.readme.io <
> >> http://apacheignite.readme.io/> snippet.
> >>>
> >>>
> >>>
>  On 30 May 2018, at 02:57, Prachi Garg  >> pg...@gridgain.com>> wrote:
> 
>  Peter,
> 
>  I updated the RPM and DEB description on the downloads page[1]
> >> (following the instructions on the documentation [2]). Please check that
> >> the repositories and installation instructions are up-to-date.
> 
>  [1] https://ignite.apache.org/download.cgi#rpm-package <
> >> https://ignite.apache.org/download.cgi#rpm-package>
>  [2] https://apacheignite.readme.io/docs/getting-started#
> >> section-rpm-deb-packages-installation  >> io/docs/getting-started#section-rpm-deb-packages-installation>
> 
>  On Tue, May 29, 2018 at 4:47 PM, Dmitriy Setrakyan <
> >> dsetrak...@apache.org > wrote:
>  I just tried the Debian install. This is what I got after executing
> >> "sudo
>  apt get" command:
> 
> 
> >
> > *E: The repository 'https://apache.org/dist/ignite/deb <
> >> https://apache.org/dist/ignite/deb>
> >  >> ignite/deb>> apache-ignite Release' does not have a
> > Release file.N: Updating from such a repository can't be done
> >> securely, and
> > is therefore disabled by default.N: See apt-secure(8) manpage for
> > repository creation and user configuration details.*
> 
> 
>  D.
> 
>  On Tue, May 29, 2018 at 4:42 PM, Denis Magda  >> > wrote:
> 
> > Andrey,
> >
> > Please help to generate 2.5 release HTML file and add it to Ignite
> >> website
> > SVN. Sergey K and Ilya S. should be able to assist with this.
> >
> > Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
> > can't announce the release and close it without having the docs done.
> >
> > --
> > Denis
> >
> >
> > On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  >> > wrote:
> >
> >> Folks,
> >>
> >> I have released 2.5 documentation on readme.io .
> >> Also, the downloads page
> >> on
> >> the website is updated with 2.5 release. Mauricio will work on
> >> updating
> >> the
> >> latest doc reference.
> >>
> >>
> >> Andrey,
> >>
> >> The following still needs attention:
> >>
> >>   1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/ <
> >> http://ignite.apache.org/releases/2.5.0/>
> >>   2. Zookeper documentation -
> >>   https://issues.apache.org/jira/browse/IGNITE-7900 <
> >> https://issues.apache.org/jira/browse/IGNITE-7900>
> >>   3. Consistency check utilities docs -
> >>   https://issues.apache.org/jira/browse/IGNITE-8524 <
> >> https://issues.apache.org/jira/browse/IGNITE-8524>
> >>
> >>
> >> Thanks,
> >> -Prachi
> >>
> >> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura  >> > wrote:
> >>
> >>> Pavel,
> >>>
> >>> Thanks a lot!
> >>>
> >>>
> >>>
> >>> вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn  >> >:
> >>>
>  NuGet (.NET) packages pushed:
>  https://www.nuget.org/packages?q=Apache.Ignite <
> >> https://www.nuget.org/packages?q=Apache.Ignite>
> 
>  On Tue, May 29, 2018 at 8:59 PM, Andrey Gura  >> >
> >> wrote:
> 
> > Dmitry,
> >
> > First we should check docker images. Also we are waiting for
> > publishing of artifacts to Maven Central.
> >
> > On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
> > mailto:dsetrak...@apache.org>> wrote:
> >>
> >>
> >> On Tue, May 29, 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

Of course: 
https://apacheignite.readme.io/docs/getting-started#alternative-installation-options
 

Snippet "DEB repository setup"




> On 30 May 2018, at 16:59, Dmitriy Setrakyan  wrote:
> 
> Petr, can you provide a link to the Debian snippet on readme.io? I cannot
> find it.
> 
> On Wed, May 30, 2018 at 6:16 AM, Petr Ivanov  wrote:
> 
>> Docker images for Apache Ignite [1] and Web Console [2] 2.5.0 are uploaded.
>> 
>> 
>> [1] https://hub.docker.com/r/apacheignite/ignite/tags
>> [2] https://hub.docker.com/r/apacheignite/web-console-standalone/tags/
>> 
>> 
>> 
>>> On 30 May 2018, at 06:55, Petr Ivanov  wrote:
>>> 
>>> Instructions for RPM Package Installation (snippet with repository
>> configuration) at ignite.apache.org  are
>> obsolete and should be replaced by apacheignite.readme.io <
>> http://apacheignite.readme.io/> snippet.
>>> 
>>> 
>>> 
 On 30 May 2018, at 02:57, Prachi Garg > pg...@gridgain.com>> wrote:
 
 Peter,
 
 I updated the RPM and DEB description on the downloads page[1]
>> (following the instructions on the documentation [2]). Please check that
>> the repositories and installation instructions are up-to-date.
 
 [1] https://ignite.apache.org/download.cgi#rpm-package <
>> https://ignite.apache.org/download.cgi#rpm-package>
 [2] https://apacheignite.readme.io/docs/getting-started#
>> section-rpm-deb-packages-installation > io/docs/getting-started#section-rpm-deb-packages-installation>
 
 On Tue, May 29, 2018 at 4:47 PM, Dmitriy Setrakyan <
>> dsetrak...@apache.org > wrote:
 I just tried the Debian install. This is what I got after executing
>> "sudo
 apt get" command:
 
 
> 
> *E: The repository 'https://apache.org/dist/ignite/deb <
>> https://apache.org/dist/ignite/deb>
> > ignite/deb>> apache-ignite Release' does not have a
> Release file.N: Updating from such a repository can't be done
>> securely, and
> is therefore disabled by default.N: See apt-secure(8) manpage for
> repository creation and user configuration details.*
 
 
 D.
 
 On Tue, May 29, 2018 at 4:42 PM, Denis Magda > > wrote:
 
> Andrey,
> 
> Please help to generate 2.5 release HTML file and add it to Ignite
>> website
> SVN. Sergey K and Ilya S. should be able to assist with this.
> 
> Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
> can't announce the release and close it without having the docs done.
> 
> --
> Denis
> 
> 
> On Tue, May 29, 2018 at 4:20 PM, Prachi Garg > > wrote:
> 
>> Folks,
>> 
>> I have released 2.5 documentation on readme.io .
>> Also, the downloads page
>> on
>> the website is updated with 2.5 release. Mauricio will work on
>> updating
>> the
>> latest doc reference.
>> 
>> 
>> Andrey,
>> 
>> The following still needs attention:
>> 
>>   1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/ <
>> http://ignite.apache.org/releases/2.5.0/>
>>   2. Zookeper documentation -
>>   https://issues.apache.org/jira/browse/IGNITE-7900 <
>> https://issues.apache.org/jira/browse/IGNITE-7900>
>>   3. Consistency check utilities docs -
>>   https://issues.apache.org/jira/browse/IGNITE-8524 <
>> https://issues.apache.org/jira/browse/IGNITE-8524>
>> 
>> 
>> Thanks,
>> -Prachi
>> 
>> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura > > wrote:
>> 
>>> Pavel,
>>> 
>>> Thanks a lot!
>>> 
>>> 
>>> 
>>> вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn > >:
>>> 
 NuGet (.NET) packages pushed:
 https://www.nuget.org/packages?q=Apache.Ignite <
>> https://www.nuget.org/packages?q=Apache.Ignite>
 
 On Tue, May 29, 2018 at 8:59 PM, Andrey Gura > >
>> wrote:
 
> Dmitry,
> 
> First we should check docker images. Also we are waiting for
> publishing of artifacts to Maven Central.
> 
> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
> mailto:dsetrak...@apache.org>> wrote:
>> 
>> 
>> On Tue, May 29, 2018 at 9:08 AM, Andrey Gura <
>> ag...@apache.org >
>>> wrote:
>>> 
>>> RPM and DEB packages are published to bintray [1] [2]
>>> 
>>> [1] https://bintray.com/apache/ignite-rpm <
>> https://bintray.com/apache/ignite-rpm>
>>> [2] https://bintray.com/apache/ignite-deb <
>> https://bintray.com/apache/ignite-deb>
>> 
>> 
>> Thanks, 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

Petr, can you provide a link to the Debian snippet on readme.io? I cannot
find it.

On Wed, May 30, 2018 at 6:16 AM, Petr Ivanov  wrote:

> Docker images for Apache Ignite [1] and Web Console [2] 2.5.0 are uploaded.
>
>
> [1] https://hub.docker.com/r/apacheignite/ignite/tags
> [2] https://hub.docker.com/r/apacheignite/web-console-standalone/tags/
>
>
>
> > On 30 May 2018, at 06:55, Petr Ivanov  wrote:
> >
> > Instructions for RPM Package Installation (snippet with repository
> configuration) at ignite.apache.org  are
> obsolete and should be replaced by apacheignite.readme.io <
> http://apacheignite.readme.io/> snippet.
> >
> >
> >
> >> On 30 May 2018, at 02:57, Prachi Garg  pg...@gridgain.com>> wrote:
> >>
> >> Peter,
> >>
> >> I updated the RPM and DEB description on the downloads page[1]
> (following the instructions on the documentation [2]). Please check that
> the repositories and installation instructions are up-to-date.
> >>
> >> [1] https://ignite.apache.org/download.cgi#rpm-package <
> https://ignite.apache.org/download.cgi#rpm-package>
> >> [2] https://apacheignite.readme.io/docs/getting-started#
> section-rpm-deb-packages-installation  io/docs/getting-started#section-rpm-deb-packages-installation>
> >>
> >> On Tue, May 29, 2018 at 4:47 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org > wrote:
> >> I just tried the Debian install. This is what I got after executing
> "sudo
> >> apt get" command:
> >>
> >>
> >> >
> >> > *E: The repository 'https://apache.org/dist/ignite/deb <
> https://apache.org/dist/ignite/deb>
> >> >  ignite/deb>> apache-ignite Release' does not have a
> >> > Release file.N: Updating from such a repository can't be done
> securely, and
> >> > is therefore disabled by default.N: See apt-secure(8) manpage for
> >> > repository creation and user configuration details.*
> >>
> >>
> >> D.
> >>
> >> On Tue, May 29, 2018 at 4:42 PM, Denis Magda  > wrote:
> >>
> >> > Andrey,
> >> >
> >> > Please help to generate 2.5 release HTML file and add it to Ignite
> website
> >> > SVN. Sergey K and Ilya S. should be able to assist with this.
> >> >
> >> > Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
> >> > can't announce the release and close it without having the docs done.
> >> >
> >> > --
> >> > Denis
> >> >
> >> >
> >> > On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  > wrote:
> >> >
> >> >> Folks,
> >> >>
> >> >> I have released 2.5 documentation on readme.io .
> Also, the downloads page
> >> >> on
> >> >> the website is updated with 2.5 release. Mauricio will work on
> updating
> >> >> the
> >> >> latest doc reference.
> >> >>
> >> >>
> >> >> Andrey,
> >> >>
> >> >> The following still needs attention:
> >> >>
> >> >>1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/ <
> http://ignite.apache.org/releases/2.5.0/>
> >> >>2. Zookeper documentation -
> >> >>https://issues.apache.org/jira/browse/IGNITE-7900 <
> https://issues.apache.org/jira/browse/IGNITE-7900>
> >> >>3. Consistency check utilities docs -
> >> >>https://issues.apache.org/jira/browse/IGNITE-8524 <
> https://issues.apache.org/jira/browse/IGNITE-8524>
> >> >>
> >> >>
> >> >> Thanks,
> >> >> -Prachi
> >> >>
> >> >> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura  > wrote:
> >> >>
> >> >> > Pavel,
> >> >> >
> >> >> > Thanks a lot!
> >> >> >
> >> >> >
> >> >> >
> >> >> > вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn  >:
> >> >> >
> >> >> > > NuGet (.NET) packages pushed:
> >> >> > > https://www.nuget.org/packages?q=Apache.Ignite <
> https://www.nuget.org/packages?q=Apache.Ignite>
> >> >> > >
> >> >> > > On Tue, May 29, 2018 at 8:59 PM, Andrey Gura  >
> >> >> wrote:
> >> >> > >
> >> >> > >> Dmitry,
> >> >> > >>
> >> >> > >> First we should check docker images. Also we are waiting for
> >> >> > >> publishing of artifacts to Maven Central.
> >> >> > >>
> >> >> > >> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
> >> >> > >> mailto:dsetrak...@apache.org>> wrote:
> >> >> > >> >
> >> >> > >> >
> >> >> > >> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura <
> ag...@apache.org >
> >> >> > wrote:
> >> >> > >> >>
> >> >> > >> >> RPM and DEB packages are published to bintray [1] [2]
> >> >> > >> >>
> >> >> > >> >> [1] https://bintray.com/apache/ignite-rpm <
> https://bintray.com/apache/ignite-rpm>
> >> >> > >> >> [2] https://bintray.com/apache/ignite-deb <
> https://bintray.com/apache/ignite-deb>
> >> >> > >> >
> >> >> > >> >
> >> >> > >> > Thanks, Andrey! Can we update the download page on the
> website?
> >> >> > >> >
> >> >> > >> > D.
> >> >> > >> >
> >> >> > >>
> >> >> > >
> >> >> > >
> >> >> >
> >> >>
> >> >
> >> >
> >>
> >
>
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

Docker images for Apache Ignite [1] and Web Console [2] 2.5.0 are uploaded.


[1] https://hub.docker.com/r/apacheignite/ignite/tags
[2] https://hub.docker.com/r/apacheignite/web-console-standalone/tags/



> On 30 May 2018, at 06:55, Petr Ivanov  wrote:
> 
> Instructions for RPM Package Installation (snippet with repository 
> configuration) at ignite.apache.org  are obsolete 
> and should be replaced by apacheignite.readme.io 
>  snippet.
> 
> 
> 
>> On 30 May 2018, at 02:57, Prachi Garg > > wrote:
>> 
>> Peter,
>> 
>> I updated the RPM and DEB description on the downloads page[1] (following 
>> the instructions on the documentation [2]). Please check that the 
>> repositories and installation instructions are up-to-date.
>> 
>> [1] https://ignite.apache.org/download.cgi#rpm-package 
>> 
>> [2] 
>> https://apacheignite.readme.io/docs/getting-started#section-rpm-deb-packages-installation
>>  
>> 
>> 
>> On Tue, May 29, 2018 at 4:47 PM, Dmitriy Setrakyan > > wrote:
>> I just tried the Debian install. This is what I got after executing "sudo
>> apt get" command:
>> 
>> 
>> >
>> > *E: The repository 'https://apache.org/dist/ignite/deb 
>> > 
>> > > 
>> > apache-ignite Release' does not have a
>> > Release file.N: Updating from such a repository can't be done securely, and
>> > is therefore disabled by default.N: See apt-secure(8) manpage for
>> > repository creation and user configuration details.*
>> 
>> 
>> D.
>> 
>> On Tue, May 29, 2018 at 4:42 PM, Denis Magda > > wrote:
>> 
>> > Andrey,
>> >
>> > Please help to generate 2.5 release HTML file and add it to Ignite website
>> > SVN. Sergey K and Ilya S. should be able to assist with this.
>> >
>> > Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
>> > can't announce the release and close it without having the docs done.
>> >
>> > --
>> > Denis
>> >
>> >
>> > On Tue, May 29, 2018 at 4:20 PM, Prachi Garg > > > wrote:
>> >
>> >> Folks,
>> >>
>> >> I have released 2.5 documentation on readme.io . Also, 
>> >> the downloads page
>> >> on
>> >> the website is updated with 2.5 release. Mauricio will work on updating
>> >> the
>> >> latest doc reference.
>> >>
>> >>
>> >> Andrey,
>> >>
>> >> The following still needs attention:
>> >>
>> >>1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/ 
>> >> 
>> >>2. Zookeper documentation -
>> >>https://issues.apache.org/jira/browse/IGNITE-7900 
>> >> 
>> >>3. Consistency check utilities docs -
>> >>https://issues.apache.org/jira/browse/IGNITE-8524 
>> >> 
>> >>
>> >>
>> >> Thanks,
>> >> -Prachi
>> >>
>> >> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura > >> > wrote:
>> >>
>> >> > Pavel,
>> >> >
>> >> > Thanks a lot!
>> >> >
>> >> >
>> >> >
>> >> > вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn > >> > >:
>> >> >
>> >> > > NuGet (.NET) packages pushed:
>> >> > > https://www.nuget.org/packages?q=Apache.Ignite 
>> >> > > 
>> >> > >
>> >> > > On Tue, May 29, 2018 at 8:59 PM, Andrey Gura > >> > > >
>> >> wrote:
>> >> > >
>> >> > >> Dmitry,
>> >> > >>
>> >> > >> First we should check docker images. Also we are waiting for
>> >> > >> publishing of artifacts to Maven Central.
>> >> > >>
>> >> > >> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
>> >> > >> mailto:dsetrak...@apache.org>> wrote:
>> >> > >> >
>> >> > >> >
>> >> > >> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura > >> > >> > >
>> >> > wrote:
>> >> > >> >>
>> >> > >> >> RPM and DEB packages are published to bintray [1] [2]
>> >> > >> >>
>> >> > >> >> [1] https://bintray.com/apache/ignite-rpm 
>> >> > >> >> 
>> >> > >> >> [2] https://bintray.com/apache/ignite-deb 
>> >> > >> >> 
>> >> > >> >
>> >> > >> >
>> >> > >> > Thanks, Andrey! Can we update the download page on the website?
>> >> > >> >
>> >> > >> > D.
>> >> > >> >
>> >> > >>
>> >> > >
>> >> > >
>> >> >
>> >>
>> >
>> >
>> 
> 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

Instructions for RPM Package Installation (snippet with repository 
configuration) at ignite.apache.org are obsolete and should be replaced by 
apacheignite.readme.io snippet.



> On 30 May 2018, at 02:57, Prachi Garg  wrote:
> 
> Peter,
> 
> I updated the RPM and DEB description on the downloads page[1] (following the 
> instructions on the documentation [2]). Please check that the repositories 
> and installation instructions are up-to-date.
> 
> [1] https://ignite.apache.org/download.cgi#rpm-package 
> 
> [2] 
> https://apacheignite.readme.io/docs/getting-started#section-rpm-deb-packages-installation
>  
> 
> 
> On Tue, May 29, 2018 at 4:47 PM, Dmitriy Setrakyan  > wrote:
> I just tried the Debian install. This is what I got after executing "sudo
> apt get" command:
> 
> 
> >
> > *E: The repository 'https://apache.org/dist/ignite/deb 
> > 
> > > 
> > apache-ignite Release' does not have a
> > Release file.N: Updating from such a repository can't be done securely, and
> > is therefore disabled by default.N: See apt-secure(8) manpage for
> > repository creation and user configuration details.*
> 
> 
> D.
> 
> On Tue, May 29, 2018 at 4:42 PM, Denis Magda  > wrote:
> 
> > Andrey,
> >
> > Please help to generate 2.5 release HTML file and add it to Ignite website
> > SVN. Sergey K and Ilya S. should be able to assist with this.
> >
> > Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
> > can't announce the release and close it without having the docs done.
> >
> > --
> > Denis
> >
> >
> > On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  > > wrote:
> >
> >> Folks,
> >>
> >> I have released 2.5 documentation on readme.io . Also, 
> >> the downloads page
> >> on
> >> the website is updated with 2.5 release. Mauricio will work on updating
> >> the
> >> latest doc reference.
> >>
> >>
> >> Andrey,
> >>
> >> The following still needs attention:
> >>
> >>1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/ 
> >> 
> >>2. Zookeper documentation -
> >>https://issues.apache.org/jira/browse/IGNITE-7900 
> >> 
> >>3. Consistency check utilities docs -
> >>https://issues.apache.org/jira/browse/IGNITE-8524 
> >> 
> >>
> >>
> >> Thanks,
> >> -Prachi
> >>
> >> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura  >> > wrote:
> >>
> >> > Pavel,
> >> >
> >> > Thanks a lot!
> >> >
> >> >
> >> >
> >> > вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn  >> > >:
> >> >
> >> > > NuGet (.NET) packages pushed:
> >> > > https://www.nuget.org/packages?q=Apache.Ignite 
> >> > > 
> >> > >
> >> > > On Tue, May 29, 2018 at 8:59 PM, Andrey Gura  >> > > >
> >> wrote:
> >> > >
> >> > >> Dmitry,
> >> > >>
> >> > >> First we should check docker images. Also we are waiting for
> >> > >> publishing of artifacts to Maven Central.
> >> > >>
> >> > >> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
> >> > >> mailto:dsetrak...@apache.org>> wrote:
> >> > >> >
> >> > >> >
> >> > >> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura  >> > >> > >
> >> > wrote:
> >> > >> >>
> >> > >> >> RPM and DEB packages are published to bintray [1] [2]
> >> > >> >>
> >> > >> >> [1] https://bintray.com/apache/ignite-rpm 
> >> > >> >> 
> >> > >> >> [2] https://bintray.com/apache/ignite-deb 
> >> > >> >> 
> >> > >> >
> >> > >> >
> >> > >> > Thanks, Andrey! Can we update the download page on the website?
> >> > >> >
> >> > >> > D.
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >
> >
> 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

I’ve updated instructions correspondingly: it seems that redirect from https to 
https requires more complicated rules, which I will try to introduce in next 
release (2.6).
Currently we should use http, i. e. ignite.list should be look like this: deb 
http://apache.org/dist/ignite/deb/ apache-ignite main



> On 30 May 2018, at 02:47, Dmitriy Setrakyan  wrote:
> 
> I just tried the Debian install. This is what I got after executing "sudo
> apt get" command:
> 
> 
>> 
>> *E: The repository 'https://apache.org/dist/ignite/deb
>>  apache-ignite Release' does not have a
>> Release file.N: Updating from such a repository can't be done securely, and
>> is therefore disabled by default.N: See apt-secure(8) manpage for
>> repository creation and user configuration details.*
> 
> 
> D.
> 
> On Tue, May 29, 2018 at 4:42 PM, Denis Magda  wrote:
> 
>> Andrey,
>> 
>> Please help to generate 2.5 release HTML file and add it to Ignite website
>> SVN. Sergey K and Ilya S. should be able to assist with this.
>> 
>> Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
>> can't announce the release and close it without having the docs done.
>> 
>> --
>> Denis
>> 
>> 
>> On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  wrote:
>> 
>>> Folks,
>>> 
>>> I have released 2.5 documentation on readme.io. Also, the downloads page
>>> on
>>> the website is updated with 2.5 release. Mauricio will work on updating
>>> the
>>> latest doc reference.
>>> 
>>> 
>>> Andrey,
>>> 
>>> The following still needs attention:
>>> 
>>>   1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/
>>>   2. Zookeper documentation -
>>>   https://issues.apache.org/jira/browse/IGNITE-7900
>>>   3. Consistency check utilities docs -
>>>   https://issues.apache.org/jira/browse/IGNITE-8524
>>> 
>>> 
>>> Thanks,
>>> -Prachi
>>> 
>>> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura  wrote:
>>> 
 Pavel,
 
 Thanks a lot!
 
 
 
 вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn :
 
> NuGet (.NET) packages pushed:
> https://www.nuget.org/packages?q=Apache.Ignite
> 
> On Tue, May 29, 2018 at 8:59 PM, Andrey Gura 
>>> wrote:
> 
>> Dmitry,
>> 
>> First we should check docker images. Also we are waiting for
>> publishing of artifacts to Maven Central.
>> 
>> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
>>  wrote:
>>> 
>>> 
>>> On Tue, May 29, 2018 at 9:08 AM, Andrey Gura 
 wrote:
 
 RPM and DEB packages are published to bintray [1] [2]
 
 [1] https://bintray.com/apache/ignite-rpm
 [2] https://bintray.com/apache/ignite-deb
>>> 
>>> 
>>> Thanks, Andrey! Can we update the download page on the website?
>>> 
>>> D.
>>> 
>> 
> 
> 
 
>>> 
>> 
>> 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Prachi Garg]

Peter,

I updated the RPM and DEB description on the downloads page[1] (following
the instructions on the documentation [2]). Please check that the
repositories and installation instructions are up-to-date.

[1] https://ignite.apache.org/download.cgi#rpm-package
[2] https://apacheignite.readme.io/docs/getting-started#
section-rpm-deb-packages-installation


On Tue, May 29, 2018 at 4:47 PM, Dmitriy Setrakyan 
wrote:

> I just tried the Debian install. This is what I got after executing "sudo
> apt get" command:
>
>
> >
> > *E: The repository 'https://apache.org/dist/ignite/deb
> >  apache-ignite Release' does not
> have a
> > Release file.N: Updating from such a repository can't be done securely,
> and
> > is therefore disabled by default.N: See apt-secure(8) manpage for
> > repository creation and user configuration details.*
>
>
> D.
>
> On Tue, May 29, 2018 at 4:42 PM, Denis Magda  wrote:
>
> > Andrey,
> >
> > Please help to generate 2.5 release HTML file and add it to Ignite
> website
> > SVN. Sergey K and Ilya S. should be able to assist with this.
> >
> > Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
> > can't announce the release and close it without having the docs done.
> >
> > --
> > Denis
> >
> >
> > On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  wrote:
> >
> >> Folks,
> >>
> >> I have released 2.5 documentation on readme.io. Also, the downloads
> page
> >> on
> >> the website is updated with 2.5 release. Mauricio will work on updating
> >> the
> >> latest doc reference.
> >>
> >>
> >> Andrey,
> >>
> >> The following still needs attention:
> >>
> >>1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/
> >>2. Zookeper documentation -
> >>https://issues.apache.org/jira/browse/IGNITE-7900
> >>3. Consistency check utilities docs -
> >>https://issues.apache.org/jira/browse/IGNITE-8524
> >>
> >>
> >> Thanks,
> >> -Prachi
> >>
> >> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura  wrote:
> >>
> >> > Pavel,
> >> >
> >> > Thanks a lot!
> >> >
> >> >
> >> >
> >> > вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn :
> >> >
> >> > > NuGet (.NET) packages pushed:
> >> > > https://www.nuget.org/packages?q=Apache.Ignite
> >> > >
> >> > > On Tue, May 29, 2018 at 8:59 PM, Andrey Gura 
> >> wrote:
> >> > >
> >> > >> Dmitry,
> >> > >>
> >> > >> First we should check docker images. Also we are waiting for
> >> > >> publishing of artifacts to Maven Central.
> >> > >>
> >> > >> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
> >> > >>  wrote:
> >> > >> >
> >> > >> >
> >> > >> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura 
> >> > wrote:
> >> > >> >>
> >> > >> >> RPM and DEB packages are published to bintray [1] [2]
> >> > >> >>
> >> > >> >> [1] https://bintray.com/apache/ignite-rpm
> >> > >> >> [2] https://bintray.com/apache/ignite-deb
> >> > >> >
> >> > >> >
> >> > >> > Thanks, Andrey! Can we update the download page on the website?
> >> > >> >
> >> > >> > D.
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

I just tried the Debian install. This is what I got after executing "sudo
apt get" command:


>
> *E: The repository 'https://apache.org/dist/ignite/deb
>  apache-ignite Release' does not have a
> Release file.N: Updating from such a repository can't be done securely, and
> is therefore disabled by default.N: See apt-secure(8) manpage for
> repository creation and user configuration details.*


D.

On Tue, May 29, 2018 at 4:42 PM, Denis Magda  wrote:

> Andrey,
>
> Please help to generate 2.5 release HTML file and add it to Ignite website
> SVN. Sergey K and Ilya S. should be able to assist with this.
>
> Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
> can't announce the release and close it without having the docs done.
>
> --
> Denis
>
>
> On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  wrote:
>
>> Folks,
>>
>> I have released 2.5 documentation on readme.io. Also, the downloads page
>> on
>> the website is updated with 2.5 release. Mauricio will work on updating
>> the
>> latest doc reference.
>>
>>
>> Andrey,
>>
>> The following still needs attention:
>>
>>1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/
>>2. Zookeper documentation -
>>https://issues.apache.org/jira/browse/IGNITE-7900
>>3. Consistency check utilities docs -
>>https://issues.apache.org/jira/browse/IGNITE-8524
>>
>>
>> Thanks,
>> -Prachi
>>
>> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura  wrote:
>>
>> > Pavel,
>> >
>> > Thanks a lot!
>> >
>> >
>> >
>> > вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn :
>> >
>> > > NuGet (.NET) packages pushed:
>> > > https://www.nuget.org/packages?q=Apache.Ignite
>> > >
>> > > On Tue, May 29, 2018 at 8:59 PM, Andrey Gura 
>> wrote:
>> > >
>> > >> Dmitry,
>> > >>
>> > >> First we should check docker images. Also we are waiting for
>> > >> publishing of artifacts to Maven Central.
>> > >>
>> > >> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
>> > >>  wrote:
>> > >> >
>> > >> >
>> > >> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura 
>> > wrote:
>> > >> >>
>> > >> >> RPM and DEB packages are published to bintray [1] [2]
>> > >> >>
>> > >> >> [1] https://bintray.com/apache/ignite-rpm
>> > >> >> [2] https://bintray.com/apache/ignite-deb
>> > >> >
>> > >> >
>> > >> > Thanks, Andrey! Can we update the download page on the website?
>> > >> >
>> > >> > D.
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Denis Magda]

Andrey,

Please help to generate 2.5 release HTML file and add it to Ignite website
SVN. Sergey K and Ilya S. should be able to assist with this.

Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We can't
announce the release and close it without having the docs done.

--
Denis


On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  wrote:

> Folks,
>
> I have released 2.5 documentation on readme.io. Also, the downloads page
> on
> the website is updated with 2.5 release. Mauricio will work on updating the
> latest doc reference.
>
>
> Andrey,
>
> The following still needs attention:
>
>1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/
>2. Zookeper documentation -
>https://issues.apache.org/jira/browse/IGNITE-7900
>3. Consistency check utilities docs -
>https://issues.apache.org/jira/browse/IGNITE-8524
>
>
> Thanks,
> -Prachi
>
> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura  wrote:
>
> > Pavel,
> >
> > Thanks a lot!
> >
> >
> >
> > вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn :
> >
> > > NuGet (.NET) packages pushed:
> > > https://www.nuget.org/packages?q=Apache.Ignite
> > >
> > > On Tue, May 29, 2018 at 8:59 PM, Andrey Gura  wrote:
> > >
> > >> Dmitry,
> > >>
> > >> First we should check docker images. Also we are waiting for
> > >> publishing of artifacts to Maven Central.
> > >>
> > >> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
> > >>  wrote:
> > >> >
> > >> >
> > >> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura 
> > wrote:
> > >> >>
> > >> >> RPM and DEB packages are published to bintray [1] [2]
> > >> >>
> > >> >> [1] https://bintray.com/apache/ignite-rpm
> > >> >> [2] https://bintray.com/apache/ignite-deb
> > >> >
> > >> >
> > >> > Thanks, Andrey! Can we update the download page on the website?
> > >> >
> > >> > D.
> > >> >
> > >>
> > >
> > >
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Andrey Gura]

Pavel,

Thanks a lot!



вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn :

> NuGet (.NET) packages pushed:
> https://www.nuget.org/packages?q=Apache.Ignite
>
> On Tue, May 29, 2018 at 8:59 PM, Andrey Gura  wrote:
>
>> Dmitry,
>>
>> First we should check docker images. Also we are waiting for
>> publishing of artifacts to Maven Central.
>>
>> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
>>  wrote:
>> >
>> >
>> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura  wrote:
>> >>
>> >> RPM and DEB packages are published to bintray [1] [2]
>> >>
>> >> [1] https://bintray.com/apache/ignite-rpm
>> >> [2] https://bintray.com/apache/ignite-deb
>> >
>> >
>> > Thanks, Andrey! Can we update the download page on the website?
>> >
>> > D.
>> >
>>
>
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Pavel Tupitsyn]

NuGet (.NET) packages pushed:
https://www.nuget.org/packages?q=Apache.Ignite

On Tue, May 29, 2018 at 8:59 PM, Andrey Gura  wrote:

> Dmitry,
>
> First we should check docker images. Also we are waiting for
> publishing of artifacts to Maven Central.
>
> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
>  wrote:
> >
> >
> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura  wrote:
> >>
> >> RPM and DEB packages are published to bintray [1] [2]
> >>
> >> [1] https://bintray.com/apache/ignite-rpm
> >> [2] https://bintray.com/apache/ignite-deb
> >
> >
> > Thanks, Andrey! Can we update the download page on the website?
> >
> > D.
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Andrey Gura]

Dmitry,

First we should check docker images. Also we are waiting for
publishing of artifacts to Maven Central.

On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
 wrote:
>
>
> On Tue, May 29, 2018 at 9:08 AM, Andrey Gura  wrote:
>>
>> RPM and DEB packages are published to bintray [1] [2]
>>
>> [1] https://bintray.com/apache/ignite-rpm
>> [2] https://bintray.com/apache/ignite-deb
>
>
> Thanks, Andrey! Can we update the download page on the website?
>
> D.
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Andrey Gura]

RPM and DEB packages are published to bintray [1] [2]

[1] https://bintray.com/apache/ignite-rpm
[2] https://bintray.com/apache/ignite-deb

On Mon, May 28, 2018 at 5:38 PM, Andrey Gura  wrote:
> Igniters,
>
> Apache Ignite 2.5.0 release (RC1) has been accepted.
>
> 4 "+1" binding votes received:
>
> - Alexey Kuznetsov
> - Denis Magda
> - Pavel Tupitsyn
> - Valentin Kulichenko
>
> Vote thread:
>
> *http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-5-0-RC1-td30923.html
> *
>
> Ignite 2.5.0 will be released soon.