A hierarchical, NSI compatible, topology proposal for NML

Slides:



Advertisements
Similar presentations
© 2006 Open Grid Forum Network Services Interface Introduction to NSI Guy Roberts.
Advertisements

NSI/NML Resource and Topology Issues OGF Munich March 2010.
A Guide to INCTR s Portal Enhancing international communication in the service of global cancer control.
NMC-WG Session 2 October 28 th 2010, OGF 30 Jason Zurawski – Internet2 Roman Lapacz – PSNC/GÉANT3.
Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Network Service Interface (NSI) Inder Monga Co-chair, Network Services.
NORDUnet Nordic infrastructure for Research & Education NSI in the SDN Environment (from perspective of an NSI fellow) Jerry Sobieski NORDUnet Presented.
© 2006 Open Grid Forum Network Service Interface in a Nut Shell GEC 19, Atlanta, GA Presenter: Chin Guok (ESnet) Contributors: Tomohiro Kudoh (AIST), John.
Semantic Web Thanks to folks at LAIT lab Sources include :
NORDUnet Nordic Infrastructure for Research & Education Service Sharing at NORDUnet Lars Fischer TF-MSP Meeting Malta, 27 November 2014.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
1 Review of Important Networking Concepts Introductory material. This module uses the example from the previous module to review important networking concepts:
OCR Nationals ICT – Unit 2 Task 3 Task Overview In this task you will create hyperlinks to link the pages together, link to other websites on the Internet.
The Data Grid: Towards an Architecture for the Distributed Management and Analysis of Large Scientific Dataset Caitlin Minteer & Kelly Clynes.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 LAN Switching and Wireless Implement Spanning Tree Protocols (STP) Chapter.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 4: Addressing in an Enterprise Network Introducing Routing and Switching in the.
NSH0503/01/11041 Overview Computer Network Technology By Diyurman Gea.
Lecture # 3 & 4 Chapter # 2 Database System Concepts and Architecture Muhammad Emran Database Systems 1.
DataBase Management System What is DBMS Purpose of DBMS Data Abstraction Data Definition Language Data Manipulation Language Data Models Data Keys Relationships.
Chapter 2 Dissecting the OSI Model
NSI Topology Wishes OGF Lyon Sep 2011 Jerry Sobieski.
Restructuring Proposal for TOSCA Files 1. Goals Separation of concerns: only expose what is needed to different roles in the creation of TOSCA templates.
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
Component Design Elaborating the Design Model. Component Design Translation of the architectural design into a detailed (class-based or module- based)
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Implement Spanning Tree Protocols (STP) LAN Switching and Wireless – Chapter.
© 2006 Open Grid Forum Network Services Interface Document roadmap, April 2014 Guy Roberts, Chin Guok, Tomohiro Kudoh.
NORDUnet Nordic Infrastructure for Research & Education Update on OpenNSA LHCONE Meeting, CERN, February 2014 Henrik Thostrup Jensen
© 2010 Open Grid Forum STP and TF how they work Tomohiro Kudoh.
NSI Service Definition Federation of providers A group of network providers get together and decide that they wish to offer a multi-domain connection services.
1 Network Services Interface An Interface for Requesting Dynamic Inter- datacenter Networks Tomohiro Kudoh (AIST) Guy Roberts (DANTE) Inder Monga (ESnet)
Network No network resources exist outside a network Transport resources inside network –Link, Nodes, ports – are used to create connections between network.
© 2006 Open Grid Forum NML Agenda OGF 34, Oxford.
Topology Issues in Inter-Domain Connection Services Jerry Sobieski (NORDUnet) The Cynic’s Perspective & Jeroen van der Ham (University of Amsterdam) The.
© 2006 Open Grid Forum A hierarchical, NSI compatible, topology proposal for NML Jerry Sobieski NORDUnet Presented at OGF 34.
NSI Topology v2.0 Version 1.2 John MacAuley, ESNET September 22, 2014 Uppsala.
© 2006 Open Grid Forum The Network Services Interface An Overview of the NSI Framework and the GLIF Automated GOLE dynamic network provisioning demonstration.
NORDUnet Nordic infrastructure for Research & Education NSI V3 Some Burning Topics for Discussion and Features for Consideration The musings of Jerry Sobieski.
Chapter 2 Network Models
Services in a Converged WAN
NML support in AutoGOLE
Dynamic Circuit Networks Topology Description Issues
Task Analysis CSCI 4800/6800 Feb 27, 2003.
(OGF NSI-WG co-chairs)
Network Architecture Layered system with alternative abstractions available at a given layer.
Part I. Overview of Data Communications and Networking
Objective: ARP.
NML-WG: Monday brainstorming
SUPA/YMCA (Yang Models for Configuration and topology Abstraction)
Network Services Interface
A Deterministic End to End Performance Verification Architecture
NSI Topology Thoughts on how topology fits into the NSI architecture
NSI Service Definition
Data Models.
Integration of Network Services Interface version 2 with the JUNOS Space SDK
Network Services Interface gateway for future network services
Availability Query / Internal Topology
Single-Area OSPF (Open Shortest Path First Protocol)
Network Services Interface
A hierarchical, NSI compatible, topology proposal for NML
Module 5 - Switches CCNA 3 version 3.0.
Component-Level Design
Network Services Interface
Services in a Converged WAN
CS 4594 Broadband PNNI Signaling.
Digital Fundamentals Floyd Chapter 4 Tenth Edition
Hardware Modeling & Synthesis Using VHDL
Services in a Converged WAN
Cengage Learning: Computer Networking from LANs to WANs
Review of Important Networking Concepts
Routing Considerations
TAPI Topology & Connectivity Enhancements Proposal for v3.0
Presentation transcript:

A hierarchical, NSI compatible, topology proposal for NML Jerry Sobieski NORDUnet Presented at OGF 34

Hierarchical topology… The existing NSI topology model does not provide a consistent mechanism for exposing intra-domain topological structure. The base model hides all internal structure…which is good in many (most) high level cases…. But… Where a network wishes to do so, it should be able to expose additional internal structure or state in a measured and graduated degree…down to the hardware minutia if so desired.

NML recommendations This proposal retains the NSI abstractions at the highest topological layer, and retains the NSI model internally as smaller NSI domains are defined A key relation called an “alias” is defined to link STPs (NML Ports) at any desired level to STPs at the next lower (more detailed) level. An Alias is an internal topological construct that should probably be stored at the lower level (more detailed level). It therefore stays private until/unless that level is announced externally. (local agents will not have a problem using this relation.) An Alias could [alternatively] reference a conventional NML topological object – thus mapping the NSI topology to appropriate NML object as the local topology manager deems appropriate.

NSI Topology Example Current existing NSI topology model: only L0 has structure, L1+ is opaque (private) PSNC Topo level 1 NDN.EFDX Opaque internal Topo level 1 NDN Pionier Universal space Topo level 0 STPs (NML Ports) Internet2 Internet2 Topo level 1 NetherLight-o NDN SDPs (NML Links) NetherLight Topo level 1 NDN ION-o

Proposed Hierarchical NSI Topology Example Proposed NorthernLight topology: L0 & internal L1 objects are publically announced by NorthernLight; As a Worldview, this topo would say I2, PSNC, and NL only announced L0 information. As a Local Topology from NDN, this is the only L0 information that NorthernLight can provide (i.e. its direct adjacencies) Pionier Topo level 1 NDN.EFDX Topo level 1 NDN Pionier Universal space Topo level 0 NYC Level 2 CPH CPH Level 2 POZ ION Blue links are “aliases” indicating an level transition in the topology. (Aliases act similarly to SDPs, so red and blue relations are simple logical links.) NYC AMS Internet2 Internet2 Topo level 1 NDN NetherLight NetherLight Topo level 1 NDN

Hierarchical Topology Proposal Bi-directional Example topo{ name $L0$; /* level 0 is the universal space */ topo{ name NDN.EFDX; version 2012-02-29-18:42:23 /* level 1 topology */ NSA https://orval.grid.aau.dk:9443/NSI/services/ConnectionService port Pionier, NetherLight, Internet2 bidirectional; topo{ name CPH; location lat 24.1234 lon -57.2345; /* level 2 topology */ port AMS, POZ, NYC bidirectional; } topo{ name NYC; location lat 24.1234 lon -87.2345; /* level 2 topology */ port ION, CPH bidirectional; link NYC:CPH, CPH:NYC; /* level 2 to level 2 */ alias NDN.EFDX:Pionier, CPH:POZ; /* level 1 to level 2 boundary links */ alias NDN.EFDX:NetherLight, CPH:AMS; /* level 1 to level 2 boundary links */ alias NDN.EFDX:Internet2, NYC:ION; /* level 1 to level 2 boundary links */ Link NDN.EFDX:Pionier, Pionier.EFDX:NDN; /* NDN level 1 port to Pionier level 1 port */ Link NDN.EFDX:NetherLight, NetherLight.EFDX:NDN; /* level 1 port to level 1 port */ Link NDN.EFDX:Internet2, Internet2.EFDX:NDN; /* level 1 port to level 1 port */

Modular description Proposal by T.K. network $L0${ /* level 0 is the top level universal space */ has_networks NDN.EDFX, Pionier.EFDX, NetherLight.EFDX, Internet2.EFDX; link CPH:POZ, Pionier.EFDX:NDN; /* SDP */ link CPH:AMS, NetherLight.EFDX:NDN; /* SDP */ link NYC.ION:Internet2, Internet2.EFDX:NDN; /* SDP */ } network NDN.EDFX { ; version 2012-02-29-18:42:23 /* level 1 network */ NSA https://orval.grid.aau.dk:9443/NSI/services/ConnectionService; has_networks CPH, NYC; port CPH:POZ, CPH:AMS, NYC:ION bidirectional; /* STPs */ link NYC:CPH, CPH:NYC; /* SDP */ network Pionier.EFDX { NSA https://..... port Pionier.EFDX:NDN; network NetherLight.EFDX {...} network Internet2.EFDX {...} network CPH { ; location lat 24.1234 lon -57.2345; /* level 2 network */ port CPH:AMS, CPH:POZ, CPH:NYC bidirectional; /* STPs */ network NYC { ; location lat 24.1234 lon -87.2345; /* level 2 network */ port NYC:ION, NYC:CPH bidirectional; /* STPs */

Modular description / network view Proposal by T.K. Modular description / network view network $L0${ /* level 0 is the top level universal space */ has_networks NDN.EDFX, Pionier.EFDX, NetherLight.EFDX, Internet2.EFDX; } network NDN.EDFX { ; version 2012-02-29-18:42:23 /* level 1 network */ NSA https://orval.grid.aau.dk:9443/NSI/services/ConnectionService; has_networks CPH, NYC; port CPH:POZ, CPH:AMS, NYC:ION bidirectional; /* STPs */ link CPH:POZ, Pionier.EFDX:NDN; /* SDP */ link CPH:AMS, NetherLight.EFDX:NDN; /* SDP */ link NYC.ION:Internet2, Internet2.EFDX:NDN; /* SDP */ network Pionier.EFDX { NSA https://..... port Pionier.EFDX:NDN; link Pionier.EFDX:NDN, CPH:POZ; /* SDP */ network NetherLight.EFDX {...} network Internet2.EFDX {...} network CPH { ; location lat 24.1234 lon -57.2345; /* level 2 network */ port CPH:AMS, CPH:POZ, CPH:NYC bidirectional; /* STPs */ link CPH:NYC, NYC:CPH; /* SDP */ network NYC { ; location lat 24.1234 lon -87.2345; /* level 2 network */ port NYC:ION, NYC:CPH bidirectional; /* STPs */ link NYC:CPH, CPH:NYC; /* SDP */

Modular description / with alias Proposal by T.K. Modular description / with alias network $L0${ /* level 0 is the top level universal space */ has_networks NDN.EDFX, Pionier.EFDX, NetherLight.EFDX, Internet2.EFDX; } network NDN.EDFX { ; version 2012-02-29-18:42:23 /* level 1 network */ NSA https://orval.grid.aau.dk:9443/NSI/services/ConnectionService; has_networks CPH, NYC; port CPH:POZ alias NDN.EDFX:Pionier , CPH:AMS alias NDN.EDFX:NetherLight, NYC:ION alias NDN.EDFX:Internet2 bidirectional; /* STPs */ link NDN.EFDX:Pionier, Pionier.EFDX:NDN; /* SDP */ link NDN.EFDX:NetherLight, NetherLight.EFDX:NDN; /* SDP */ link NDN.EFDX:Internet2, Internet2.EFDX:NDN; /* SDP */ network Pionier.EFDX { NSA https://..... port Pionier.EFDX:NDN; link Pionier.EFDX:NDN, NDN.EFDX:Pionier; /* SDP */ network NetherLight.EFDX {...} network Internet2.EFDX {...} network CPH { ; location lat 24.1234 lon -57.2345; /* level 2 network */ port CPH:AMS, CPH:POZ, CPH:NYC bidirectional; /* STPs */ link CPH:NYC, NYC:CPH; /* SDP */ network NYC { ; location lat 24.1234 lon -87.2345; /* level 2 network */ port NYC:ION, NYC:CPH bidirectional; /* STPs */ link NYC:CPH, CPH:NYC; /* SDP */

Modular description / no internals Proposal by T.K. Modular description / no internals network $L0${ /* level 0 is the top level universal space */ has_networks NDN.EDFX, Pionier.EFDX, NetherLight.EFDX, Internet2.EFDX; } network NDN.EDFX { ; version 2012-02-29-18:42:23 /* level 1 network */ NSA https://orval.grid.aau.dk:9443/NSI/services/ConnectionService; port NDN.EDFX:Pionier , NDN.EDFX:NetherLight, NDN.EDFX:Internet2 bidirectional; /* STPs */ link NDN.EFDX:Pionier, Pionier.EFDX:NDN; /* SDP */ link NDN.EFDX:NetherLight, NetherLight.EFDX:NDN; /* SDP */ link NDN.EFDX:Internet2, Internet2.EFDX:NDN; /* SDP */ network Pionier.EFDX { NSA https://..... port Pionier.EFDX:NDN; link Pionier.EFDX:NDN, NDN.EFDX:Pionier; /* SDP */ network NetherLight.EFDX {...} network Internet2.EFDX {...}