perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

"Uhl, George D. (GSFC-423.0)[SGT INC]" writes:

 

I’m remembering what Mark Feit said a few months ago:

 

The JSON that goes into a pSConfig test template is the same JSON that the test spec that “pscheduler task --export throughput …” would produce.  Any parameter available for that test (or any other) is available for pSConfig, too.  The throughput test has a “reverse” option (see “pscheduler task throughput --help”) that can be put into a template:

 

{

    "dest": "{% address[1] %}",

    "reverse": true

}

 

This answers the question about defining single-ended tests in a psconfig template.  However will the results of a single-ended test be extractable from Esmond via a maddash dashboard or would I need to use a different Nagios check than the “check_throughput.pl”?

 

The result format for each test is standardized, so single- and dual-ended will be indistinguishable.

 

As I recall, the reverse option in a psconfig defined throughput test did not produce reverse direction throughput results from “check_throughput.pl” because the source and destination test nodes as defined in the test remain unchanged in the reverse test.

 

That’s correct.  The result format doesn’t repeat the test parameters and the Esmond archiver maps the source and destination as-is.

 

There are a couple of ways around it.  One is to give the Esmond archiver a switch that makes it swap the source and destination when the parameters say it was a reverse test.  (Making this a default behavior would violate the principle of least astonishment.)  The other would be to put a jq transform into your archive spec for throughput tests that does the equivalent.  The latter would be a good test bed for this since it can be done with a config change rather than us having to release code before we’re sure it’s a good thing.

 

--Mark