1 / 8

common Network Information Service (cNIS)

common Network Information Service (cNIS). Andreas Hanemann, DFN October 12, 2006 Montpellier, France. Motivation for cNIS. Observation that different GN2 activities need network information

kuri
Download Presentation

common Network Information Service (cNIS)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. common Network Information Service (cNIS) Andreas Hanemann, DFN October 12, 2006 Montpellier, France

  2. Motivation for cNIS • Observation that different GN2 activities need network information • JRA1: Network topologies including geographical information needed for CNM, Nemo, VisualperfSONAR (layer 3) • SA3: Network topology and path/routing information needed for path finding and provisioning system (AMPS, layer3) • JRA3: Technology-dependent network topology needed for bandwidth-on-demand activity • JRA4: Database for optical network paths required

  3. cNIS Activity • „common Network Information Service“ (cNIS) is a new activity started in Year 3 • Leader: Anand Patil (DANTE) • Implementors: Marcin Wolski (coordinator), Pawel Gruszczynski, Stanislaw Osinski, Maciel Labedzki (all PSNC) • Coordination with other activities: Anand Patil (DANTE; SA3), Andreas Hanemann (DFN; JRA1), Ulisses Alonso (RedIRIS; JRA1), Angelos Lenis (GRNET, JRA3), Matthias Hamm (DFN; JRA4), Mark Yampolskiy (DFN; JRA4)

  4. Topology Service and cNIS • JRA1‘s Topology Service implemented by Ulisses Alonso will later be replaced by cNIS • During Year 3 the Topology Service will be used • Get whole topology within a Topology Service instance • Get topology of one domain only • Topology Service registers itself with Lookup Service • Registration of clients for updates at the service (optional) • Work on more data input methods for providing topology information • Aim: use of the functionalities and learn for cNIS

  5. Topology Service Architecture NMWG interface Specific data filling method (e.g. script using CDP/LLDP, script using routing protocol information, database output, NAV) for perfSONAR Topology Service Postgres DB : NMWG message

  6. cNIS Architecture: Version at Poznan meeting (end Sep) NMWG/NDL interface SA3 specific Web service API Specific data filling method for perfSONAR Java API Business logic Input API Inputlogic Other input methods (SA3, JRA3,…) Hibernatelayer (API) : NMWG message Data repository : new component

  7. cNIS Architecture: Proposal after perfSONAR workshop SA3 specific output other output perfSONAR AAA/ LS Specific data filling method for perfSONAR Other input methods (SA3, JRA3,…) NMWG/NDL interface (input/output) Java API Constraint logic XML <-> SQL Logic : NMWG message : new component Data repository

  8. cNIS Workplan • 4 Documents: • Use cases and derived requirements • Database schema description (based on previous work) • Architecture description • Interface description • Database schema deliverable (end of December) • cNIS complete design milestone (end of February) • Release of first version (end of May) • NAV installation at DFN (check as data provisioning method)

More Related