perfSONAR User Q&A and Other Discussion

[Hervey Allen <>]

On 2/7/18 2:27 PM, Mark Feit wrote:
> Hervey Allen writes:
>     
>     Mark - Thank you for that example. We were just using the perfSONAR
>     Testpoint bundle during a workshop and wanted to allow UDP tests from
>     hosts on our subnet. If anyone is interested what we did is here:
>     
>     http://prp.ucsd.edu:8080/prpworkshop/materials/limits.conf
>     
>     btw... If this is not the way to do this I'd love to hear that as well.
> 
> If you still want to allow the default things allowed by the limits file we 
> ship with the toolkit, then your change is spot on.  Technically, it allows 
> hosts on your workshop LAN to do anything; you could add UDP throughput 
> only with some additions to the limits and applications.  In a lab or 
> workshop setting, I'd put it wide open for anyone on the local segment as 
> you've done.
> 

Thank you Mark. Much appreciated.

Exactly - for purposes of just local network testing. If we were doing
this across domains, then I'd want more restrictions.

And, to the list, a < 50M bandwidth test is allowed by default. I.E.,
this works with no changes to the limits.conf file:

pscheduler task --tool iperf3 throughput --dest REMOTE_HOST --interval 2
-u --bandwidth 49M

But, we wanted to do:

pscheduler task --tool iperf3 throughput --dest REMOTE_HOST --interval 2
-u --bandwidth 500M

thus, the reason for the change.

> The example I posted for Joon is a bit more locked down and doesn't have 
> any of the additional checks in the toolkit limits file that don't get used.
> 

Thanks!

It's more useful and helps me to understand using the limits.conf file
better.

A side question - Once pScheduler is used by the GUI in Toolkit version
4.1 (is this correct?) - will changes to the limits.conf file take place
via items we tweak in the GUI?

I confess I have not dug through the list to see if this has already
been answered, so apologies if this is an obvious question.

- Hervey

> --Mark
> 
>  
>