Multi-domain NetworkProvisioning using GLIF/feniusinterface
Jin Tanaka NICT/KDDI
Takahiro Miyamoto KDDIlabs
Evangelos Chaniotakis Esnet

SC09
18th November 2009

DCN Multi-domain ControlPlane
Web Interface

IDC•XML Request•Authentication•Schedule Reservation•Request VLAN
•Request Bandwidth

IDC•XML Request

IDC•XML Topology Exchange•XML Topology Exchange•Path Creation•Path Creation•Path Creation
DC/vlsr

DC/vlsr

DC/vlsr

DC/vlsr

DC/vlsr

Network2

DC/vlsr

Network3

Network1

User

End-to-End Ethernet VLAN Path

• Better Performance • Symmetric• Secure • Shorten Provisioning time• Efficient use of Network ResourceEnd SystemEnd System

Example of DCN Utility
NICT e-VLBI Correlation over DCN at SC08Deployment Status in Japan• Installation of DCN systems in JGN2plus and APANJP--Linux based IDC and DCs / DCN Software Suite version 0.5.2
Establish control plane(dcn.jgn2plus.jp) and data plane on anationwide
Connection test on multiple VLSRs in JGN2plus intra-domain
Connection test over inter-domain between JGN2plus and APAN-JP
Preparation works for the beginning of JGN2plus DCN pilot service

Tsukuba
IDCDCFukuokaKashimaOtemachi

nstallation of Control Plane Software
Web Interface

IDC•XML Request•Authentication•Schedule Reservation•Request VLAN
•Request BandwidthIDC•XML Request•XML Topology Exchange•XML Topology Exchange•Path Creation•Path Creation•Path Creation

DC/vlsr
DC/vlsr

DC/vlsr

DC/vlsr

DC/vlsr

Network2
Network1

DC/vlsrInternet2 or other
Network3
DCN

End-to-End Ethernet VLAN PathUser

End System
End System

Control Plane Software (1)Domain Controller
DC(Domain Controller)• DRAGON(Dynamic Resource Allocation via Gmpls Optiacl Network)--VLSR (Virtual Label Switched Router)-System Requirements for Installation

VLSR

JGN2plus and APAN-JPhardware
HP ProLiant DL360 G5Intel Xeon X5260 3.33GHz
DualCore
DDR2-667 2GB * 2
SAS146GB*2 (RAID1)
10/100/1000 base-T * 2-Open source implementation of GMPLS maintained byMAX, USC ISI EAST, and George Mason University• Zebra PC based control plane software• Provides GMPLS protocol support for devices which do not support
GMPLS• OSPF-TE, RSVP-TE• Provision the Ethernet Switch and SONET/SDH Switch• Switch setting method: SNMP, CLI, TL1, other script• Provisioning request via CLI, XML• DRAGON System- Linux BOX- RedHat Enterprise Base (Kernel version 2.4.2 or later)- Software Requirements• DRAGON Software package (VLSR, NARB, RCE, ASTB)• Dependence-package (SSH, GNU Compiles, Net-SNMP, libxml2,zlib-1.2.3)

Control Plane Software (2)Inter-Domain Controller
IDC(Inter-domain Controller)•OSCARS- Open source project maintained by Internet2 and ESnet- Accept circuit requests from users- Use IDC protocol which consist of web services as amessaging among Inter-domain- Web User Interface function for users- Book-ahead and manage the scheduling of circuits- System Requirements for Installation

JGN2plus and APAN-JPhardware
HP ProLiant DL360 G5Intel Xeon X5260 3.33GHz
DualCore
DDR2-667 2GB * 2
SAS146GB*2 (RAID1)
10/100/1000 base-T * 2-

• OSCARS System- Linux BOX- RedHat Enterprise (Kernel version 2.4.2 or later)- OSCARS Package Software- Third-Party Library and Package Requirements• OSCARS Package Software• MySQL5.0 / JDK5.0 / Tomcat 5.5 / Axis2 1.4.1/ Rampart 1.4.1/
Ant 1.7- SMTP(sendmail) for e-mail notification of circuit activity- NTP sourceG- lambda project overview
Joint project of NICT, AIST, KDDI R&D labs. and NTT.
 G-lambda project has been started in December 2004.
 The goal of this project is to define a standard web
services interface (GNS-WSI) between Grid resource
manager and network resource manager provided bynetwork operators.
An Example Service Model of Commercial GRID
This WorkUser
Application Service Provider(ASP)

Computing
Resource
Providers

StorageResource
Providers

1. Definition of Common
Interface between ASP
and Telecom Operators
2. Scheduled Provisioning ofLambda Path between
computing resources.

Network Resource
ProvidersTelecom
Operator A

Telecom
Operator Z• User access• NW resources integrity

Demonstration @ GLIF2006
CH1(SL)KMF

FUK

VC1(NCSU)

RA1(MCNC)

BT1(LSU)
PelicanBackup

TKB
6509

(UR1)
0.11a.6

(UO2)
(UO1)

4G

X15G

X1N 5G
KAN(UO3)
0.11a.2

(UR2)

(UO4)
X1U

BT2(LSU)
Santaka

10.16a.2

(UR3)
X2N
2G

X1S

X2

LA
Foundry

X2S
AKB

OSA
NR3
KHN

0.11a.7

LA1(Caltech)

BT3(LSU)
Viz
MachineClientResource Map
Simulation result

Time table (clusters)

Time table (networks)
13G-lambda/Enlightened middleware coordination diagram
Japan
Application

EL
App. Launcher

EL
Grid Resource
Coordinator

EL→GLwrapperGL
Grid Resource
Scheduler

CRM

CRM

Cluster Cluster

CRM

HARC
Acceptor

NRM

USJAPAN

GL→EL
wrapper

NRM

NRM

US
Application

CRM

CRM

CRM

CRM

CRM

Cluster Cluster

Cluster

Cluster Cluster

Cluster

KREOnet

Fenius