perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Ahuja, Satish (Exchange) writes:

 

I referred the doc and configured configuration-file named skeleton.json and followed other steps as mentioned. I have attached the json file below. Please let me know if I’m missing something here.

 

There are two problems, one is yours, one is ours:

 

Yours is that the structure of the “groups” section of the config is invalid:

 

     "groups": {

        "example_group_mesh": {

            "type": "mesh",

            "addresses": [

           {"neo-comp-devperf1": "10.224.21.11" },  <-- Invalid Format

           {"neo-comp-devperf2": "10.224.21.12" }   <-- Invalid Format

            ]

        }

    },

 

The addresses array is a list of objects containing a name element, like this:

 

     "groups": {

        "example_group_mesh": {

            "type": "mesh",

            "addresses": [

           { "name": "neo-comp-devperf1" },  <-- Valid Format

           { "name": "neo-comp-devperf2" }   <-- Valid Format

            ]

        }

    },

 

Fixing that will yield a pSConfig file that validates properly.  The structure in the skeleton.json we ship and the documentation (see https://docs.perfsonar.net/psconfig_templates_intro.html#psconfig-templates-intro-example-groups) is correct.

 

 

Ours is that pSConfig doesn’t do proper validation of that part of the input.  The program is forging ahead as if it were valid and gets tripped up by making that assumption.   I’ve written an issue against it (see https://github.com/perfsonar/psconfig/issues/99) and we’ll get it fixed in the current code and the upcoming rewrite.

 

--Mark