perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

The one page you mention has not been updated as indicated in the header at the top, but also not sure it would contain anything that would help your case. The remainder of the docs I sent should not mention perfsonarbuoy and are brand new for 4.1.

Thanks,

Andy

On February 6, 2019 at 12:10:16 PM, Pete LG () wrote:

Thank you so much!  I'll mess around and see if I can't get it working.  I go through the example docs you referenced too.

So are there no psconfig auto-config docs on the way?It says at the top that they are not updated, and they still look like the old yaml examples.

pSConfig Auto-Configuration

NOTE: THIS PAGE HAS NOT BEEN UPDATED FOR 4.1. STILL UNDER CONSTRUCTION.

https://docs.perfsonar.net/psconfig_autoconfig.html

I does seem like most of the examples in the main docs still reference perfsonarbuoy and other deprecated configs. I'm starting to finally wrap my head around all the changes.

Regardless of my issues, I appreciate all your support.  You guys are great! 

Thanks,

Pete

Pete LG

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Wednesday, February 6, 2019 8:28 AM, Andrew Lake <> wrote:

Hi,

All the docs for defining a mesh, now part of the pSConfig component, can be found under the heading here: http://docs.perfsonar.net/#managing-multiple-hosts-with-psconfig. It goes into quite a bit of depth on concepts as well as references for the syntax.

Examples can be found under /usr/share/doc/perfsonar/psconfig or you can view them online here: https://github.com/perfsonar/psconfig/tree/master/doc

If you want a really large example, you can see ESnet’s pSConfig template that drives ps-dashboard.es.net here: https://github.com/esnet/esnet-perfsonar-mesh/blob/master/psconfig/esnet-psconfig.json

For running a test once a week, update your psconfig templates “schedules” section with something like the following:

"schedules" : {

      "schedule_once_a_week" : {

         "repeat" : "P1W",

         "slip" : "PT12H",

         "sliprand" : true

      }

}

The “repeat" says you want it to run every week, the “slip” gives it 12 hours of wiggle room if it cannot get a slot exactly 1 week from the previous run, and “sliprand" has it randomly choose a slot in the 12 hour range so everything is not piled at the beginning of the interval. The 12H is arbitrary and probably a bit high, but its good to build in some wiggle room, especially if you have a lot of tests. 

Thanks,

Andy

On February 5, 2019 at 9:14:09 PM, Pete LG () wrote:

I have a request to add a maddash/mesh grid for 'throughput' testing that is only run once a week at a certain time. 

Does anyone know the best way to go about this.  I suggested that we cron off a test and just get an email once a week with iperf results, but they asked for it in maddash form.

Any ideas or suggestions are most welcome.

Also, is there any work being done on the newer docs for maddash/mesh?  From what I can tell, most of the examples are still in yaml, and all the good examples show bwctl versions of tests.  If anyone knows of example out there, I'd love to view them.

Thanks,

Pete

Pete LG

Sent with ProtonMail Secure Email.

--

To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user