Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Research on Networks presentation at SURFnet, November 8th 2010


Published on

  • Be the first to comment

  • Be the first to like this

Research on Networks presentation at SURFnet, November 8th 2010

  1. 1. Interoperability of Lightpath Provisioning Systems in a Multi-domain Testbed Fred Wan Paola Grosso Cees de Laat University of Amsterdam System and Network Engineering research group
  2. 2. Overview• Background – E-science and dynamic resource allocation and provisioning – GLIF, NRENs and GOLEs – Lightpaths/deterministic paths – Network Resource Provisioning Systems (NRPSs)• Network service- and control-planes – General NRPS architecture – Multi-domain NRPSs: Chain versus Tree model – Harmony, Fenius, IDC – Interoperability requirements – Automated GOLE pilot, Fenius – SC10 demo• Conclusions and future work
  3. 3. Dynamic Resource Allocation and Provisioning• National Research and Education Networks (NRENs) facilitate data transport between – compute resources – scientific instruments – data-storage – distributed measurement equipment• Dynamic resource allocation: The network as a dynamic resource• Efforts to combine international e-science resources: – EU projects Phosphorus (finished), Geysers (current), FEDERICA, Panlab, FIRE, etc. – US projects, e.g. GENI• Problem: how to combine, allocate and control the inter-NREN network?• Current status: manually by NREN NOCs• Goal: automate request processing for network connections (advance reservation and provisioning)
  4. 4. GLIF and GOLEs• Global Lambda Integrated Facility• Virtual international organization promoting paradigm of lambda networking• Collaborative initiative among worldwide NRENs, consortia and institutions• World-scale Lambda based Laboratory to facilitate application and middleware development• GOLE – GLIF Open Lightpath Exchange – Peering point for lightpaths – Global model: MANLAN, NetherLight, UKLight, Starlight, NorthernLight, …• Open anyone can bring lambdas – Lambda owner controls port – GOLE owner makes cross connects happen – Limitations only in technology
  5. 5. GLIF: Global Lambda Integrated Facility
  6. 6. GLIF EuropeGlobal Open Lightpath Exchanges (GOLEs):NetherLightNorthernLightCERNLight
  7. 7. Netherlight GOLE: Global Open Lightpath Exchange
  8. 8. Connection requirements and Control• Overprovisioning best-effort networks does not work• Requirements: – deterministic bandwidth – point to point connection – capacity and timeliness guarantees when transferring large chunks asynchronously – Bandwidth guarantees and jitter-free transport when transferring synchronously• Available technologies: GMPLS, WDM, TDM (layer 1) and PBT (layer 2)• TDM: provision a number of VC-4 (or other capacity) channels by creating cross connects on the switches comprising the path• Configuration: CLI, TL1, SNMP• Integrate NEs into workflow: Network Resource Provisioning Systems (NRPSs) so lightpaths can be reserved in advance• General design abstracted from various implementations
  9. 9. General inter-domain NSP design and implementations Single-domain NRPSs: Multi-domain NSP: OSCARS & DRAGON (IDC) IDC Internet2, ESnet
  10. 10. Inter-domain path reservation and provisioning: Two models• Federated model: uniform request interface, topology exchange and event notification among peers
  11. 11. Legend: East / West interfaces Grid Reservation service interface ---------------------------------------------------------- Middleware Reservation WS: Topology service interface • Availability Request • Create Reservation Request Request for end-to-end resource provisioning Network Service Plane • Query Reservation(s) Request • Activate Reservation Request Database Topology information • Cancel Reservation Request NRPS address information • Status Request Topology NRPS Manager Path Topology WS: Computer Service • Add domain Reservation service client • Delete domain Interoperability • Edit domain Resource reservations layer • Retrieve domain • Add Endpoints • Delete Endpoint Reservation Topology service client Reservation Topology service client Reservation Topology service client • Edit Endpoints • Retrieve Endpoints Adapter Adapter Adapter • Add Link ARGON driver UCLP driver DRAC driver • Delete Link • Edit Link • Retrieve Link ARGON domain UCLP domain DRAC domainCentralized model: unification of request interface through an adaptationlayer, overlay topology and central event management
  12. 12. Automated GOLE pilot • 16 Networks/GOLEs • NRPSs: IDC, ARGIA, DRAC, G-Lambda, AutoBAHN • Central controller: Fenius • Fenius: simpler version of Harmony
  13. 13. SC09 setup (UvA view)• Dynamic lightpath provisioning between GOLEs/Networks• Each domain: perfSONAR deployed• Demo: light turns green when connections are made
  14. 14. Pinger matrix
  15. 15. Example Scenario: UvA-StarLight • Fenius translator on each domain • Super-Agent: – central request handler, – inter-domain path- finder – messaging to translators • Domain-NRPSs handle path-setup • Translators can be queried
  16. 16. Endpoints involved in the UvA-StarLight pathUvALight geller_8630_GBR_s8p4 geller_8630_GBR_s8p5 NetherLight-UvALight VM_fooyoung (perfSONAR) NetherLight Force10_Ge0/5 (to UvALight) UvA : geller_8630_GBR_s8p4 NetherLight Force10_Ge0/6 (to UvALight) UvA : geller_8630_GBR_s8p5 NetherLight To StarLight StarLight Starlight starlight:arista-sl:1/13 to USLHCNet / NetherLight USLHCNet & NetherLight Starlight starlight:arista-sl:1/14 to JGN2 JGN2 Starlight starlight:arista-sl:1/24 StarLight PerfSONAR StarLight PerfSONAR
  17. 17. Conclusions and future work• Interoperability between heterogeneous Network Resource Provisioning Systems is possible• An hierarchical model is easiest to realize for heterogeneous NRPSs (lesson learned from Harmony)• A federated model is more flexible (design changes in the interface apply to all instances), has enhanced interoperability and scalability• We have show that mixing the two models is possible, but leads to a lot of ad-hoc solutions• Ideal solution is a standardized Network Service Interface: work underway in the OGF-NSI working group. However: slow progress• Future work: – Investigate automation of GOLES: OGF automated-GOLE WG – Improve the design and application of the current prevalent hierarchical design component: Fenius – Investigate if an IDC service interface can be designed to improve integration with DRAC
  18. 18. Questions?Thank you!