Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Lookup Service Disable

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Lookup Service Disable


Chronological Thread 
  • From: Sowmya Balasubramanian <>
  • To: Andrew Grabowski <>
  • Cc: Aaron Brown <>, perfsonar-user <>
  • Subject: Re: [perfsonar-user] Lookup Service Disable
  • Date: Thu, 22 May 2014 09:39:18 -0700

Hi Andrew,

I think it takes a day or two to disappear from the cache.

Sowmya


On Thu, May 22, 2014 at 7:15 AM, Andrew Grabowski <> wrote:
Hi Aaron and Sowmya,

How long before a record is considered stale and removed from the "Global Performance Services" page? Which is derived from:





Thank you,

Andrew Grabowski




On Thu, May 22, 2014 at 10:00 AM, Andrew Grabowski <> wrote:
Hi Aaron,

I noticed the daemon kept getting started and did not know where it was coming from. Thanks for the input!




Thank you,

Andrew Grabowski




On Thu, May 22, 2014 at 8:08 AM, Aaron Brown <> wrote:
Hey Andrew,

You’ll also need to edit “/opt/perfsonar_ps/ls_registration_daemon/etc/ls_registration_daemon.conf”, and add “disabled           1” to it. A service watcher script will automatically restart the ls registration daemon, even if you shut it down.

Cheers,
Aaron

On May 21, 2014, at 7:52 PM, Sowmya Balasubramanian <> wrote:

Hi Andrew,

Your understanding of how nodes get registered is correct. 

If you don't want to register private nodes in the global lookup service, you can stop the ls_registration_deamon and may the bootstrap daemon also(since bootstrap is used only by the ls_registration_daemon). Hosts that were already registered will go away in couple of hours.

The cache daemon doesn't really affect the registration process. So, turning this off is optional.

And, if you would like a "no update" option, you can request this feature by creating a request here: https://code.google.com/p/perfsonar-ps/issues/list.

Hope this helps!

Thanks,
Sowmya





On Wed, May 21, 2014 at 2:25 PM, Andrew Grabowski <> wrote:
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
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









Archive powered by MHonArc 2.6.16.

Top of Page