Provide path discovery in LHCONE

[fno2010]

Some related references:

• https://twiki.cern.ch/twiki/bin/view/LHCONE/WebHome
• https://twiki.cern.ch/twiki/bin/view/LHCONE/LhcOneAup
• https://twiki.cern.ch/twiki/bin/view/LHCONE/LhcOneVRF#Connected_Sites
• https://indico.cern.ch/event/1110783/contributions/4689271/attachments/2418010/4138250/LHCOPNE-20220330-48-CRIC-database.pdf
• https://wlcg-cric.cern.ch/api/core/rcsite/query/?json
• http://lhcone-lg.cern.ch/

[fno2010]

Some first-step thoughts: https://docs.google.com/document/d/1wSy4NlQ-CuYUbmCxVG1ny60SMlR1EFnYMrgqgZWpkls/edit?usp=sharing

[fno2010]

A network automation tool that we can use to get information from routers: https://napalm.readthedocs.io/en/latest/

[fno2010]

So far, we support two kinds of data sources:

• Looking Glass
• CRIC

However, looking glass has no standard. That means that

1. different looking glass servers may provide data using different formats;
2. different looking glass servers may even provide different functionalities.

One option is to write different agents for each specific looking glass server. Another one is to leverage some other standard approaches. Internet Routing Registry (IRR) can be one of the options. And we can leverage its standard data format, i.e., RPSL (https://www.ietf.org/rfc/rfc2622.txt)

Tools may be useful:

• https://github.com/irrdnet/irrd