Utilization of DCN/ION for Infrastructure of Future Internet Testbed - - PowerPoint PPT Presentation

utilization of dcn ion for infrastructure of future
SMART_READER_LITE
LIVE PREVIEW

Utilization of DCN/ION for Infrastructure of Future Internet Testbed - - PowerPoint PPT Presentation

Utilization of DCN/ION for Infrastructure of Future Internet Testbed Jin Tanaka KDDI/NICT APAN-JP/JGN2plus/TEIN3-JP NOCs Aug. 11 2010 APII / Future Internet Testbed WG in 30th APAN Meeting Hanoi, Vietnam 1 Outline 1. DCN Overview


slide-1
SLIDE 1

Jin Tanaka

KDDI/NICT APAN-JP/JGN2plus/TEIN3-JP NOCs

  • Aug. 11 2010

APII / Future Internet Testbed WG in 30th APAN Meeting Hanoi, Vietnam

Utilization of DCN/ION for Infrastructure of Future Internet Testbed

1

slide-2
SLIDE 2

2

Outline

  • 1. DCN Overview
  • What’s and Why DCN?
  • Multi-domain Control Plane Softwares
  • JGN2plus Dynamic Circuit Network
  • 2. Use Cases and New Technology
  • eVLBI
  • Telemedicine
  • Live TV Broadcasting
  • 3. Future Internet Testbed and DCN
  • Infrastructure for Future Internet Testbed
  • GENI Demo over DCN
  • Collaboration of CoreLab and DCN
  • Global Dynamic Circuit Network
  • 4. Next Step and Future Plan
  • DCN/ION activity
  • DCN deployment on AP
  • For Future Internet Testbed
slide-3
SLIDE 3

Why Dynamic Provisioning?

  • Network is a “Resource”

– Network itself should be also considered as a “resource” and bandwidth should be allocated to users appropriately

Dynamic Network Provisioning

  • Can select different end-points, bandwidths, and durations
  • Can create flexible network meet to special requirements related to

quality of service, for example jitter requirements

  • Resources are only used when needed
  • Efficient – unused resources can be used by others
  • No charge when not in use
  • Reduce operational expense
  • Contain elements of Green IT

3

slide-4
SLIDE 4

DCN Multi-domain Control Plane

End System

Network2 Network1 Network3

DC/vlsr DC/vlsr DC/vlsr DC/vlsr DC/vlsr DC/vlsr

IDC IDC IDC

End System

User

  • Authentication
  • Schedule Reservation
  • Request

VLAN

  • Request Bandwidth
  • XML Request
  • XML Request
  • Path Creation
  • Path Creation
  • Path Creation

Web Interface

End-to-End Ethernet VLAN Path

  • Symmetric
  • Better Performance
  • Secure
  • Shorten Provisioning time
  • Efficient use of Network Resource

4

  • XML Topology registration
  • XML Topology
  • XML Topology
  • PerfSONAR

Topology service

  • XML Topology

Global Topology of DCN

slide-5
SLIDE 5

Benefits of Using DCN

  • Enable user to create on demand end-to-end L2

VLAN path

  • User or operators can provision

VLAN path through Web Interface by themselves

  • Save significant network provisioning time
  • Possible use for interactive real-time application, events over the network
  • Provides speedy implementation of research activities and experiments
  • Reduce the burden of multi-domain network coordination
  • No need to coordinate the path among multiple networks in each use case
  • Facilitate the smooth implementation of international collaboration researches
  • Schedule management of finite network resources
  • IDC scheduler prevents the network performance degradation by cross-traffic collision
  • Especially effective in stationary and huge data transmission
  • Improvement of network performance
  • MPLS, SONET/SDH provides dedicate circuit and secured the bandwidth
  • Avoids a negative impact of cross-traffic in the shared-network-specific
  • “DCN web service API” to request circuits
  • DCN API can be used into your applications or scripts
  • DCN API enables users to develop the original client software appropriate for own

application

5

slide-6
SLIDE 6

End System

Network2 Network1 Network3

DC/vlsr DC/vlsr DC/vlsr DC/vlsr DC/vlsr DC/vlsr

IDC IDC

End System

User

  • Authentication
  • Schedule Reservation
  • Request

VLAN

  • Request Bandwidth
  • XML Request
  • XML Request
  • XML Topology registration
  • XML Topology
  • Path Creation
  • Path Creation

Web Interface

End-to-End Ethernet VLAN Path

Internet2 or other DCN

  • Path Creation

Installation of Control Plane Software

6

  • XML Topology
  • PerfSONAR

Topology service Global Topology of DCN

slide-7
SLIDE 7

Control Plane Software -1-

Domain Controller

DC(Domain Controller) • DRAGON(Dynamic Resource Allocation via Gmpls Optiacl Network)

  • Open source implementation of GMPLS maintained by MAX,

USC ISI EAST, and George Mason University

  • VLSR (Virtual Label Switched Router)
  • 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
  • System Requirements for Installation
  • 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)

VLSR

7

JGN2plus and APAN-JP hardware

  • HP ProLiant DL360 G5
  • Intel Xeon X5260 3.33GHz

DualCore

  • DDR2-667 2GB * 2
  • SAS146GB*2 (RAID1)
  • 10/100/1000 base-T * 2
slide-8
SLIDE 8

End System

Network2 Network1 Network3

DC/vlsr DC/vlsr DC/vlsr DC/vlsr DC/vlsr DC/vlsr

IDC IDC IDC

End System

User

  • Authentication
  • Schedule Reservation
  • Request

VLAN

  • Request Bandwidth
  • XML Request
  • XML Request
  • Path Creation
  • Path Creation
  • Path Creation

Web Interface

End-to-End Ethernet VLAN Path

Installation of Control Plane Software

8

  • XML Topology registration
  • XML Topology
  • XML Topology
  • PerfSONAR

Topology service Global Topology of DCN

slide-9
SLIDE 9

IDC(Inter-domain Controller)

  • System Requirements for Installation
  • 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

9

JGN2plus and APAN-JP hardware

  • HP ProLiant DL360 G5
  • Intel Xeon X5260 3.33GHz

DualCore

  • DDR2-667 2GB * 2
  • SAS146GB*2 (RAID1)
  • 10/100/1000 base-T * 2

Control Plane Software -2-

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 a

messaging among Inter-domain

  • Web User Interface function for users
  • Book-ahead and manage the scheduling of circuits
slide-10
SLIDE 10

JGN2plus DCN

10

slide-11
SLIDE 11

DCN Use Case (1)

JP-US e-VLBI Correlation

11

slide-12
SLIDE 12

Example of DCN Utility

NICT e-VLBI Correlation over DCN at SC08

Kashima, JP Metsähovi, FI Austin, US

DCN

Dynamic Circuit Network

12

slide-13
SLIDE 13

NICT SC08 Network Topology

MPLS/L2VPN 13

slide-14
SLIDE 14

DCN Use Case (2)

JP-TH Telemedicine

14

slide-15
SLIDE 15

DCN Telemedicine demo between Japan and Thailand

15

slide-16
SLIDE 16

DCN Telemedicine demo between Japan and Thailand

16

slide-17
SLIDE 17

DCN Use Case (3)

JP-KR Live TV Broadcasting

17

slide-18
SLIDE 18

18

Network Diagram of DCN demo for Broadcasting

slide-19
SLIDE 19

KOREN

19

Network Diagram of DCN demo for Broadcasting

slide-20
SLIDE 20

Future Internet Testbed and DCN

20

slide-21
SLIDE 21

Infrastructure for Future Internet Testbed

  • Presently-available network technology
  • Layer3 : IP Packet network
  • Layer2 : Ethernet

VLAN

  • Wireless : WiMax, Sensor
  • Optical will soon line-up
  • Still few global connection
  • Features of desired testbed network
  • Securing the network resource/slice for experiment

within limited resources

  • Doesn't affect the other research and experiments
  • Dedicated network, Isolated network
  • Controlled Network by the associated user
  • Programmable
  • Routing, Bandwidth control
  • Global, Multi-domain
  • Interoperability

21

slide-22
SLIDE 22

DCN/ION and Future Internet Testbed

  • DCN/ION is not Future Internet technology
  • Infrastructure
  • DCN/ION is one of the infrastructure technology to run an

experiment of Future Internet

  • DCN/ION could promote the federation of future Internet research
  • Internet2 ION
  • JGN2plus DCN
  • KOREN DCN
  • Control Plane Software
  • DCN/ION’s API facilitates a integration/aggregation of DCN/ION with
  • ther control framework
  • MAX + PlanetLab, GpENI
  • CoreLab + JGN2plus DCN

22

slide-23
SLIDE 23

Internet2 ION Service for GENI

  • Internet2 ION backbone service transitioning

from Ciena dedicated wave to Juniper MPLS tunnel

  • Internet2 10 Gbps MOU expires after GEC8
  • Separate 1 GE connections for each

ProtoGENI and OpenFlow backbone node with transparent MPLS tunnels between nodes

  • 1 GE connections for new ShadowNet nodes
  • 1 GE ION link for access at each node for

layer2 access

  • Use of ION for GENI
  • OpenFlow : 5

VLANs

  • ProtoGENI : 3

VLANs

  • MAX, GpENI (Univ. of Kansas, etc.) : Occasionally

23 Pictures from GEC8

slide-24
SLIDE 24

 7th GEC (March 2010)

  • MAX, Cluster B
  • KOREN/JGN2plus/Inernet2 ION/MAX connectivity test
  • Preparation for integration of PlanetLab

Vitalization and Network Vitalization

  • Set up a host on KOREN/JGN2plus/MAX on a specific

VLAN, with a Static IP address

  • Set up a dynamic circuit and demonstrate connection via ping test

Demo over DCN/ION at GENI Engineering Conference

24

KOREN JGN2plus I2 ION MAX PlanetLab PlanetLab

GEC7 Venue

slide-25
SLIDE 25

MAX DCN Demo at GEC7

25

slide-26
SLIDE 26
  • Initial Phase
  • Implement

VLAN tagged capability in virtual interface on CoreLab

  • DCN SW creates different bandwidth circuit associated with different

VLAN ID

  • Create Isolate bandwidth network through tagged

VLAN between Corelab Nodes

  • Challenge to Integrate of Dynamic Circuit and CoreLab Slice

Providing

  • Plan on developing the integrated interface to provision the dynamic circuit

between CoreLab nodes using OSCARS API

  • Possibly integrate the single client WBUI to create slice and underlying path
  • f them

Collaboration with CoreLab Japan

26

slide-27
SLIDE 27

CoreLab

Shares DNA with PlanetLab (w/ more Net Virt Support) Creates slices across Japan (24+ nodes) Overlaid on multiple backbone networks Extending to Asian regions (plus part of U.S.)

27

Node Sliver: Programmable VM

slide-28
SLIDE 28

DCN SW

DCN VLAN (vlan1)

Implementation of DCN/VLAN in CoreLab

28

CoreLab node2

NOX

Sliver 2

user kernel

eth0

vOFS

eth0 eth1 eth2

gtap2

gtap1

Sliver 1

vOFS

eth0 eth1 eth2

gtap2

gtap1

Open vSwitch eth0.vlan1 eth0.vlan2 CoreLab node1

NOX

Sliver 2

user kernel

eth0

vOFS

eth0 eth1 eth2

gtap2

gtap1

Sliver 1

vOFS

eth0 eth1 eth2

gtap2

gtap1

Open vSwitch eth0.vlan1 eth0.vlan2

DCN VLAN (vlan2) Best-Effort VLAN (default)

DCN SW

slide-29
SLIDE 29

29

KOREN DCN JGN2plus DCN

Otemachi/Tokyo Hakusan/Tokyo Daejong Fukuoka Gwangju

CoreLab over DCN between Japan and Korea

Experiment has just begun!

slide-30
SLIDE 30

30

CoreLab over Global Dynamic Circuit Network

DCN/ION

slide-31
SLIDE 31

 To be a Network Service Layer on R&E network

  • Leads to the promotion of the international collaboration on R&E networks
  • Can create flexible network meet to special requirements of Science,

Education, and Engineering applications

  • Interconnect Future Internet Testbeds, and accelerate a global research

experiment of Future Internet

Global Dynamic Circuit Network

  • ver Multi-domain

31

Science ¡& ¡Education ¡Data ¡ Future ¡Internet ¡Research

DCN/ION

Underlying R&E Networks

slide-32
SLIDE 32

 DCN/ION Activity

  • Upgrading IDC/OSCARS software to v0.6
  • Multi-point enable, MPLS tunnel based
  • Data/Control Plane connections with NTT
  • lab DCN
  • Development of application associated with Tailed Walled Display
  • Fenius Global demo with GLIF members at SC10

Next Steps and Future Work

32

NetherLight CERNLight MANLAN UvA Internet2 ESnet StarLight NorthernLight NORDUnet SC10 JGN2+ G-lambda

Fenius Topology Plan for SC10 Provided by Evangelos Chaniotakis@ESnet

slide-33
SLIDE 33

 DCN deployment over APAN

  • Inter-domain connection between Thailand
  • DCN/ION training workshop

 For the Future Internet Testbed

  • Development of User Interface Integrated DCN with CoreLab
  • Create a virtual circuit from CoreLab WBUI
  • Cooperation to implementation of MAX GENI Aggregate Manager
  • Interoperation of the PlanetLab control framework and IDC based

international dynamic networks

  • Planning to demo at 9th GENI Engineering Conference

Next Steps and Future Work

33

slide-34
SLIDE 34

Reference URLs

  • DCN Software Suite

https://wiki.internet2.edu/confluence/display/DCNSS/Home

  • OSCARS

http://www.es.net/oscars/

  • OSCARS Web Services Specification

https://wiki.internet2.edu/confluence/display/CPD/OSCARS+Web+Service+Definition

  • DRAGON

http://dragon.maxgigapop.net/twiki/bin/view/DRAGON/WebHome

  • DCN Working Group Wiki

https://spaces.internet2.edu/display/DCN/Home

  • PerfSONAR

http://www.perfsonar.net/

  • SC08

http://sc08.supercomputing.org/

  • SC09

http://sc09.supercomputing.org/

  • GLIF GNI task force

http://www.glif.is/meetings/2009/tech/chaniotakis-gni.pdf

  • MAX

http://wiki.maxgigapop.net/twiki/bin/view/MAX/WebHome

  • CoreLab

http://www.corelab.jp/

  • GENI

http://www.geni.net/ 34