Re: lttng-relayd---->lttng-relayd communication

Re: lttng-relayd---->lttng-relayd communication

[Jonathan Rajotte-Julien]

Hi Ramith,

On Thu, Feb 01, 2018 at 12:08:03PM +0000, Ramith Shetty wrote:
> Hi,
> 
> Could you please let us know if we can establish the below setup with the lttng-relayd?

As of today lttng-relayd cannot act as a "client" to another lttng-relayd.

Could you explain a bit more what would be the end goal here?

Cheers

> 
> 
> [target1:session-daemon]-------tracepath---> [target2:lttng-relayd]-------tracepath------>[target3:lttng-relayd]-------->viewer
> 
> 
> Regards,
> Ramith

> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev


-- 
Jonathan Rajotte-Julien
EfficiOS
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: lttng-relayd---->lttng-relayd communication

[Ramith Shetty]

Hi Jonathan,

Thanks for your support.

If we have a setup as below. Can we stream the logs to host SystemA  from TargetB below?

Here TargetA and TargetB are part of a private network. Only TargetA has connectivity to SystemA. We need to stream data from TargetB to SystemA.

[    TargetB----->TargetA    ]------->[SystemA]

Regards,
Ramith

-----Original Message-----
From: Jonathan Rajotte-Julien [mailto:jonathan.rajotte-julien@efficios.com] 
Sent: Saturday, February 3, 2018 2:49 AM
To: Ramith Shetty <rshetty@infinera.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] lttng-relayd---->lttng-relayd communication

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


Hi Ramith,

On Thu, Feb 01, 2018 at 12:08:03PM +0000, Ramith Shetty wrote:
> Hi,
>
> Could you please let us know if we can establish the below setup with the lttng-relayd?

As of today lttng-relayd cannot act as a "client" to another lttng-relayd.

Could you explain a bit more what would be the end goal here?

Cheers

>
>
> [target1:session-daemon]-------tracepath---> [target2:lttng-relayd]-------tracepath------>[target3:lttng-relayd]-------->viewer
>
>
> Regards,
> Ramith

> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev


--
Jonathan Rajotte-Julien
EfficiOS
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: lttng-relayd---->lttng-relayd communication

[Jonathan Rajotte-Julien]

Hi,

On Sat, Feb 03, 2018 at 05:08:25AM +0000, Ramith Shetty wrote:
> 
> If we have a setup as below. Can we stream the logs to host SystemA  from TargetB below?
> 
> Here TargetA and TargetB are part of a private network. Only TargetA has connectivity to SystemA. We need to stream data from TargetB to SystemA.
> 
> [    TargetB----->TargetA    ]------->[SystemA]

This seems like a perfect match for ssh tunneling via TargetA.

On System A:
    Start lttng-relayd.
      The default ports are as follow:
        Control port: tcp://0.0.0.0:5342
        Data port: tcp://0.0.0.0:5343
        Live port: tcp://localhost:5344

On Target B:
    Create a ssh tunnel via Target A:
      ssh -nNT -L 9990:SystemA:5342 -L 9991:SystemA:5343 targetA

    Setup live session correctly:
      lttng create --set-url net://localhost:9990:9991 --live
      lttng ...

At that point you should be able to attach locally a babeltrace to SystemA.
Note that the ssh tunnel needs to be up for everything to work. It might require
some adjustment depending on your network configuration etc.

I tested it locally with 3 VMs and everything seems to work fine.

Cheers
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: lttng-relayd---->lttng-relayd communication

[Jesper Derehag]

Or netcat if you want to skip the encryption overhead.

/Jesper

________________________________________
Från: lttng-dev <lttng-dev-bounces@lists.lttng.org> för Jonathan Rajotte-Julien <jonathan.rajotte-julien@efficios.com>
Skickat: den 3 februari 2018 19:11
Till: Ramith Shetty
Kopia: lttng-dev@lists.lttng.org
Ämne: Re: [lttng-dev] lttng-relayd---->lttng-relayd communication

Hi,

On Sat, Feb 03, 2018 at 05:08:25AM +0000, Ramith Shetty wrote:
>
> If we have a setup as below. Can we stream the logs to host SystemA  from TargetB below?
>
> Here TargetA and TargetB are part of a private network. Only TargetA has connectivity to SystemA. We need to stream data from TargetB to SystemA.
>
> [    TargetB----->TargetA    ]------->[SystemA]

This seems like a perfect match for ssh tunneling via TargetA.

On System A:
    Start lttng-relayd.
      The default ports are as follow:
        Control port: tcp://0.0.0.0:5342
        Data port: tcp://0.0.0.0:5343
        Live port: tcp://localhost:5344

On Target B:
    Create a ssh tunnel via Target A:
      ssh -nNT -L 9990:SystemA:5342 -L 9991:SystemA:5343 targetA

    Setup live session correctly:
      lttng create --set-url net://localhost:9990:9991 --live
      lttng ...

At that point you should be able to attach locally a babeltrace to SystemA.
Note that the ssh tunnel needs to be up for everything to work. It might require
some adjustment depending on your network configuration etc.

I tested it locally with 3 VMs and everything seems to work fine.

Cheers
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: lttng-relayd---->lttng-relayd communication

[Jonathan Rajotte-Julien]

On Mon, Feb 05, 2018 at 04:02:13PM +0000, Jesper Derehag wrote:
> Or netcat if you want to skip the encryption overhead.

Good point!

Also for a more permanent installation I think one could use IPtables.
Unfortunately, I do not use IPtables enough to give advices on that end.

Cheers

> 
> /Jesper
> 
> ________________________________________
> Från: lttng-dev <lttng-dev-bounces@lists.lttng.org> för Jonathan Rajotte-Julien <jonathan.rajotte-julien@efficios.com>
> Skickat: den 3 februari 2018 19:11
> Till: Ramith Shetty
> Kopia: lttng-dev@lists.lttng.org
> Ämne: Re: [lttng-dev] lttng-relayd---->lttng-relayd communication
> 
> Hi,
> 
> On Sat, Feb 03, 2018 at 05:08:25AM +0000, Ramith Shetty wrote:
> >
> > If we have a setup as below. Can we stream the logs to host SystemA  from TargetB below?
> >
> > Here TargetA and TargetB are part of a private network. Only TargetA has connectivity to SystemA. We need to stream data from TargetB to SystemA.
> >
> > [    TargetB----->TargetA    ]------->[SystemA]
> 
> This seems like a perfect match for ssh tunneling via TargetA.
> 
> On System A:
>     Start lttng-relayd.
>       The default ports are as follow:
>         Control port: tcp://0.0.0.0:5342
>         Data port: tcp://0.0.0.0:5343
>         Live port: tcp://localhost:5344
> 
> On Target B:
>     Create a ssh tunnel via Target A:
>       ssh -nNT -L 9990:SystemA:5342 -L 9991:SystemA:5343 targetA
> 
>     Setup live session correctly:
>       lttng create --set-url net://localhost:9990:9991 --live
>       lttng ...
> 
> At that point you should be able to attach locally a babeltrace to SystemA.
> Note that the ssh tunnel needs to be up for everything to work. It might require
> some adjustment depending on your network configuration etc.
> 
> I tested it locally with 3 VMs and everything seems to work fine.
> 
> Cheers
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Jonathan Rajotte-Julien
EfficiOS
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: lttng-relayd---->lttng-relayd communication

[Ramith Shetty]

Thanks a lot Jonathan and Jesper for your support.

Regards,
Ramith

-----Original Message-----
From: Jonathan Rajotte-Julien [mailto:jonathan.rajotte-julien@efficios.com] 
Sent: Monday, February 5, 2018 9:51 PM
To: Jesper Derehag <jderehag@hotmail.com>
Cc: Ramith Shetty <rshetty@infinera.com>; lttng-dev@lists.lttng.org
Subject: Re: SV: [lttng-dev] lttng-relayd---->lttng-relayd communication

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


On Mon, Feb 05, 2018 at 04:02:13PM +0000, Jesper Derehag wrote:
> Or netcat if you want to skip the encryption overhead.

Good point!

Also for a more permanent installation I think one could use IPtables.
Unfortunately, I do not use IPtables enough to give advices on that end.

Cheers

>
> /Jesper
>
> ________________________________________
> Från: lttng-dev <lttng-dev-bounces@lists.lttng.org> för Jonathan 
> Rajotte-Julien <jonathan.rajotte-julien@efficios.com>
> Skickat: den 3 februari 2018 19:11
> Till: Ramith Shetty
> Kopia: lttng-dev@lists.lttng.org
> Ämne: Re: [lttng-dev] lttng-relayd---->lttng-relayd communication
>
> Hi,
>
> On Sat, Feb 03, 2018 at 05:08:25AM +0000, Ramith Shetty wrote:
> >
> > If we have a setup as below. Can we stream the logs to host SystemA  from TargetB below?
> >
> > Here TargetA and TargetB are part of a private network. Only TargetA has connectivity to SystemA. We need to stream data from TargetB to SystemA.
> >
> > [    TargetB----->TargetA    ]------->[SystemA]
>
> This seems like a perfect match for ssh tunneling via TargetA.
>
> On System A:
>     Start lttng-relayd.
>       The default ports are as follow:
>         Control port: tcp://0.0.0.0:5342
>         Data port: tcp://0.0.0.0:5343
>         Live port: tcp://localhost:5344
>
> On Target B:
>     Create a ssh tunnel via Target A:
>       ssh -nNT -L 9990:SystemA:5342 -L 9991:SystemA:5343 targetA
>
>     Setup live session correctly:
>       lttng create --set-url net://localhost:9990:9991 --live
>       lttng ...
>
> At that point you should be able to attach locally a babeltrace to SystemA.
> Note that the ssh tunnel needs to be up for everything to work. It 
> might require some adjustment depending on your network configuration etc.
>
> I tested it locally with 3 VMs and everything seems to work fine.
>
> Cheers
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

--
Jonathan Rajotte-Julien
EfficiOS
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

lttng-relayd---->lttng-relayd communication

[Ramith Shetty]

[-- Attachment #1.1: Type: text/plain, Size: 251 bytes --]

Hi,

Could you please let us know if we can establish the below setup with the lttng-relayd?


[target1:session-daemon]-------tracepath---> [target2:lttng-relayd]-------tracepath------>[target3:lttng-relayd]-------->viewer


Regards,
Ramith

[-- Attachment #1.2: Type: text/html, Size: 2452 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev