perfSONAR User Q&A and Other Discussion

["Nickless, Bill" <>]

Hi Andy,

I have the toolkit installed on computers within a walled garden / private 
internet.  They can't reach the public Internet (and probably never will), so 
they cannot register with the existing gLS.  

This wouldn't be a problem, except that scheduled bandwidth tests won't run 
between these walled garden / private internet toolkit instances.  I'm not 
sure, but I'm afraid the scheduled bandwidth tests won't run until these 
walled garden / private toolkit instances are registered with a gLS.

Evidently I'm actually asking three questions--

1.  Do I need a gLS to run scheduled bandwidth tests within a walled garden / 
private internet?

2.  If so, how can I establish a gLS within my walled garden / private 
internet?

3.  Alternatively, will the problem in #1 go away with the new lookup service?

Sorry for the confusion!

Bill Nickless

> -----Original Message-----
> From: Andy Lake 
> [mailto:]
> Sent: Wednesday, January 02, 2013 1:26 PM
> To: Nickless, Bill
> Cc: 
> ''
> Subject: Re: [perfsonar-user] Global Lookup Service configuration on a
> private internet?
> 
> Hi Bill,
> 
> The standard toolkit currently comes equipped with a home lookup service
> (hLS) but not a gLS which is a slightly different configuration. I'm
> also not entirely sure it would solve your problem anyways. To backup,
> what are you trying to accomplish? Do you have a toolkit installed and
> just want to get your services registered somewhere that's publicly
> accessible to others that want to test to you? or do you have something
> else in mind? It's also worth noting we are just a couple weeks away
> from rolling out an early version of a complete replacement for the
> lookup service, so I'd hate for you to do too much work to get things
> setup as the currently stand.
> 
> Thanks,
> Andy
> 
> On Jan 2, 2013, at 3:04 PM, "Nickless, Bill" 
> <>
> wrote:
> 
> > Hi Andy,
> >
> > Thank you for your quick response.
> >
> > Unfortunately the (small-I) internet hosts are prohibited by
> technology and policy from accessing any of the hosts at
> http://www.perfsonar.net/gls.root.hints , and I don't have the authority
> to change that fact.
> >
> > So I guess I'm going to have to set up my own gLS on that internet.
> Is that task as simple as publishing a gls.root.hints file with pointers
> to otherwise standard perfSONAR Toolkit hosts, or do I need to set up
> additional infrastructure?
> >
> > Thanks again and best regards,
> >
> > Bill Nickless
> >
> >> -----Original Message-----
> >> From: Andy Lake 
> >> [mailto:]
> >> Sent: Wednesday, January 02, 2013 11:55 AM
> >> To: Nickless, Bill
> >> Cc: 
> >> ''
> >> Subject: Re: [perfsonar-user] Global Lookup Service configuration on
> a
> >> private internet?
> >>
> >> Hi Bill,
> >>
> >> You should not need any special configuration to access the hosts in
> the
> >> file. I can reach the one's that are running from Comcast-land so
> really
> >> anywhere should be able to access them. The current gLS has a number
> of
> >> stability issues and as such will be getting replaced in the very
> near
> >> future. Its quite possible some will not respond because they are in
> a
> >> bad state. Just doing some quick tests the ESnet and RNP instances
> all
> >> seem to respond.
> >>
> >> Thanks,
> >> Andy
> >>
> >>
> >>
> >>
> >> On Jan 2, 2013, at 2:46 PM, "Nickless, Bill" 
> >> <>
> >> wrote:
> >>
> >>> Good morning,
> >>>
> >>> I'm responsible for monitoring performance on a private (small-I)
> >> internet.  Hosts on this internet cannot resolve the DNS names nor
> >> establish TCP/IP connections to any of the hosts listed at
> >> http://www.perfsonar.net/gls.root.hints .
> >>>
> >>> Do I need to do any special configuration on the perfSONAR instances
> >> listed in the gls.root.hints file on the private internet?  Or is the
> >> bog standard perfSONAR Toolkit Lookup Service configuration also
> >> suitable for being a root server?
> >>>
> >>> Thank you and best regards,
> >>>
> >>> Bill Nickless
> >>> Pacific Northwest National Laboratory
> >>> +1 509 713 2455
> >>>
> >>>
> >