perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Fligor, Debbie writes:
       
    > However, I figure out the problem.  After all this time, it was that it 
didn’t like that I’d asked for a 90 second test instead of a 20 second test.  
I had set it to longer than the default to see whether or not a longer test 
would improve the throughput or not. instead, it failed to run.  as kind of a 
last thing before I reinstalled, it occurred to me just to see, and now it’s 
working.  It would be handy if the schedule user interface told you it would 
fail if you make the duration too long.

The limit configuration that ships with the toolkit sets a cap of 60 seconds 
for throughput tests requested by untrusted hosts, which is anything not 
requested on a local interface.  This would mean that even if you're running 
a test between machines on your campus, the far (receiving) end would still 
reject it because it doesn't know to trust the near end.

The "schedule" command can't show rejected tasks because they don't make it 
far enough through the process to have a presence on the schedule.  The 
command-line interface does:

pscheduler task throughput --source tb-el7-prod.ps.dev.internet2.edu --dest 
tb-el7-patch.ps.dev.internet2.edu --duration PT90S
Submitting task...
Failed to post task: Task forbidden by limits:
Hints:
  requester: 12.34.56.78   <--- My home IP address, untrusted
  server: 163.253.37.213
Identified as everybody
Classified as default
Application: Defaults applied to non-friendly hosts   <--- Limits applied to 
untrusted requesters
  Group 1: Limit 'innocuous-tests' failed: Passed but inverted
  Group 1: Limit 'throughput-default-time' failed: Duration not in 
PT5S..PT60S    <--- Time not within limits
  Group 1: Limit 'idleex-default' failed: Test is not 'idleex'
  Group 1: Want any, 0/3 passed, 3/3 failed: FAIL
  Group 1: Failed; stopping here.
  Application FAILS
Proposal does not meet limits 

--Mark