perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Phil Reese writes:

Currently, I have the 5.0.8 Testpoints pointing at the original Maddash
setup. By adding a second 'psconfig remote add <new 5.1 opensearch
Archive server>' a new 5.1.0 Archive host is also showing the data.

I believe this means that the Testpoints are running duplicate tests. 

By subscribing to two separate meshes, they would be.  Even though the tasking is the same between both, pSConfig doesn’t deduplicate between them because they came from two different sources and archives are different.

I'd like to update the Testpoints to 5.1.0, would both the older Maddash
and new Archive grids continue to work?  (I assume the duplicate tests
would continue to be needed, for a short transition time.)

Yes, they would.  We didn’t break backward compatibility in 5.0 or 5.1, so you can still archive to Esmond if that’s your thing.  :-)

pScheduler and, by extension, pSConfig allow multiple archive destinations per task, so there isn’t any need for duplicate measurements or meshes.  Add a second archive to your existing mesh that points at the new (5.1.0) archive and add that archive to your task and/or host entries.  The next time pSConfig on the test points cycles, it will replace the tasks it was running with new ones that archive to both.  When you decommission your older (5.0.8) archive, remove the original archive and all references to it from the mesh and your test point will start running single-archive measurements that get sent to the new one within an hour or two.

--Mark