Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Where can I find an updated perfSONAR Mesh example config file?

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Where can I find an updated perfSONAR Mesh example config file?


Chronological Thread 
  • From: Andrew Lake <>
  • To: Jeremy Palmer <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] Where can I find an updated perfSONAR Mesh example config file?
  • Date: Fri, 2 Jan 2015 10:18:12 -0500


On Dec 24, 2014, at 4:22 PM, Jeremy Palmer <> wrote:

FYI, it does appear you can leave the measurement_archive sections out of the mesh config file. It seems to default to "localhost" which is fine if you want to run an MA on each local PS node. My mesh config seems to work just fine without the measurement_archive configs defined and is much cleaner now without all those extra lines.

To clarify, the measurement_archive block is only required if you use the mesh config to generate a MaDDash confiuration. The MaDDash configuration needs the read_url so it know which MA to query. The write_url, which is what used to be used by the regular testing is now ignored because the URL is no longer enough to post data (you also need a username and password). The toolkit defaults to localhost and generates a password for you on install. 


Jeremy Palmer
Senior Network Engineer
ViaWest, Inc.
Office: 720.891.1045
Fax: 303-874-5236
http://www.viawest.com
On 12/19/2014 4:50 PM, Jeremy Palmer wrote:
Sorry, one last question on this.

Looking at sample mesh config located here:
http://docs.perfsonar.net/multi_server_config.html#generating-the-configuration

This example does not have any "measurement_archive" sections included (where the read_url and write_url configs normally live). Is the "measurement_archive" config optional in the latest version, or is this example config incomplete?
Jeremy Palmer
Senior Network Engineer
ViaWest, Inc.
Office: 720.891.1045
Fax: 303-874-5236
http://www.viawest.com
On 12/19/2014 4:34 PM, Jeremy Palmer wrote:
Thank you, exactly what I needed.
It does appear that the example.conf mesh config file included in the RPM is indeed out of date.
I was able to use the current esnet mesh config as a good example:
https://github.com/esnet/esnet-perfsonar-mesh/blob/master/conf/esnet-mesh_config.conf
Jeremy Palmer
Senior Network Engineer
ViaWest, Inc.
Office: 720.891.1045
Fax: 303-874-5236
http://www.viawest.com
On 12/19/2014 4:18 PM, Brian Tierney wrote:

I think this is what you need:

The wiki might be out of date.


On Fri, Dec 19, 2014 at 3:13 PM, Jeremy Palmer <> wrote:
I have some things that are not working correctly on my mesh (traceroute and pingER tests are not working, owamp tests do work tho). Since this is broken on every single one of my mesh hosts (all running toolkit 3.4.1), I'm assuming there is something wrong with my mesh config.

Question: Where can I find a valid example mesh config file?
Per the perfSonar Mesh Config Instructions found here:
https://code.google.com/p/perfsonar-ps/wiki/MeshConfigurationInstallation
There is an example mesh config located at /opt/perfsonar_ps/mesh_config/doc/example.conf and also at:
http://perfsonar-ps.googlecode.com/git/perfSONAR_PS-MeshConfig/doc/example.conf

However the read_url and write_url values in these example files look wrong to me (they look like pre-esmond URLs) so I'm assuming (perhaps incorrectly) that these examples are out of date.

Can someone clarify if the above example mesh config files are valid or not, and if they are not, is there updated documentation somewhere on the recommended way to create a mesh config file in the correct format?

Thanks!

--
Jeremy Palmer
Senior Network Engineer
ViaWest, Inc.
Office: 720.891.1045
Fax: 303-874-5236
http://www.viawest.com



--
Brian Tierney, http://www.es.net/tierney
Energy Sciences Network (ESnet), Berkeley National Lab
http://fasterdata.es.net







  • Re: [perfsonar-user] Where can I find an updated perfSONAR Mesh example config file?, Andrew Lake, 01/02/2015

Archive powered by MHonArc 2.6.16.

Top of Page