perfSONAR User Q&A and Other Discussion

[Travis Cook <>]

Howdy, Mark!

Thank you so much for your help! The jq scripting helped resolve the issue, and the data is now displaying the reverse tests in the correct format.

Sincerely,

Travis

On Mon, Nov 29, 2021 at 3:10 PM Mark Feit <> wrote:

	This Message is From an External Sender This message came from outside your organization

 

Travis Cook writes:

 

Node1 can perform tests with the other
perfSONAR nodes in our network, but our perfSONAR devices can't perform tests
on Node1 due to it being protected by its private network's NAT. To account
for this, we ran reverse tests from Node1 to test the connectivity from other
devices to Node1.

…
Is there a way to
separate the data so that the reverse test data will be in column where Node1
is the destination and not the source?

 

The easiest route to that would be to use a transform while archiving those measurements to rearrange the test specification to make it look like a forward measurement.   (How this is done is covered in our jq tutorial here: https://youtu.be/FrT6R75M3BE?t=2678.  If you haven’t used jq, you can start from the beginning.)

 

The jq for that would look something like this:

 

if .test.type == "throughput" and .test.spec.reverse

then

  # Swap the source and destination and make the test look forward

    .test.spec.source as $old_source

  | .test.spec.source = .test.spec.dest

 | .test.spec.dest = $old_source

  | .test.spec.reverse = false

 

else

  # Anything else gets left alone.

  .

end

 

The catch is that your test must have an explicitly-specified source and destination or you’ll end up with archived measurements that have a source but no destination.

 

Hope that helps.

 

--Mark