Network Service Interface (NSI)
Inder Monga
Co-chair, Network Services Interface Working Group
OGF
Lawrence Berkeley National Laboratory
U.S. Department of Energy | Office of Science
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
Lawrence Berkeley National Laboratory
U.S. Department of Energy | Office of Science
Abstraction
Present a simple interface to the external world
Lawrence Berkeley National Laboratory
U.S. Department of Energy | Office of Science
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
Lawrence Berkeley National Laboratory
U.S. Department of Energy | Office of Science
Network Service Framework concepts
Network Services Interface (NSI)
Network
Service
A
Network
Service
B
Network
Service
A
Service
Service
NSI Provider
Provider
Agent (PA)
NSI Requestor
Requestor
Agent (RA)
NRM
Network
Service
B
NSA
NSA
NRM
Service Plane
Local
Resources
Transport Plane
* Slides contain animation, does not show in pdf
Lawrence Berkeley National Laboratory
Local
Resources
NSA = Network Services Agent
NRM = Network Resource Manager
U.S. Department of Energy | Office of Science
NSI Connection Service
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
Slide from jerry Sobieski
Lawrence Berkeley National Laboratory
U.S. Department of Energy | Office of Science
How NSI-CS Works…
The user application
RA
PA
Appl
NSA
NSA
NSA
RM
RM
NSA
RM
Slide from jerry Sobieski
Lawrence Berkeley National Laboratory
U.S. Department of Energy | Office of Science
Congratulations!
7 independent interoperable implementations
KRLight.ets
Daejeon
Dynam icKL
A
GLORIAD.ets
KRLight
A
A
Chicago
OpenNSA
WIX.ets
NorthernLight.ets CzechLight.ets
Washington
OpenNSA
Copenhagen
OpenNSA
A
HKOEP.ets
A
Fujim ino
G-LAMBDA-K
GLORIAD
JGN-X
A
NORDUnet +
SURFnet
Hong Kong
KDDI-Labs.ets
Prague
DRAC
CESNET
Pionier.ets
ACE
A
Poznan
JGNX.ets
StarLight.ets
NetherLight.ets
Tokyo
G-LAMBDA-K
Chicago
OpenNSA/ Argia
Am sterdam
DRAC
US LHCnet
Pionier
A AutoBAHN
GEANT
A
A
AIST.ets
ESnet.ets
Tsukuba
G-LAMBDA-A
Chicago
OSCARS
UvALight.ets
University of Am s.
OpenNSA
GEANT.ets
Paris
AutoBAHN
NSI Networks (“A”=Aggregator)
NSI peerings (SDPs) unless otherwise indicated these are vlans 1780-1783
Lawrence Berkeley National Laboratory
U.S. Department of Energy | Office of Science
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
Lawrence Berkeley National Laboratory
U.S. Department of Energy | Office of Science
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
Lawrence Berkeley National Laboratory
U.S. Department of Energy | Office of Science
Questions?
imonga at es.net
http://www.gridforum.org/gf/group_info/view.php?group=nsi-wg
Thanks to the hard-working NSI
contributors
Lawrence Berkeley National Laboratory
U.S. Department of Energy | Office of Science
Service Termination Points (STP) and
Service Demarcation Points (SDP)
STP a
STP b
SDP
N1/a
N2/ X
N1/ b
N2/ y
TF
Network
STP d
STP c
STP a = Network + ‘a’ (local
identifier)
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
Lawrence Berkeley National Laboratory
SDP = interconnected STPs
Abstracts the connectivity between
two STPs
Transfer Function (TF) indicates the
internal network capabilities
TF- Transfer Function
U.S. Department of Energy | Office of Science
Service Plane Topology: Service
Termination Points
Inter-Network representation of network resources
STP a/STP b
STP g
STP c/STP f
Network W
TF
SDP
TF
SDP
Network X
STP e
STP d
Dynamic Connection
Network
Y
SDP
Network Z
Network W
STP k
STP - Service Termination Point
TF - Transfer Function
SDP - Service Demarcation Point
STP h/STP j
Link
Host
EP - Edge point
Node
EP g
EP a
EP b
EP c
EP f
Node
EP k
Node
EP h
Host
EP j
EP d
EP e
Intra-network representation of network resources
Service Plane represents the topological interconnects with STPs
Lawrence Berkeley National Laboratory
U.S. Department of Energy | Office of Science
Anatomy of a Connection
Ingress
Service Termination Point
“A”
Access section
Ingress Framing
Egress
Service Termination Point
“Z”
Transport section
Transport framing
Access section
Egress 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.
Lawrence Berkeley National Laboratory
U.S. Department of Energy | Office of Science
Connection Service Protocol
Requestor
Behavior of the following set of
messages nailed down:
Provider
reserve
confirm
• Reserve
• Provision
Start
time
provision
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
Lawrence Berkeley National Laboratory
release
In service
• Query
confirm
confirm
provision
confirm
In service
• Terminate
Reserved
period
• Release
U.S. Department of Energy | Office of Science
Recursive Framework scales over multiple
Network Service Agents (NSA)
A
Ultimate
Requestor
1
Service Plane
8
B
2
Tree model
C
7
Chain model
5
6
E
F
G
3
D
Chain model
H
J
I
4
Tree model
K
F
M
C
B
E
L
G
Transport Plane
Lawrence Berkeley National Laboratory
D
I
H
K
L
J
M
U.S. Department of Energy | Office of Science