perfSONAR User Q&A and Other Discussion

[Andrew Grabowski <>]

Hi all,

Anyone have any experience with tweaking or disabling the global lookup service. I am interested in having some private perfsonar nodes not show up in the global catalog (Global Performance Services) if possible. 

So far I was able to deduct the lookup service logic as follows:

How PSONAR nodes send their configs/updates to central ES.NET catalog... Send on port 8090

1. Lookup service uses "SimpleLSBootStrapClientDaemon.conf"

/opt/SimpleLS/bootstrap/etc/SimpleLSBootStrapClientDaemon.conf

This file has the updates interval.. but *no* option to not update... (Maybe update_interval set to 0??

This file points to the:

2. /opt/SimpleLS/bootstrap/etc/hosts-client.yml

The hosts-client.yml has a configured value of "- locator: "http://ps1.es.net:8096/lookup/activehosts.json"";

3. The activehosts.json lists update servers....

*Note - Node configurations seem to be taken from:

"/opt/perfsonar_ps/ls_registration_daemon/etc/ls_registration_daemon.conf"

How PSONAR nodes retrieve Global Services catalog... Get on port 8096

1. /opt/perfsonar_ps/ls_cache_daemon/etc/ls_cache_daemon.conf

2. hints_file  http://www.perfsonar.net/ls.cache.hints

3. The hints file lists servers which have updated catalog

4. Catalog is download every 8 hrs or per configuration in:

/opt/SimpleLS/bootstrap/etc/SimpleLSBootStrapClientDaemon.conf

Are my assumptions of the process correct? Is there a sure way to tweak or stop this?

I am thinking stopping the following services:

/etc/init.d/ls_registration_daemon stop /etc/init.d/ls_cache_daemon stop /etc/init.d/simple_ls_bootstrap_client stop

Removing them from chkconfig... And tweaking the above configuration files (notably SimpleLSBootStrapClientDaemon.conf) would stop this.. Anyone have any experience?

Thank you,

Andrew Grabowski