perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Tristan Sullivan writes:

 

Thanks, that did the trick.

 

Why this is will become clearer below, but note that adding the archiver plugin to pScheduler will make it accept tasks that archive to Esmond but will not result in measurements being sent to an archive.

 

If you don't mind, could I just clarify something with you about the WLCG test spec, that's confused me since perfsonar 5 was released? If I look at my perfsonar hosts on the PWA interface, they each have the box ticked "use local Esmond MA". I don't see an option for a local http archive.

 

There isn’t one and won’t be.  The box that’s there is a holdover from pre-5.0 that, in my opinion, should have been removed once that could be governed by adding configuration to the local system.  Other than Elmond (more on that below), anything involving Esmond became unsupported as of 5.0.  I’d recommend un-checking that box.

 

PWA is, unfortunately, not as well-maintained as the rest of perfSONAR because the people who’ve worked on it are no longer with us (literally, in one case) and haven’t been for quite some time.   The current iteration is considered to be on its last legs.  We’re in the very early stages of planning its replacement, and that will be the next major change we make in the system.  There’s a lot to be done in modernizing it and we’re not to the point where an estimate of how long it will take is possible.

 

Which I suppose is why psconfig was complaining about not recognising esmond. But the only file actually present in /etc/perfsonar/psconfig/archives.d/ is http_logstash.json.

 

Checking the Local Esmond MA box is checked makes PWA insert hard-wired directives to archive to Esmond on the local host.  Re-adding the plugin keeps pScheduler from choking on the tasking up front but won’t produce successful archiving to a nonexistent Esmond.

 

  Archives in the archives.d directory are read by pSConfig and added to whatever input it gets.  With http_logstash.json installed on the system, archiving to Esmond is redundant.

 

Am I right in thinking that elmond is translating the http archive entries to esmond, and that's why this works? So after 5.3 or whenever esmond finally disappears, the WLCG test spec will have to change?

 

Elmond is a read-only compatibility layer that looks like Esmond at the front but queries OpenSearch behind the scenes.  It was intentionally written that way to encourage people to get rid of their dependencies on Esmond and switch to the new stuff.

 

HTH.

 

--Mark