Apache Ignite 2.6 - Packages roadmap

classic Classic list List threaded Threaded
24 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite 2.6 - Packages roadmap

vveider
Understood. Will do today.


On Thu, 7 Jun 2018 at 08:43, Dmitriy Setrakyan <[hidden email]>
wrote:

> On Wed, Jun 6, 2018 at 10:40 PM, Peter Ivanov <[hidden email]> 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.
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite 2.6 - Packages roadmap

vveider
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 <[hidden email]> wrote:
>
> Understood. Will do today.
>
>
> On Thu, 7 Jun 2018 at 08:43, Dmitriy Setrakyan <[hidden email] <mailto:[hidden email]>> wrote:
> On Wed, Jun 6, 2018 at 10:40 PM, Peter Ivanov <[hidden email] <mailto:[hidden email]>> 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.

Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite 2.6 - Packages roadmap

dmagda
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 <[hidden email]> wrote:

> 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 <[hidden email]> wrote:
> >
> > Understood. Will do today.
> >
> >
> > On Thu, 7 Jun 2018 at 08:43, Dmitriy Setrakyan <[hidden email]
> <mailto:[hidden email]>> wrote:
> > On Wed, Jun 6, 2018 at 10:40 PM, Peter Ivanov <[hidden email]
> <mailto:[hidden email]>> 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.
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite 2.6 - Packages roadmap

vveider
On Fri, 8 Jun 2018 at 00:37, Denis Magda <[hidden email]> 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.
VirtualBox, VMWare, Hyper-V, etc.) everything will work just as on the bare
metal. And no special section is required, otherwise you will end up
describing support of every virtualization technology in the world. I would
suggest we wait for some user and dev experience about using packages in
virtual and containerized environments to better understand what should be
mentioned in documentation and what should not.



>
> 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 <[hidden email]> wrote:
>
> > 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 <[hidden email]> wrote:
> > >
> > > Understood. Will do today.
> > >
> > >
> > > On Thu, 7 Jun 2018 at 08:43, Dmitriy Setrakyan <[hidden email]
> > <mailto:[hidden email]>> wrote:
> > > On Wed, Jun 6, 2018 at 10:40 PM, Peter Ivanov <[hidden email]
> > <mailto:[hidden email]>> 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.
> >
> >
>
12