Network Service Interface (NSI)

1. Network Service Interface (NSI) Inder Monga Co-chair, Network Services Interface Working Group OGF

2. Introduction • Cloud = “xxx” as a service • Grid = a ‘cloud’ made of federated resources • Open Grid Forum • Community of users, developers and vendors • Standardization for distributed computing (including clusters, grids and clouds) • Network Services Interface working group (nsi-wg) • Generic service interface between the user (and their application middleware) and multi-domain network infrastructure

3. Abstraction Present a simple interface to the external world

4. Network Services Framework • Specifies • An abstract Network Services Agent (NSA) that represents each network service region • A high level protocol model between NSAs to enable multi-domain services • An abstract model of a network “connection” • An abstract model of “topology” over which connections are established

5. Network Service Framework concepts Network Services Interface (NSI) Network Service A Network Service B Network Service A Network Service B Service Requestor Service Provider NSI Requestor Agent (RA) NSI Provider Agent (PA) NRM NRM NSA NSA Service Plane TransportPlane Local Resources Local Resources NSA = Network Services Agent NRM = Network Resource Manager * Slides contain animation, does not show in pdf

6. NSI Connection Service Slide from jerry Sobieski • The NSI Connection Service (NSI-CS) is the first protocol defined under the NSI Framework • NSI-CS specifies a set of basic primitives and functional capabilities that create and manage a NSI Connection through its life cycle. • NSI-CS Features: • Supports Reserve, Provision, Release, Terminate, and Query primitives. • Supports conventional “chain” signaling but also incorporates novel “tree” signaling - providing greater flexibility and control to the Requesting Agent – i.e. the user. • Allows users to schedule connections in advance. • Allows service providers to define common service specifications to aid in end to end service interoperability

7. How NSI-CS Works… NSA NSA NSA RM RM RM NSA Appl The user application RA PA Slide from jerry Sobieski

8. Congratulations! 7 independent interoperable implementations

9. Status • NSI 1.0sc demonstrated at SC with multiple independent implementations • Helped discover protocol and state machine issues • Independent development and demonstration of NSI by Science end-user: JIVE Project • NSI 2.0 features agreed upon at the OGF in March • Roadmap • NSI 2.0 feature implementation agreement by mid-summer • Formal specification draft by late summer • New children drafts on service discovery, topology exchange and security profile • Demonstration by October/November • NSI 2.0 Specification approved by end of 2012 • Children drafts follow soon after

10. Network Services Interface:Summary • Service Plane • Abstraction of multi-layer, multi-domain, network capabilities for Users, Applications, Network Administrators • Network Services Interface • Base interface between requestor agent and provider agent to request and get network services • Composable Services • Ability to create a higher-layer, customized service with multiple network services to meet an application need. • Connection Service • First network service being defined carried by NSI • Topology Service • Candidate for the next NSI service

11. Questions? imonga at es.net http://www.gridforum.org/gf/group_info/view.php?group=nsi-wg Thanks to the hard-working NSI contributors

12. Service Termination Points (STP) and Service Demarcation Points (SDP) STP a STP b TF • 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 • Transfer Function (TF) indicates the internal network capabilities Network SDP STP d STP c STP a = Network + ‘a’ (local identifier) N1/a N2/ X N1/ b N2/ y TF- Transfer Function

13. Service Plane Topology: Service Termination Points Service Plane represents the topological interconnects with STPs

14. Anatomy of a Connection Ingress Service Termination Point “A” Egress Service Termination Point “Z” Access section Access section Egress Framing Ingress Framing Transport section Transport framing The User (RA) specifies connection constraints (ostensibly externally measurable) for the access portion of the service instance The Network (PA) decides how to fulfil those constraints across the transport section.

15. Connection Service Protocol Requestor Provider reserve confirm Start time provision confirm In service Reserved period release confirm provision confirm In service • Behavior of the following set of messages nailed down: • Reserve • Provision • Release • Terminate • Query • Major difference from existing protocols • Explicit provision expected from Requestor • Provision can be before start time • Duration of reservation separated from “actual use” of resources

16. Recursive Framework scales over multiple Network Service Agents (NSA) Ultimate Requestor A Service Plane 1 Tree model 8 C B D 2 7 Chain model Chain model 5 6 H E F J G I 3 4 Tree model C B K L M E G F D I H J L Transport Plane K M