perfSONAR User Q&A and Other Discussion

[Joe Breen <>]

Bruce and Chris,

Thanks very much for validating results and posting.  

Mark,

Thanks very much for the feedback, and explanation.   That info is very helpful.

  --Joe

 

  Univ of Utah Center for High Performance Computing

On Thu, Jun 25, 2020 at 8:10 AM Mark Feit <> wrote:

Joe Breen writes:

 

##############

[chpcadmin@uofu-science-dmz-bandwidth ~]$ pscheduler task throughput --source uofu-ddc-dmz-latency.chpc.utah.edu
Submitting task...
Unable to determine the lead participant: At /schema: 1 is not one of [2]

##############

 

If I swap --source for --dest for the same address, I receive results.  If I explicitly put in the --dest and --source, I receive results:

 

The destination is a required parameter.  The error message is dreadfully bad thanks to the library that parses the JSON schemas for the test specifications.  That’s been remedied in 4.3:

 

$ pscheduler task throughput --source foo.bar.org

Submitting task...

Unable to determine the lead participant: At /: 'dest' is a required property

 

Slightly more detail here:  https://github.com/perfsonar/pscheduler/issues/979.  Issue 427 was a side effect of the BWCTL backward-compatibility code that we nuked from orbit in 4.2.

 

--Mark