perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Onno Zweers writes:

 

I suppose I need to remove this block:

      …

 But do I also need to remove all references to idleex-default? And to idleex?

 

If you remove idleex-default, just remove references to that.  Idleex may be referenced elsewhere, but those should be fine as they are because they refer to a test by name rather than a removed limit.  I’ll add mention of that to the script.

 

The script says:

> The idleex test is now disallowed for untrusted hosts by the 'allowed-tests' limit.

But there is no 'allowed-tests' mentioned in the limits.conf. Should there be?

 

Ah, yes, sorry…  I was thinking of the new version of the limit configuration when I wrote that.  (I’ll fix that, too.)  Sometimes constant exposure to this stuff can be hazardous.  :-)  There is one, and you’ll find it in the default version we shipped with 5.0:  https://github.com/perfsonar/toolkit/blob/bdc7e7bceb215533beae59a3d45792ca56d26d30/toolkit/perfsonar-toolkit/etc/default_service_configs/pscheduler_limits.conf#L148

 

If your existing configuration is lightly-customized, it may be worth the effort to re-customize the default we ship with 5.0.  We don’t expect to drop support for any more limit types anytime soon, so you shouldn’t have to repeat the exercise.

 

The script also mentions a throughput-default-time test. But the code for that test differs between the limist.conf and the script output. Should I replace the limits.conf version with the script’s version?

 

Correct.  The new one is a drop-in replacement.  Your old one should be the no-longer-supported “test” type and the new one will be the still-supported “jq.”

 

--Mark