NSI/NML Resource and Topology Issues OGF Munich March 2010.

Slides:



Advertisements
Similar presentations
© 2006 Open Grid Forum Network Services Interface OGF30: Connection Services Guy Roberts, 27 th Oct 2010.
Advertisements

Use cases for implementation of the NSI interface Takahiro Miyamoto, Nobutaka Matsumoto KDDI R&D Laboratories Inc. This work is partially supported by.
© 2006 Open Grid Forum Network Services Interface Introduction to NSI Guy Roberts.
NSI wg Architecture Elements John Vollbrecht Internet2.
© 2010 Open Grid Forum Choices in Reservation operation 1PC/2PC, timing Tomohiro Kudoh, AIST.
1 Virtual Resource Management (VRM) in Cloud Environment draft-Junsheng-Cloud-VRM-00 Friday 21 Jan 2011 B. Khasnabish, Chu JunSheng, Meng Yu.
1 Introducing the Specifications of the Metro Ethernet Forum.
Modeling Software Systems Lecture 2 Book: Chapter 4.
NSI Architecture Document Status and Work to be done: A view from a chair Inder Monga ESNet.
Access Control CS461/ECE422 Fall Reading Material Chapter 4 through section 4.5 Chapters 23 and 24 – For the access control aspects of Unix and.
NEW OUTLOOK ON MULTI-DOMAIN AND MULTI-LAYER TRAFFIC ENGINEERING Adrian Farrel
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.
Hidden Terminal Problem and Exposed Terminal Problem in Wireless MAC Protocols.
© 2006 Open Grid Forum Network Service Interface in a Nut Shell GEC 19, Atlanta, GA Presenter: Chin Guok (ESnet) Contributors: Tomohiro Kudoh (AIST), John.
Joining LANs - Bridges. Connecting LANs 4 Repeater –Operates at the Physical layer no decision making, processing signal boosting only 4 Bridges –operates.
Compute Aggregate 1 must advertise this link. We omit the physical port on the switch to which the node is directly connected. Network Aggregate Links.
Ethernet and switches selected topics 1. Agenda Scaling ethernet infrastructure VLANs 2.
Feb On*Vector Workshop Semantic Web for Hybrid Networks Dr. Paola Grosso SNE group University of Amsterdam The Netherlands.
Shalini Bhavanam. Key words: Basic Definitions Classification of Networks Types of networks Network Topologies Network Models.
Core 3: Communication Systems. On any network there are two types of computers present – servers and clients. By definition Client-Server architecture.
MODULE IV SWITCHED WAN.
National Science Foundation Arlington, Virginia January 7-8, 2013 Tom Lehman University of Maryland Mid-Atlantic Crossroads.
Institute of Computer and Communication Network Engineering OFC/NFOEC, 6-10 March 2011, Los Angeles, CA Lessons Learned From Implementing a Path Computation.
Basic LAN techniques IN common with all other computer based systems networks require both HARDWARE and SOFTWARE to function. Networks are often explained.
GEC 15 Houston, Texas October 23, 2012 Tom Lehman Xi Yang University of Maryland Mid-Atlantic Crossroads (MAX)
Cisco 3 - LAN Perrine. J Page 110/20/2015 Chapter 8 VLAN VLAN: is a logical grouping grouped by: function department application VLAN configuration is.
Clever Framework Name That Doesn’t Violate Copyright Laws MARCH 27, 2015.
NSI Topology Wishes OGF Lyon Sep 2011 Jerry Sobieski.
Omniran CF00 1 P802.1CF NRM Mapping to real networks Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Omniran CF CF Network Reference Model Introduction Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
Silberschatz, Galvin and Gagne  Operating System Concepts UNIT II Operating System Services.
Framework & Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks draft-ietf-ancp-framework-02.txt Presenter: Dong Sun.
Abstraction and Control of Transport Networks
Dynamic Network Services In Internet2 John Vollbrecht /Dec. 4, 2006 Fall Members Meeting.
Internetworking Lecture 10 October 23, Introduction to Internetworking So far, we’ve discussed about how a single network functions. Internetworking.
© 2006 Open Grid Forum Network Services Interface Document roadmap, April 2014 Guy Roberts, Chin Guok, Tomohiro Kudoh.
1 Network Services Interface Connection Service v2.0 Tomohiro Kudoh (AIST) (OGF NSI-WG)
1 Network Services Interface An Interface for Requesting Dynamic Inter- datacenter Networks Tomohiro Kudoh (AIST) Guy Roberts (DANTE) Inder Monga (ESnet)
Saturday, July OGF32 – Salt Lake City NSI-WG: Network Service Interface working group OGF NSI Protocol Protocol status and discussion John MacAuley.
Network No network resources exist outside a network Transport resources inside network –Link, Nodes, ports – are used to create connections between network.
© 2007 Open Grid Forum NSI CS Protocol State Machine Message Handling OGF 37.
Operating Framework of Connection Networks OGF/NSI Working Group Chicago Oct. 10, 2012 John Vollbrecht & Leon Gommans University of Amsterdam.
© 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 NML Progres OGF 28, München.
Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Network Service Interface: Concepts and Architecture Inder Monga Guy.
NSI Topology v2.0 Version 1.2 John MacAuley, ESNET September 22, 2014 Uppsala.
IP Addressing, Sub-netting & VLSM
Chapter 3: Link Aggregation
ROUTING.
Operating Framework of Connection Networks
CCNA 3 Chapter 10 Virtual Trunking Protocol
Dynamic Circuit Networks Topology Description Issues
Network instantiation
Requirements for Ring Protection in MPLS-TP
NML-WG: Monday brainstorming
SUPA/YMCA (Yang Models for Configuration and topology Abstraction)
A Deterministic End to End Performance Verification Architecture
A hierarchical, NSI compatible, topology proposal for NML
NSI Topology Thoughts on how topology fits into the NSI architecture
NSI wg Architecture Elements
Integration of Network Services Interface version 2 with the JUNOS Space SDK
Availability Query / Internal Topology
Network Layer in the Internet (3)
Network Services Interface
AutoGOLE Dashboard presented by Cees de Laat
Planning the Addressing Structure
The University of Adelaide, School of Computer Science
What is an ESS? Date: Authors: July 2009
Presentation transcript:

NSI/NML Resource and Topology Issues OGF Munich March 2010

NSI Network Concepts In NSI every transport resource is owned by one and only one an NRM (Network Resource Manager) An NRM is embedded in one and only one NSA (Network Service Agent) An NSA may manage additional resources by using an NSI Requestor interface to make requests to other NSAs Segregation/ aggregation Segregation/ aggregation NRM NSI (provider) NSI (provider) NSI (requestor) NSI (requestor) To requestor To provider(s) Local resources NSA

NSI Concepts Set of resources managed by an NSA is called a network in NSI (a group owned by an NSA in NML talk) A network consists of all resources managed by an NSA (Network Service Agent) An Atomic Network is a network managed by an NRM – Atomic in the sense that resources cannot be divided among other networks Some extensions of this – A Network is a set of one or more Atomic networks – An network can be in multiple other networks

NS transport capability Network is the basic abstract transport resource presented to the outside Provider NSA schedules, reserves, and instantiates a connection between network ports on a network Network Ports are places where a network can attach to another network or to an end systems transport

Connecting Networks Networks connect to other networks by joining ports at a topological point I call this a Network Point (so far)

Topology Graph for Interconnected Networks Resource R3 Resource R2 Resource R1 Port P1 Port P2 Port P1 Point T1 Point T3 Point T2 T 1 := {R 1 /P 2, R 3 /P 2 }; T 2 := {R 1 /P 1, R 2 /P 1 }; T 3 := {R 2 /P 2, R 3 /P 1 }; T3 T2 T1 R3 R2R1

network Network each network known by an NSA Atomic network

NRM NSI (provider) NSI (provider) Net A NRM NSI (provider) NSI (provider) Net C NRM NSI (provider) NSI (provider) Net B Segregation/ aggregation Segregation/ aggregation NSI (provider) NSI (provider) NSI (requestor) NSI (requestor) Segregation/ aggregation Segregation/ aggregation NSI (provider) NSI (provider) NSI (requestor) NSI (requestor) NSA 1 NSA 4 NSA 5 NSA 2 NSA 3 Network (N1) at NSA1 == [NetA, NetB] Network (N2) at NSA2 == [NetB, NetC] Atomic Network (Net B) in multiple networks

Question for NML NSI implies a topology of connected networks Networks connect (relate) directly to each other A Network is defined by which NSA can make connections across it Question is how to describe this topology (perhaps a next version of NML?) Topology seen from service plane is different from actual data plane topology so can NML provide a way a to describe this?

Topology requirements from NSI Requirements doc [with a few edits for clarity] The model must describe a group of network resources that are owned or controlled by a single Provider NSA. (tentatively called network) The model must be able to describe a grouping of Networks (also a network) The model must be able to describe resources (ports/points) in a Network that are available for connecting to other Networks. Network Ports must be able to be assigned to the end of a either a link or node that is internal to the network The model must be able to describe an arbitrary number of layers of logical ports within a Network Port. The model must be able to describe connectivity between Networks. The resources that attached to Network Points must have ownership by a clearly identifiable provider The model must allow policy to be assigned at network and port level