perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

The short answer is there isn't currently an easy way to make the GUI do this without changing the _javascript_ of the web interface. Basically the _javascript_ has some cellsize/2 where it should really have cellsize/num_checks. I have created an issue for this: https://github.com/esnet/maddash/issues/11. We'll try to get this fixed in one of the next maddash releases (which should be sometime after the upcoming perfsonar release that is a couple weeks away).

Thanks,

Andy

On Sep 11, 2014, at 9:55 AM, Raphael Dourado <> wrote:

I've faced the same problem and as a workarround I changed the size of the boxes in the /etc/maddash/maddash-webui/etc/config file (to make them more "squarish"), so the empty boxes would be less visible (see the result here: ps.fibre.org.br). 

However, it still doesn't look as good as when the redundant tests are enabled. It would help a lot if we could, like Andrew said, show the box as a full color for only one test.

Best,

Raphael Augusto Dourado.

http://www.cin.ufpe.br/~rasd2/

On Tue, Sep 9, 2014 at 5:10 PM, Andrew Grabowski <> wrote:

Hi Aaron,

A followup to my question. It is understood that the mesh config is smart enough to recognize bidirectional testing. Hence only displaying all the status boxes half full. Is there a way to have the status boxes report only one test? IE report owampLossCheck only without the omwapLossRevCheck.... Commenting one line out in the maddash.yaml still shows the box only half colored.... The idea solution would be to show the box as a full color for only one test.. IE omwapLossRevCheck.

Would there need to be modifications to the maddash-webui.js in /opt/maddash/maddash-webui/lib ???

Thanks in advance for all your help and contributions.

Thank you,

Andrew Grabowski

On Tue, Aug 26, 2014 at 10:13 AM, Aaron Brown <> wrote:

Hey Andrew,

Yep, you’d put it in the mesh config file. You can just put:

“force_bidirectional”: 1,

into the tests in the .json file though if you’d prefer editing that directly.

Cheers,

Aaron

On Aug 26, 2014, at 9:46 AM, Andrew Grabowski <> wrote:

Hi Aaron,

Thanks for the input. If I would like to force the birectional test... Where is the "force_bidirectional" keyword actually put? In the mesh conf file?? I see a potential of putting it in the parameters section of the JSON file...

Thank you,

Andrew Grabowski

On Tue, Aug 26, 2014 at 8:30 AM, Aaron Brown <> wrote:

Hey Andrew,

Unidirectionality is the default behavior to avoid redundant tests. The idea being, if your mesh has hosts A and B in it, and they’re performing tests to each other, if A runs tests from A to B, and from B to A, and B runs tests from A to B, and B to A, it’d double the number of tests that the mesh as a whole is running. If you use MaDDash, it’ll grab the results from the mesh as a whole and display them. If you’d like to have both A and B run both tests, you can set “force_bidirectional” to "1” in the test definition.

Cheers,

Aaron

On Aug 25, 2014, at 6:00 PM, Andrew Grabowski <> wrote:

Hi Raphael and List,

I also have the same problems. I have a full mesh configured and the tests are being reported as not being bi-directional. I thought it might be an issue with the bwctld and owampd limits.. But it is not... 

On top of Raphael's observations,I also notice this on my maddash dashboard. All of the boxes are half empty... (Or half full depending on how you look at it...)

Anyone have any success fixing this?

Thank you,

Andrew Grabowski

On Fri, Aug 15, 2014 at 12:16 PM, Raphael Dourado <> wrote:

Hi!

I have a set of pSPT servers configured to perform OWAMP and BWCTL tests in full-mesh, using the Mesh Configuration tool. 

The problem is that these servers end up performing only unidirectional, reverse-direction tests, as shown in the figure below, taken from on of the nodes (10.132.0.60):

<image.png>

Probably this is just some problem with my configuration files. Please find attached the following files:

• myconf.conf and myconf.json: mesh configuration files
• owmesh.conf: resulting owmesh of one of my nodes, after running the "generate_configuration" script 
• agent_configuration.conf: mesh agent configuration file I'm using on each node

At first I thought it was because I enabled the "skip redundant tests" option on the agent_configuration.conf file, but then I commented it and ran the "generate_configuration" script again, but no changes were made in the owmesh file.

Best,

Raphael Augusto Dourado.