Re: Apache Ignite 2.6 - Packages roadmap

On Fri, 8 Jun 2018 at 00:37, Denis Magda wrote: > Petr, > > Am I correct that all 3 points were tested for VirtualBox? No, it was tested for Windows 10 WSL. I would > introduce a documentation sub-section for VirtualBox then. As I said previously — under “honest” virtual environments (i. e.

Re: Apache Ignite 2.6 - Packages roadmap

Petr, Am I correct that all 3 points were tested for VirtualBox? I would introduce a documentation sub-section for VirtualBox then. As for the Windows WSL, did you have a change to look into it? -- Denis On Thu, Jun 7, 2018 at 2:42 AM, Petr Ivanov wrote: > Here are the results of checks: > >

Re: Apache Ignite 2.6 - Packages roadmap

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

Re: Apache Ignite 2.6 - Packages roadmap

Understood. Will do today. On Thu, 7 Jun 2018 at 08:43, Dmitriy Setrakyan wrote: > On Wed, Jun 6, 2018 at 10:40 PM, Peter Ivanov wrote: > > > Dmitriy, > > > > > > What kind of instructions? Systemd or stand-alone? > > I thought we have already agreed that systemd services are not eligible > fo

Re: Apache Ignite 2.6 - Packages roadmap

On Wed, Jun 6, 2018 at 10:40 PM, Peter Ivanov 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

Re: Apache Ignite 2.6 - Packages roadmap

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 stan

Re: Apache Ignite 2.6 - Packages roadmap

Petr, I confirm that Ignite starts for me from a downloadable archive on Ubuntu under Windows 10. I would actually recommend that instead of discussing here how running Linux in Windows 10 is not a valid use case, we should probably just test it and fix it. Can you please try running your instruc

Re: Apache Ignite 2.6 - Packages roadmap

Denis, The question “will Apache Ignite start under Windows 10 WSL Ubuntu from packages?” is the same as “will Apache Ignite start under Windows 10 WSL Ubuntu from binary archive?” concerning running Apache Ignite as standalone service (from ignite.sh). Did anyone from community tried running Apa

Re: Apache Ignite 2.6 - Packages roadmap

Stop. I've finally figured out what kind of environment Dmitriy is talking about. Imagine a Windows developer who needs to run something under Linux on his machine. He/she would go for VirtualBox and Parallels Desktop. Hope, we don't have any doubts that it needs to be possible to install Ignite v

Re: Apache Ignite 2.6 - Packages roadmap

Denis, I’ll look into it On Wed, 6 Jun 2018 at 19:17, Denis Magda wrote: > I suggest us trying to move the conversation in this direction. > > Is it possible to install and run Cassandra using DEB from that emulation > environment on Windows? If yes, then we should spend our efforts adopting

Re: Apache Ignite 2.6 - Packages roadmap

I suggest us trying to move the conversation in this direction. Is it possible to install and run Cassandra using DEB from that emulation environment on Windows? If yes, then we should spend our efforts adopting Ignite for the environment. Otherwise, we should skip it for now. -- Denis On Tue, J

Re: Apache Ignite 2.6 - Packages roadmap

On Tue, Jun 5, 2018 at 12:12 PM, Petr Ivanov wrote: > Dmitriy, > > > I will check soon and see what can be done to overcome this. > Thanks! Looking forward to your feedback. > > Yet, I still doubt that running Apache Ignite packed in DEB under Windows > 10 WSL Ubuntu is a plausible user case.

Re: Apache Ignite 2.6 - Packages roadmap

On Tue, Jun 5, 2018 at 1:54 PM, Sergey Kozlov wrote: > Hi > > For Windows users we should provide Windows installer (.exe or .msi) that > set up and install AI as service. But that task requires significant > efforts and makes sense to start in that way after stabilization DEB/RPM > architecture

Re: Apache Ignite 2.6 - Packages roadmap

Hi For Windows users we should provide Windows installer (.exe or .msi) that set up and install AI as service. But that task requires significant efforts and makes sense to start in that way after stabilization DEB/RPM architecture On Tue, Jun 5, 2018 at 10:12 PM, Petr Ivanov wrote: > Dmitriy,

Re: Apache Ignite 2.6 - Packages roadmap

Dmitriy, I will check soon and see what can be done to overcome this. Yet, I still doubt that running Apache Ignite packed in DEB under Windows 10 WSL Ubuntu is a plausible user case. To be honest, I doubt that our packages are being downloaded and installed at all... > On 5 Jun 2018, at 2

Re: Apache Ignite 2.6 - Packages roadmap

Petr, Were you ever able to successfully start an Ignite node from Ubuntu on Windows 10? It looks like a node startup hangs for me. Here is the message I am getting when bringing up a node in verbose mode: *[18:24:27,778][WARNING][main][TcpDiscoverySpi] Node has not been connected > to topology

Re: Apache Ignite 2.6 - Packages roadmap

Dmitriy, I’ve replaced root user requirement with ignite user requirement. It is necessary because after installation ignite user receive all Apache Ignite work directories ownership (to be able to write woking files there). In fact, Apache Ignite as a service is configured to run just under th

Re: Apache Ignite 2.6 - Packages roadmap

Petr, I think it was Denis who reworked the documentation. In any case, if you see something lacking you can fix it. Just to clarify, are you suggesting that you don't have to be root to run the Ignite process after the package install? D. On Mon, Jun 4, 2018 at 9:31 PM, Petr Ivanov wrote: >

Re: Apache Ignite 2.6 - Packages roadmap

> 1. Remove the requirement to run Ignite scripts as root. This will be a > huge No in most environment and we should fix it. > There is already a ticket for point 1: > https://issues.apache.org/jira/browse/IGNITE-8695 > 1. I am not the au

Re: Apache Ignite 2.6 - Packages roadmap

There is already a ticket for point 1: https://issues.apache.org/jira/browse/IGNITE-8695 -- Denis On Mon, Jun 4, 2018 at 2:40 PM, Dmitriy Setrakyan wrote: > Here is my list: > >1. Remove the requirement to run Ignite scripts as root. This will be a >huge No in most environment and we sh

Re: Apache Ignite 2.6 - Packages roadmap

Here is my list: 1. Remove the requirement to run Ignite scripts as root. This will be a huge No in most environment and we should fix it. 2. Add Ignite "bin" folder to PATH, so all Ignite scripts will be executable without specifying the whole path name (not sure if it is already d

Re: Apache Ignite 2.6 - Packages roadmap

Petr, I do remember the multi-package approach was suggested as a solution to trim down the size of the binary that is hosted by ASF. Since now the binaries are hosted in Bintray, do we still have that issue? If it's fine to preload and keep big binaries in Bintray then I would suggest us to postp

Re: Apache Ignite 2.6 - Packages roadmap

Hello! Here's my list of improvements for AI package: - Make sqlline.sh callable from command line (PATH). E.g. symlink it as /usr/bin/sqlline-ignite, make sure it works. - Fix control.sh and visor-cmd, expose them too. - Allow specifying of JDK implementation and JDK arguments for Apache Ignite s

Apache Ignite 2.6 - Packages roadmap

Igniters! Apache Ignite 2.5 is released and for the first time in it’s history is shipped in both RPM and DEB packages. And, I think, it is time to discuss the future roadmap of Apache Ignite in Linux packages initiative. For the first “feature” I would suggest splitting of the packages on sma