We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byGreyson Key
Modified about 1 year ago
© 2006 Open Grid Forum Network Service Interface in a Nut Shell GEC 19, Atlanta, GA Presenter: Chin Guok (ESnet) Contributors: Tomohiro Kudoh (AIST), John MacAuley (ESnet), Inder Monga (ESnet), Guy Roberts (DANTE), Jerry Sobieski (NORDUnet) 17 th March 2014
© 2006 Open Grid Forum 2 NRM 1.“Network Service Interface” is a framework for inter-domain service coordination Examples: Connection Service (NSI-CS) Topology Service (NSI-TS) Discovery Service (NSI-DS) Switching Service (NSI-SS) Monitoring Service Protection Service Verification Service Etc. NSI Fundamental Design Principles (1/3) NSA Network Services Agent (NSA) Requester Agent (RA) Provider Agent (PA) Network Services Interface Network Resource Manager (NRM) NSI Network Service Domain 2 Supports advance reservations
© 2006 Open Grid Forum 3 2. Designed for flexible, multi-domain, service chaining Domain CDomain BDomain A NSI Topology Supports Tree and Chain model of service chaining Fits in well with Cloud/Compute model of provisioning as well as Network/GMPLS model Domain CDomain BDomain A NSA Aggregator NSA NSI Topology NSA ultimate RA ultimate PA uPA uRA Aggregator/ uPA NSI Fundamental Design Principles (2/3)
© 2006 Open Grid Forum 4 3. Principles of Abstraction applied – to network layers, technologies and domains Service Termination Points (STP) and Service Demarcation Points (SDP) are abstract and technology independent NSI Fundamental Design Principles (3/3)
© 2006 Open Grid Forum 5 NSA’isms An NSA can take on the following roles: uRA: The ultimate Requester Agent is the originator of a service request. This could, for example, exist in a middleware application. [Only requestor function is supported] AG: The Aggregator has more than one child NSA, and has the responsibility of aggregating the responses from each child NSA. [Both Provider and Requester functions are supported] uPA: The ultimate Provider Agent services requests by coordinating with the local Network Resource Manager (NRM) to manage network resources. [Only Provider function is supported] NSA Business Logic Message Coordinator Message Transport Layer Message tracking (i.e. last message sent out, absence of reply, etc) Aggregation of requests, replies, and notifications Decoupled message delivery mechanism from “NSI” layer Reliable and secure delivery of messages Implement behaviors as defined by state machine Enforces local policies
© 2006 Open Grid Forum Chain-based signaling model 6 uRA uPA AG A B uPA AG C D uPA AG E F Host Source STP Destination STP Signaling Flow Every NSA associated with network resources must be an Aggregator capable of propagating a reservation request to the local uPA component and at most one adjacent (child) NSA associated with the next connection segment in the data path. 6
© 2006 Open Grid Forum Tree-based signaling model 7 uRA uPA AG A B uPA AG C D uPA E F Host Source STP Destination STP Signaling Flow AG 7 An Aggregator involved in a connection reservation does not have to be associated with any network resources involved in creation of that service. A uRA can issue a service request to an Aggregator NSA anywhere in the network if authorized to do so, and the NSI CS protocol with handle creating the reservation.
© 2006 Open Grid Forum 8 Service Termination Points (STP) and Service Demarcation Points (SDP) STPs represent the external interfaces of the network domain An STP is a symbolic reference: a Network identifier string in the higher order portion a local STP identifier in the lower order portion SDP = interconnected STPs Abstracts the connectivity between two STPs Switching Service (SS) indicates the internal network capabilities *NB: Not the same as the NSI-SS (which is a multi-point service) STP a Network STP c STP b STP d SS* N1/a N1/ b N2/ X N2/ y SDP STP a = Network + ‘a’ (local identifier)
© 2006 Open Grid Forum NSI Connection Service (v2.0) 9 NSI is an advance-reservation based protocol A reservation of a connection has properties such: A-point, Z-point (mandatory) Start-time, End-time (optional*) Bandwidth, Labels (optional) A reservation is made in two-phase First phase: availability is checked, if available resources are held Second phase: the requester either commit or abort a held reservation Two-phase is convenient when a requester requests resources from multiple providers, including other resources such as computers and storages Timeout: If a requester does not commit a held reservation for a certain period of time, a provider can timeout Modification of a reservation is supported. Currently, modification of start_time, end_time and bandwidth are supported *NB: Restricted to PA policies
© 2006 Open Grid Forum NSI CS RA -> PA Messages (Requests) 10 NSI CS Message (abbreviation) SMSynch. /Asynch. Short Description reserve (rsv.rq) RSMAsynchThe reserve message allows an RA to send a request to reserve network resources to build a Connection between two STP's. reserveCommit (rsvcommit.rq) RSMAsynchThe reserveCommit message allows an RA to request the PA commit a previously allocated Connection reservation or modify an existing Connection reservation. reserveAbort (rsvabort.rq) RSMAsynchThe reserveAbort message allows an RA to request the PA to abort a previously requested Connection that was made using the reserve message. provision (prov.rq) PSMAsynchThe provision message allows RA to request the PA to transition a previously requested Connection into the Provisioned state. A Connection in Provisioned state will activate associated data plane resources during the scheduled reservation time. release (release.rq) PSMAsynchThe release message allows an RA to request the PA to transition a previously provisioned Connection into Released state. A Connection in a Released state will deactivate the associated resources in the data plane. The reservation is not affected. terminate (term.rq) LSMAsynchThe terminate message allows an RA to request the PA to transition a previously requested Connection into Terminated state. A Connection in Terminated state will release associated resources and allow the PA to clean up the RSM, PSM and all related data structures.
© 2006 Open Grid Forum The NSI CS NSA has 3 logically distinct state machines (per reservation) Reservation State Machine (RSM) Manages the resource reservation process (i.e. scheduling and bookings) Is instantiated as soon as first connection requests is received Provisioning State Machine (PSM) Supports the activation/deactivation of the data plane Is instantiated as soon as the first “version” of the reservation is committed Decoupled from reservation process to delineate separation of concerns Life Cycle State Machine (LSM) Supports the termination of the reservation at any state/time Is instantiated as soon as first connection requests is received 11 NSI CS State Machines
© 2006 Open Grid Forum 12 Reserve Held Reserve Checkin g Reserve Failed rsv.rq >rsvcommit.rq Reserve Committi ng Transitional States Initial State Stable States Reserve Aborting Reserve Timeout (reserve_timeout) rsvabort.rq rsvcommit.rq rsvabort.rq Reserve Start ” = downstream message “<“ = upstream message RSM: Reservation Successfully Committed Commit request Reserve request (check availability)
© 2006 Open Grid Forum 13 Reserve Held Reserve Checkin g Reserve Failed rsv.rq >rsvcommit.rq Reserve Committi ng Transitional States Initial State Stable States Reserve Aborting Reserve Timeout (reserve_timeout) rsvabort.rq rsvcommit.rq rsvabort.rq Reserve Start ” = downstream message “<“ = upstream message RSM: Reservation Aborted after Resources Held Abort request Reserve request (check availability)
© 2006 Open Grid Forum 14 Reserve Held Reserve Checkin g Reserve Failed rsv.rq >rsvcommit.rq Reserve Committi ng Transitional States Initial State Stable States Reserve Aborting Reserve Timeout (reserve_timeout) rsvabort.rq rsvcommit.rq rsvabort.rq Reserve Start ” = downstream message “<“ = upstream message RSM: Reservation Failed due to Unavailable Resources Reserve request (check availability)
© 2006 Open Grid Forum 15 Reserve Held Reserve Checkin g Reserve Failed rsv.rq >rsvcommit.rq Reserve Committi ng Transitional States Initial State Stable States Reserve Aborting Reserve Timeout (reserve_timeout) rsvabort.rq rsvcommit.rq rsvabort.rq Reserve Start ” = downstream message “<“ = upstream message RSM: Reservation Aborted after Failed (for Modify) Abort request
© 2006 Open Grid Forum 16 Reserve Held Reserve Checkin g Reserve Failed rsv.rq >rsvcommit.rq Reserve Committi ng Transitional States Initial State Stable States Reserve Aborting Reserve Timeout (reserve_timeout) rsvabort.rq rsvcommit.rq rsvabort.rq Reserve Start ” = downstream message “<“ = upstream message RSM: Reservation Timed Out after Resources Held Timeout
© 2006 Open Grid Forum 17 PSM: Provisioning Lifecycle Releasin g Provisio ning >prov.rq >rel.rq ” = downstream message “<“ = upstream message
© 2006 Open Grid Forum 18 LSM: Termination Sequence Stable States Transitional State Final State Input event Input message Output message Output event “>” = downstream message “<“ = upstream message Terminat ed Terminati ng Created >term.rq term.rq Passed EndTime endTimeEvent>term.rq Initial State
© 2006 Open Grid Forum Reservation, Provisioning, and Activation 19 Reservation State Machine Provision State Machine Committed Reservation Provisioned /Scheduled Committed Reservation startTime update transition Timer Data Plane is activated according to the latest committed reservation, when PSM is in “Provisioned” state AND during a reservation period Current Time Committed Reservation endTime dataPlaneStatusChance.nt
© 2006 Open Grid Forum Manual vs “Automatic” Provisioning 20 Provision request is sent before reservation startTime Dataplane activation only occurs at startTime At reservation endTime, dataplane is automatically torn down Dataplane is not in service after startTime because it has not received a provision request Past startTime, dataplane will be activated as soon as it receives a provision request Dataplane will be torn down by a terminate request anytime prior to the endtime If endTime elapse before a terminate is received, dataplane is torn down automatically For “On-Demand” Reservation/Provisioning: Leave startTime empty*, or set to <= Current Time Provision request is issued immediately after reservation is confirmed *NB: Restricted to PA policies
© 2006 Open Grid Forum NSI Service Type and Definition 21 Common service The providers need to agree among themselves the service they wish to offer to the customer. For example they may wish to offer an Ethernet VLAN Transport Service (EVTS). The service must be common to all providers and all providers must agree in advance a minimum service level that they are all able to meet. Introduction of Service Type and Service Definition removes the dependencies of service specification from the core NSI CS protocol. This allows the NSI CS protocol to remain stable while permitting changes to the services offered by NSA within the network. Abstraction of physical properties of the underlying data plane can be achieved by the Service Definition.
© 2006 Open Grid Forum 22 Building an XML Service Definition Instance The provider federation must create a common service definition instance that describes the requestable elements of multi-domain service that they wish to offer. The SD defines the parameters of the service request, their optionality, modifiability, and the range of allowed values for each. Some example parameters: Connection startTime, endTime, capacity, VLAN ranges, and MTU. The SD also describes attributes of the service that are not specified in the reservation request but describe features of the service being offered. Lastly, the SD describes service specific errors and their meanings.
© 2006 Open Grid Forum 23 How Service Types/Definitions are used in a Reservation Request Steps: 1.When reserveRequest arrives extract the serviceType value. 2.Fetch the Service Definition corresponding to the serviceType. 3.Extract the specific service elements from criteria as specified in SD. 4.Use the Service Definition to validate request. 5.Process using both the supplied service parameters and additional information as needed from the Service Definition document.
© 2006 Open Grid Forum NSI NSA Implementations 24 AutoBAHN – GÉANT (Poznan, PL) BoD - SURFnet (Amsterdam, NL) DynamicKL – KISTI (Daejeon, KR) G-LAMBDA-A - AIST (Tsukuba, JP) G-LAMBDA-K – KDDI Labs (Fujimino, JP) OpenNSA – NORDUnet (Copenhagen, DK) OSCARS – ESnet (Berkeley, US)
© 2006 Open Grid Forum OGF NSI Information 25 OGF NSI Working Group Site http://redmine.ogf.org/projects/nsi-wg/ NSI Project Page https://code.google.com/p/ogf-nsi-project/ NSI Documents NSI Framework: http://redmine.ogf.org/dmsf_files/13168?download= http://redmine.ogf.org/dmsf_files/13168?download NSI CS v2 (in public comment till Apr 15 2014): http://redmine.ogf.org/dmsf_files/13168?download= http://redmine.ogf.org/dmsf_files/13168?download NSI Co-Chairs Guy Roberts Inder Monga Tomohiro Kudoh
1 Network Services Interface An Interface for Requesting Dynamic Inter- datacenter Networks Tomohiro Kudoh (AIST) Guy Roberts (DANTE) Inder Monga (ESnet)
1 Network Services Interface Connection Service v2.0 Tomohiro Kudoh (AIST) (OGF NSI-WG)
Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Network Service Interface (NSI) Inder Monga Co-chair, Network Services.
© 2007 Open Grid Forum NSI CS Protocol State Machine Message Handling OGF 37.
© 2006 Open Grid Forum Network Services Interface Policy-based routing enforcement John MacAuley, ESnet 4 th February 2015.
Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Network Service Interface: Concepts and Architecture Inder Monga Guy.
© 2006 Open Grid Forum Network Services Interface Document roadmap, April 2014 Guy Roberts, Chin Guok, Tomohiro Kudoh.
© 2006 Open Grid Forum Network Services Interface Introduction to NSI Guy Roberts.
© 2006 Open Grid Forum Network Services Interface CS Errata Guy Roberts, Chin Guok, Tomohiro Kudoh 29 Sept 2015.
NSI Topology v2.0 Version 1.2 John MacAuley, ESNET September 22, 2014 Uppsala.
© 2006 Open Grid Forum Network Services Interface OGF 32, Salt Lake City Guy Roberts, Inder Monga, Tomohiro Kudoh 16 th July 2011.
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 The Network Services Interface An Overview of the NSI Framework and the GLIF Automated GOLE dynamic network provisioning demonstration.
NSI/NML Resource and Topology Issues OGF Munich March 2010.
© 2010 Open Grid Forum STP and TF how they work Tomohiro Kudoh.
Saturday, July OGF32 – Salt Lake City NSI-WG: Network Service Interface working group OGF NSI Protocol Protocol status and discussion John MacAuley.
Thoughts on the Firewall NAT issue* 1 Tomohiro Kudoh * I think the issue we are discussing as the “firewall issue” is almost a NAT issue (i.e. a process.
Policy in GÉANT Guy Roberts, Tangui Coulouarn NSI meeting, NORDUnet Conference, Uppsala, 22 Sept 2014.
NSI Architecture Document Status and Work to be done: A view from a chair Inder Monga ESNet.
© 2006 Open Grid Forum Network Services Interface OGF30: Working Group Meeting Guy Roberts, Inder Monga, Tomohiro Kudoh 27 th Oct 2010.
© 2006 Open Grid Forum Network Services Interface OGF30: Connection Services Guy Roberts, 27 th Oct 2010.
© 2010 Open Grid Forum Choices in Reservation operation 1PC/2PC, timing Tomohiro Kudoh, AIST.
NORDUnet Nordic infrastructure for Research & Education LHCONE NSI Adaptation An Applications’ Perspective Jerry Sobieski NORDUnet CERN Dec. 13/
“Time” in the NSI Protocol Two notions of “Time” are important to NSI Connection Service – Absolute time Globally Coordinated Time and Date, “UTC” time.
DICE: Authorizing Dynamic Networks for VOs Jeff W. Boote Senior Network Software Engineer, Internet2 Cándido Rodríguez Montes RedIRIS TNC2009 Malaga, Spain.
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.
COE 342: Data & Computer Communications (T042) Dr. Marwan Abu-Amara Chapter 2: Protocols and Architecture.
Supporting Advanced Scientific Computing Research Basic Energy Sciences Biological and Environmental Research Fusion Energy Sciences High Energy Physics.
1 Virtual Resource Management (VRM) in Cloud Environment draft-Junsheng-Cloud-VRM-00 Friday 21 Jan 2011 B. Khasnabish, Chu JunSheng, Meng Yu.
Hybrid MLN DOE Office of Science DRAGON Hybrid Network Control Plane Interoperation Between Internet2 and ESnet Tom Lehman Information Sciences Institute.
William Stallings Data and Computer Communications 7 th Edition Data Communications and Networks Overview Protocols and Architecture.
OGF DMNR BoF Dynamic Management of Network Resources Documents available at: Guy Roberts, John Vollbrecht.
SIGNALING. To establish a telephone call, a series of signaling messages must be exchanged. There are two basic types of signal exchanges: (1) between.
ESnet On-demand Secure Circuits and Advance Reservation System (OSCARS) Chin Guok Network Engineering Group Thomas Ndousse Visit February Energy.
NORDUnet Nordic infrastructure for Research & Education LHCONE “Point-to-Point Connection Service” Service Definition Jerry Sobieski.
Omniran CF00 1 Key Concepts of Association and Disassociation Date: Authors: NameAffiliationPhone Max RiegelNokia
Multi-Domain Lightpath Authorization Architecture using Tokens By: Leon Gommans, Paola Grosso, Fred Wan, Cees de Laat, Marten Hoekstra, Yuri Demchenko,
1 Introducing the Specifications of the Metro Ethernet Forum.
Operating Framework of Connection Networks OGF/NSI Working Group Chicago Oct. 10, 2012 John Vollbrecht & Leon Gommans University of Amsterdam.
DRAGON Dynamic Resource Allocation via GMPLS Optical Networks Tom Lehman University of Southern California Information Sciences Institute (USC/ISI) National.
William Stallings Data and Computer Communications 7 th Edition Chapter 2 Protocols and Architecture.
1 Revision to DOE proposal Resource Optimization in Hybrid Core Networks with 100G Links Original submission: April 30, 2009 Date: May 4, 2009 PI: Malathi.
Resource Management – a Solution for Providing QoS over IP Tudor Dumitraş, Frances Jen-Fung Ning and Humayun Latif.
NORDUnet Nordic infrastructure for Research & Education The OGF Network Services Interface Framework An Overview, Status, and Futures Presented to: OGF.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Communicating over the Network Network Fundamentals – Chapter 2.
Lucy Yong Young Lee IETF CCAMP WG GMPLS Extension for Reservation and Time based Bandwidth Service.
Semester Copyright USM EEE442 Computer Networks Introduction: Protocols En. Mohd Nazri Mahmud MPhil (Cambridge, UK) BEng (Essex, UK)
NSI Aggregator: Joint SURFnet/ESnet effort LHCONE Workshop CERN (Geneva, CH) Feb 10-11, 2014 NSI PCE Development Team.
SLC/Ver1.0/OS CONCEPTS/Oct'991INTRODUCTION What is an Operating System? Operating Structure -System Components -OS Services -System Calls & Programs -System.
1 IEX8175 RF Electronics Avo Ots telekommunikatsiooni õppetool, TTÜ raadio- ja sidetehnika inst.
© 2017 SlidePlayer.com Inc. All rights reserved.