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 NSI Project Page https://code.google.com/p/ogf-nsi-project/ NSI Documents NSI Framework: NSI CS v2 (in public comment till Apr ): NSI Co-Chairs Guy Roberts Inder Monga Tomohiro Kudoh
© 2006 Open Grid Forum Network Services Interface Introduction to NSI Guy Roberts.
© 2010 Open Grid Forum Choices in Reservation operation 1PC/2PC, timing Tomohiro Kudoh, AIST.
NSI/NML Resource and Topology Issues OGF Munich March 2010.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: XML framework for component communication Date Submitted: July.
NSI wg Architecture Elements John Vollbrecht Internet2.
1 Introducing the Specifications of the Metro Ethernet Forum.
NAESB Coordinate Interchange Standard, Version 1 / 0 ISAS Meeting San Diego, CA November 17 th, 2004.
1 Operating-System Structures Operating System & its purpose Operating Systems lead to new Hardware Features System Components System Services System Calls.
© 2006 Open Grid Forum Network Services Interface OGF30: Connection Services Guy Roberts, 27 th Oct 2010.
Advanced Operating Systems Prof. Muhammad Saeed Distributed Operating Systems Communication.
Research Challenges in the Emerging Hybrid Network World Tom Lehman University of Southern California Information Sciences Institute (USC/ISI)
Version 4.1 CCNA Discovery 2– Chapter 7. Contents 7.1: ISP Services : TCP / IP Protocols 7.2: 7.3: DNS 7.3: 7.4: Application Layer Protocols 7.4.
Windows 2008 Active Directory Configuration – Week 4 of 6 Microsoft Test: Mark McCoy MCSE, CNE, CISSP.
Agent Based Software Development Michael Luck, Ronald Ashri and Mark dInverno.
Silberschatz, Galvin, and Gagne Applied Operating System Concepts Module 14: Network Structures Background Motivation Topology Network Types.
Operating System Structures. Common System Components Due to the complex nature of the modern operating systems, it is partitioned into smaller component.
1 Computer Networks TCP/IP Protocol Suite. 2 Protocols Cooperative action is necessary computer networking is not only to exchange bytes huge system with.
G : DCM Signaling Mechanism Using GMPLS RSVP-TE ITU-T Workshop on IP-Optical, Chitose, Japan 7/11/2002 Dimitrios Pendarakis, Tellium, Inc. ITU-T.
TIB JINI. INTRODUCTION Here we look at only one type(web,object,file). Clear separation between computation and coordination exists. A distributed system.
© 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 Advanced reservation/Scheduling Tomohiro Kudoh (AIST, Japan)
GENI Distributed Services Preliminary Requirements and Design Tom Anderson and Amin Vahdat (co-chairs) David Andersen, Mic Bowman, Frans Kaashoek, Arvind.
Introduction to TCP/IP and OSI model 1/12/20141Mr. Naresh Sharma,
What is an Operating System? A program that acts as an intermediary between a user of a computer and the computer hardware. Operating system goals: Execute.
Comparison and Contrast between the OSI and TCP/IP Model.
Presented By : Vibhuti Dhiman. Outline : 1.Paper Abstract 2. Introduction 3.Design and Implementation 3.1 Event Propagation 3.2 HyperFlow Controller Application.
Windows 2008 Active Directory Configuration – Week 3 of 6 Microsoft Test: Mark McCoy MCSE, CNE, CISSP.
Security attacks. - confidentiality: only authorized parties have read access to information - integrity: only authorized parties have write access to.
© 2016 SlidePlayer.com Inc. All rights reserved.