NSI Standards Update

LHCONE Workshop

CERN (Geneva, CH)

Feb 10-11, 2014

Inder Monga

Lawrence Berkeley National Laboratory U.S. Department of Energy | Office of Science

NSI Terminology

2

Network Resource Manager (NRM)NRM

Requesting Agent (uRA)

Provider Agent (uPA)

Network Services Interface (NSI)

Network Services Agent (NSA)

NSA

NSA

NSI Network Service Domain

Lawrence Berkeley National Laboratory U.S. Department of Energy | Office of Science

Standards

• NSI 2.0 specification release for public comment in December 2013• http://redmine.ogf.org/projects/editor-pubcom/boards/18

• Next Steps• Formalize NSI extensions to NML topology• Topology distribution mechanism/service

• NSI 3.0• Extensions to the protocol to add new services

3

Lawrence Berkeley National Laboratory U.S. Department of Energy | Office of Science

GLIF NSI Implementation WG

• Production network service >> inter-domain standards

• Bridge the missing gap in GLIF, where many NRENs participate

• Work items planned• Ethernet Service schema • Error handling

• Best practices, error codes, troubleshooting, etc.• AAI – Authentication, Authorization and Identity

• User identity and user roles and policy • Best practice document with use-cases and examples

4

OSCARS Update

LHCONE Workshop

CERN (Geneva, CH)

Feb 10-11, 2014

OSCARS Development Team

Lawrence Berkeley National Laboratory U.S. Department of Energy | Office of Science

OSCARS Introduction

1. Multi-domain, Dynamic Circuit Service within ESnet• Includes NRM and NSA• Implements Inter-Domain Control Protocol (IDCP) and Network

Services Interface (NSI) multi-domain protocols• GUI-based user-interface, and roles/responsibilities

2. Open Source project • 40+ networks have OSCARS deployed in some form (production,

prototype, tests)• In many cases, have to test their own NRM functions (ex. OESS)• Getting NSI is matter of getting latest software

6

Lawrence Berkeley National Laboratory U.S. Department of Energy | Office of Science7

Differences between IDCP and NSI(Request Workflow)

• IDCs are both Requester and Providers• IDCP uses the “Chain” model

• NSAs are 1 of 3 types1. Ultimate Provider Agent (uRA)2. Aggregator Agent3. Ultimate Provider Agent (uPA)

• NSI supports both the “Chain” and “Tree” model

IDC

Network Resource Manager

IDC

Network Resource Manager

IDC

Network Resource Manager

Lawrence Berkeley National Laboratory U.S. Department of Energy | Office of Science

NSI Bridge in OSCARS v0.6

Notification Broker• Manage

Subscriptions• Forward

Notifications

AuthN• Authentication

Resource Manager• Manage

Reservations• Auditing

Coordinator• Workflow

Coordinator

PCE• Constrained Path

Computations

Topology Bridge• Topology

Information Management

IDC API• Manages External

WS Communications with other IDCs

using IDCP

Path Setup• Network Element

Interface

Lookup• Lookup service

AuthZ*• Authorization

• Costing

*Distinct Data and Control Plane Functions

Web Browser User Interface

OSCARS Inter-Domain Controller (IDC)

Use

rsU

ser

App

sID

Cs*

(ID

CP

)

Loca

l Net

wor

k R

esou

rces

8

NSI Bridge• Manages External

WS Communications with other NSAs

using NSI CS

NSAs* (NSI CS)

* IDC/NSA can be used interchangeably in this context

Lawrence Berkeley National Laboratory U.S. Department of Energy | Office of Science

• IDCP interactions with OSCARS will remain unchanged

• NSI Bridge is designed to enable OSCARS to be an ultimate Provider NSA (uPA)

• Scope of NSI control will only be intra-domain• NSI inter-domain requests will have to go via an Aggregator NSA

(i.e. SURFnet/ESnet Aggregator instance)

• NSI Bridge is responsible for the following:• NML-WG NSI topology -> NM-WG Control Plane topology• Maintaining NSA state machines (RSM, PSM, LSM) and

transitioning the NSA state machines based on NSI request from the Aggregator NSA, and IDC replies

• Coordinate NSA and IDC timeouts to maintain correct dependencies

9

NSI Bridge Design Decisions

Lawrence Berkeley National Laboratory U.S. Department of Energy | Office of Science

OSCARS Timelines

• Implementation of OSCARS NSI Bridge to support of NSI CS v2.0 (r99) (4Q13)

• Deployment of NSI CS v2.0 (r99) in production infrastructure; ESnet*, MANLAN (4Q13 – current)

• Update of OSCARS NSI Bridge to support NSI CS v2.0 (ratified) (1Q14)

• OSCARS enhancements to support ESnet service extensions• Soft/hard enforcement of reservation bandwidth (4Q13)• “Zero” bandwidth best effort VCs (1Q14)• VC protection/restoration (1Q14)• OpenFlow (including multi-layer transport SDN) (3Q13)

*NB: Topology limited to A-GOLE demo STPs

10

Lawrence Berkeley National Laboratory U.S. Department of Energy | Office of Science

OSCARS Information

• OSCARS v0.6 Project (including NSI Bridge)• http://code.google.com/p/oscars-idc/

• OSCARS Mailing Lists• oscars-announce (

https://listserv.es.net/mailman/listinfo/oscars-announce )• This list will be used to announce general information such as

upcoming releases and roadmaps.• oscars-dev (https://listserv.es.net/mailman/listinfo/oscars-dev )

• This list will be used to discuss code development issues, track bugs, and report code commits.

• oscars-users (https://listserv.es.net/mailman/listinfo/oscars-users )• This list is for the user community to share deployment and usage

experiences, as well as submitting enhancement requests and reporting bugs.

• This mailing list is in the process of being renamed to oscars-support

11

Lawrence Berkeley National Laboratory U.S. Department of Energy | Office of Science

Questions?

12

chin@es.net | Chin Guok