Here are the results of checks:
1. Ubuntu. Running Apache Ignite as a stand-alone application works fine, I have successful connections to another Apache Ignite node running under VirtualBox CentOS. NOTE: connectivity started working only after creation of “allow all incoming connections” rule in Windows Defender Firewall. 2. Debian. Running Apache Ignite as a stand-alone application works fine, I have successful connections to another Apache Ignite node running under VirtualBox CentOS. NOTE: in addition to Ubuntu’s NOTE, it is required to install dirmngr program for apt-key be able to download gpg keys over network (this NOTE can be added to documentation + I can add dependency to DEB package in next release). 3. SUSE. Has neither APT no YUM commands. RPM package can be installed via rpm -i command, but I think that this case is out of Apache Ignite 2.5 scope and the question of “officially supported Linux distributions” should be discussed separately. > On 7 Jun 2018, at 08:43, Peter Ivanov <mr.wei...@gmail.com> wrote: > > Understood. Will do today. > > > On Thu, 7 Jun 2018 at 08:43, Dmitriy Setrakyan <dsetrak...@apache.org > <mailto:dsetrak...@apache.org>> wrote: > On Wed, Jun 6, 2018 at 10:40 PM, Peter Ivanov <mr.wei...@gmail.com > <mailto:mr.wei...@gmail.com>> wrote: > > > Dmitriy, > > > > > > What kind of instructions? Systemd or stand-alone? > > I thought we have already agreed that systemd services are not eligible for > > Windows 10 WSL. > > > > So have I to check that Debian, Ubuntu and SUSE environments for Windows 10 > > WSL supports running Apache Ignite installed from packages as a stand-alone > > application? > > > > Yes.
