perfsonar development work

[Nina Jeliazkova <>]

Jeff, Szymon, All,

Szymon Trocha wrote:
> Jeff,
>
> Jeff W. Boote pisze:
>> It is not clear if this is a discovery issue, or an advertising
>> problem at this point.
>>
>> One aspect of this is that the pS-PS hLS summarization algorithm is
>> advertising too-wide of ranges, and we are working on fixing that.
>> But, we also need to understand better the summarization algorithm of
>> the MDM hLS. It looks suspect that it is advertising /32's.
>
> I think /32 can reflect correctly what is in PIONIER RRD MA. It has
> only single interface in each of these networks in metadata config
> file. So MDM hLS advertises /32s for these two IPs. Or you would
> expect something different here?
>
>> As mentioned before - we need to see the actual messages that the
>> Java gLS-API is sending to debug this. Obviously the discovery query
>> that is being sent from pS-UI is not finding those /32's - and we
>> won't be able to figure out why until we can see the specific query
>> messages it is sending.
>
> Could you Nina help us here?
Perfsonar log attached for the same scenario
(TracerouteTest#testNewLookup() )

        "150.254.185.146",//  (PIONIER)
         "192.5.40.187",
         "212.191.224.74",
         "194.141.0.10"//  (BREN)

You might notice the response from PIONIER LS contains an error code.

Hope this helps,
Nina
>
>> There is no reason to arrange a call until more information is shared
>> asynchronously. All we would be doing is reiterating the already
>> demonstrated problem. For this debugging to work, we will need Mac
>> involved to explain how MDM hLS summarization works, and we will need
>> Michael and/or Nina to explain the queries pS-UI is attempting.
>
> Maciej - can you give us some info on the current summarisation in MDM
> hLS? You used the code provided by I2 as it was or made some changes?
>
> Regards,