perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi George,

I think Aaron may be out of the office today, but I can confirm that September is in fact still the target for the final release.

Thanks,

Andy

On Aug 13, 2014, at 1:34 PM, "Uhl, George D. (GSFC-423.0)[ARTS]" <> wrote:

Aaron,

Thanks, that would be great if you've got time to spare.  Are you still anticipating September release for the production 3.4 toolkit?  

George

From: Aaron Brown <>
Date: Tuesday, August 12, 2014 5:21 PM
To: George Uhl <>
Cc: perfsonar-user <>, "" <>
Subject: Re: [perfsonar-user] Lookup Service Disable

Hey George,

Unfortunately, there’s not a way to fix that issue without a (minor) code change. Theoretically, the 3.4 version shouldn’t futz with those anymore, leaving everything to work via ‘chkconfig’ like expected. I can give you a patch to apply as a workaround until then though if you’re fine with that.

Cheers,

Aaron

On Aug 12, 2014, at 4:28 PM, Uhl, George D. (GSFC-423.0)[ARTS] <> wrote:

I've been able to disable the LS Registration Daemon but not the LS Cache Daemon.  Turning off the LS Cache daemon in chkconfig is only temporary as the service watcher daemon will start it up eventually.  Is there a way to disable it or not have it do a retrieval from the global service catalog?

There is some irony to this.  I can turn off ls_registration_daemon.conf with chkconfig but after a reboot the daemon is chkconfig'ed "on" yet I can prevent the daemon from running by setting the "disable 1" option in the config file.  Conversely when I turn off  ls_cache_daemon with chkconfig it stays off after reboot but the service watcher will start it up anyway.

Thanks,

George

From: Andrew Grabowski <>
Reply-To: "" <>
Date: Wednesday, May 21, 2014 5:25 PM
To: perfsonar-user <>
Subject: [perfsonar-user] Lookup Service Disable

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