perfsonar development work

[Maxim Grigoriev <>]

The circuits are dynamic but the metadata about available PBR clients  and
therefore about available topologies is pretty static. At least this is the
case for Lambda Station. Every new topology or PBR client will require some
preconfiguring on the hardware and this not the very dynamic part. Also, the
netblocks for the end systems are predefined as well since it designed for
the limited number of high data transfer systems and not for the average
user. Even with the much wider audience its not some kind of metadata which
may change every 5 minutes. 
--Maxim 

> -----Original Message-----
> From: Joe Metzger 
> [mailto:]
> Sent: Wednesday, May 14, 2008 12:30 PM
> To: Maxim Grigoriev
> Cc: 
> 
> Subject: Re: [pS-dev] informational call
> 
> Maxim,
> I am not sure I agree with the statement that "metadata is supposed
> to be very static".
> In the dynamic virtual circuit environment, metadata for circuit
> utilization is dynamic.
> 
> But I do think starting to think about this is a good idea!
> 
> --Joe
> 
> 
> On May 14, 2008, at 10:25 AM, Maxim Grigoriev wrote:
> 
> > Hello,
> > There is  a need to provide information about the state of metadata
> > stored
> > at MA. The metadata is supposed to be very static but some services
> > has very
> > substantial md contents.  There is only one informational call -
> > Echo which
> > can be utilized in more wider sense. It gives you information about
> > availability of the service but if it would give you the timestamp
> > of the
> > last time when metadata were updated/changed then any client would
> > be much
> > more effective in  sending MDK request once, caching it and reusing
> > already
> > cached therefore minimizing message exchange.
> > Cheers,
> >           Maxim
> >
> >
> >