perfSONAR User Q&A and Other Discussion

[Alan Whinery <>]

OK, the GUI initially creates the test, but if I edit
regular_testing.conf and add powstream tests, eventually, they get
automatically added as target hosts in "perfSONAR Toolkit Default
Traceroute Test". I believe I stayed out of the GUI and that still
happened.

As far as "it shouldn't add new hosts" I believe it did, under 3.4.1.
Obviously I need a controlled experiment. As it happens I have a few
3.4.2 machines sitting around, as I've been practicing PXE installs.

I actually like the automatic adding of traceroute test targets, but I
don't want to have human/GUI intervention be a part of automatically
adding tests.

On 4/1/2015 8:39 AM, Aaron Brown wrote:
> Hey Alan,
>
> I sent a reply that it may have gotten wedged somehow:
>
>> Hey Alan,
>>
>> The Regular Testing GUI does that, so my guess is that you did a “Save” 
>> with it at some point. Theoretically, it shouldn’t add another traceroute 
>> test to a given host if you’ve got one already defined.
>>
>> Cheers,
>> Aaron
>
>
>> On Apr 1, 2015, at 2:27 PM, Alan Whinery 
>> <>
>>  wrote:
>>
>> On 3/27/2015 11:13 AM, Alan Whinery wrote:
>>> I notice that when I add a powstream test to my
>>> /opt/perfsonar_ps/regular_testing/etc/regular_testing.conf and re-start,
>>> some time after, perhaps not immediately, the testee in the test that I
>>> added gets inserted into the "perfSONAR Toolkit Default Traceroute
>>> Test". I'm curious to know what criteria cause what entity to add that
>>> host to the traceroute test.
>>>
>>> I had been assuming that if I edited the file, I needed to add my own
>>> traceroute test, but now I've got several per endpoint...
>>>
>> Still wondering about this...