perfSONAR User Q&A and Other Discussion

["Garnizov, Ivan (RRZE)" <>]

Hi Aaron,

 

Thanks for your reply!

 

It seems that this one does work with 3.4.1. At least by looking at the logs. Lookup Service Directory portal still has no clues about the updates hopefully. I will have to wait for the update before I close this issue for me.

 

In regards to the email from Andy about the 3.4.2 upgrade. Yes we are looking into it, but what I need is a test upgrade based on the deployment we have, before this goes in production. In fact this is what I would like to achieve with the software testing environment.

 

Anyway. I have looked at the documentation Andy sent and there I miss key parameters like the host parameters (location, administrator, etc.) it would be great if pS team can keep an example of the config file there as well, if the one from 3.4.1 is obsoleted. (not sure whom to address this to)

 

Please, I could not also find release notes for the 3.4.2. Is there a way at least to search through updates that have been integrated in the release?

 

Best regards,

Ivan

 

From: Aaron Brown [mailto:]
Sent: Tuesday, April 07, 2015 2:56 PM
To: Andrew Lake
Cc: Garnizov, Ivan (RRZE);
Subject: Re: [perfsonar-user] Multiple Interface configuration - ls_registration_daemon.conf

 

 

On Apr 7, 2015, at 8:47 AM, Andrew Lake <> wrote:

 

 

On Apr 7, 2015, at 7:57 AM, "Garnizov, Ivan (RRZE)" <> wrote:

Dear pS-developers,

 

I have the following case on pS toolkit 3.4.1 boxes with multiple interfaces:

 

Independent of this, i recommend you upgrade to 3.4.2.

 

I am trying to register the services designated for specific interfaces with the LS client, but it totally disregards the config I am applying. Please see the attachements.

I have tried this https://code.google.com/p/perfsonar-ps/source/browse/perfSONAR_PS-LSRegistrationDaemon/etc/ls_registration_daemon.conf?name=3.4

 

For future reference, look at https://github.com/perfsonar/ls-registration-daemon. The Google Code site is no longer used. 

 

 and the

What is worse and this can be seen on the “Lookup Service Directory” portal that some boxes gets registered with the primary interface, some with the secondary and there is no obvious reason behind selecting one or the other as primary interface. Some appear with –owd- in their names, others with –bw-. Please there is no need for explanations here. I just need to configure that and not rely on the system’s choice.

Please note that I have tried with and without the external_interface configuration lines.

 

Could you please assist me in getting it right, so that I am able to define the interfaces for the different types of measurements separately?

I would like also to be able to define a third interface for the web interface of the system or the one that the system gets registered with for access.

 

I would also be happy, if you just point me to the relevant documentation about it.

 

 

You can definitely remove external_address and external_address_if_name. Also try re-formatting the service_templates section as follows:

 

<service_template local_latency_service>

        primary_address          em1

        autodiscover_addresses   1

</service_template>

<service_template local_bandwidth_service>

    primary_address          p1p1

    autodiscover_addresses   1

</service_template>

<service_template local_web_service>

    primary_address          p1p1

    autodiscover_addresses   1

</service_template>

 

Note that none of the above will change what is displayed on your main toolkit page. It will change what is registered in the lookup service though and what people can ultimately see here: http://stats.es.net/ServicesDirectory/. It may take a few hours for this page to update as well. 

 

I think that it should be “primary_interface”, not “primary_address”. I think that’s a typo in the original ls registration daemon configuration.

 

Cheers,

Aaron

 

Thanks,

Andy

 

 

 

 

 

 

 

Best regards,

Ivan

 

 

 

<ls_registration_daemon.conf><ls_registration_daemon.log>