perfsonar development work

[Nicolas Simar <>]

Hi Maciej, Mark and Matthias,

Maciej Glowiak wrote:
> Hi Nicolas,
>
> Nicolas Simar napisał(a):

> > > I can help and write particular XQuery expression for you if you give 
> > > me XML example of Lookup Information.
> >
> >
> > You mean that we should provide the information that will be 
> > registered in the LS.
>
>
> Yes.

During yesterday conf call with JRA3-4, it was mentioned that at this 
stage, the discovery functionality isn't needed as the visualisation 
tools download all the L2 circuit information from the MA/MPs and stitch 
them together to display them. So it seems that at this stage, the 
functionality isn't needed yet for JRA3-4 application.

It was mentioned that at some point, some scalability issues may be 
encountered and that a discovery mechanism may be needed. However, no 
information explaining when the scalability issues would be encountered 
were given.

Can I ask Mark and Matthias to give an estimate about when their tool 
would need to use a discovery mechanism (because too many MA/MP, because 
new circuits are coming regularly and the number of MP/MAs varies 
greatly, or because too many circuits and a manual file doesn't do it 
anymore).

However, as part of the perfSONAR, we need to cater for other 
visualisation or analysis tool (e.g. build by some NOC for punctual 
troubleshooting). They may have the requirement to discover:
(1) all the e2e circuits from a project, then all the MPs/MAs containing 
the relevant information in respect with those e2e circuits
(2) find out a particular e2e circuits based on the end-institution (and 
maybe the project name)
(3) find out all the information related to an end-to-end circuit (so 
the MAs/MPs where the information is located).

For 3, you need to know the e2e circuit name and you expect to get back, 
by querying the LS, the list of <domain-link, MA/M Paddress> / 
<inter-domain-link, MA/MP address > that are associated with the e2e 
circuit id. (or the <MA/MP address, list of link id>
From there, you can querry the different MA/MP and recompose the e2e 
path, except that at this stage, the MP can will only return you the 
list of all circuits when being queried.

(2) seems to require more information than just the e2e circuit id, the 
domain/inter-domain link id and the MA, MP where this info needs to be 
located. So I would set it aside for the time being.

(1) need one piece of information in addition to the triplet mentioned 
above: the name of the project having requested that circuit. Do we wish 
to add this in the information we plan to register to the LS? (who would 
register it, all the domain? What happens if people write the project 
name differently?)

Matthias and Mark, is it correct that the minimum information that a 
MP/MA would need to register to a LS would need to be <e2e circuit id, 
domain-link, MA/MP address> / <e2e circuit-id, inter-domain-link, MA/MP 
address> and that should be sufficient to be able to retrieve the info 
of a L2 circuit.

Cheers,
--
Nicolas
______________________________________________________________________

Nicolas Simar
Network Engineer

DANTE - www.dante.net

Tel - BE: +32 (0) 4 366 93 49
Tel - UK: +44 (0)1223 371 300
Mobile: +44 (0) 7740 176 883

City House, 126-130 Hills Road
Cambridge CB2 1PQ
UK
_____________________________________________________________________