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 • 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 2

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

DCN Multi-domain Control Plane Global Topology of DCN Web Interface • XML Topology registration • PerfSONAR Topology service • XML Topology • XML Topology • XML Topology IDC IDC • XML Request • XML Request • Authentication IDC • Schedule Reservation • Path Creation • Path Creation • Path Creation • Request VLAN • Request Bandwidth DC/vlsr DC/vlsr DC/vlsr DC/vlsr DC/vlsr DC/vlsr Network2 Network3 Network1 End-to-End Ethernet VLAN Path User • Better Performance • Symmetric • Secure • Shorten Provisioning time • Efficient use of Network Resource End System End System 4

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

Installation of Control Plane Software Global Topology of DCN Web Interface • XML Topology registration • PerfSONAR Topology service • XML Topology • XML Topology IDC • XML Request • XML Request • Authentication IDC • Schedule Reservation • Path Creation • Path Creation • Path Creation • Request VLAN • Request Bandwidth DC/vlsr DC/vlsr DC/vlsr DC/vlsr DC/vlsr DC/vlsr Internet2 or other Network2 Network3 Network1 DCN End-to-End Ethernet VLAN Path User End System End System 6

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 VLSR • 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 JGN2plus and APAN-JP hardware - Linux BOX - HP ProLiant DL360 G5 - RedHat Enterprise Base (Kernel version 2.4.2 or later) - Intel Xeon X5260 3.33GHz - Software Requirements DualCore - DDR2-667 2GB * 2 • DRAGON Software package (VLSR, NARB, RCE, ASTB) - SAS146GB*2 (RAID1) • Dependence-package (SSH, GNU Compiles, Net-SNMP , - 10/100/1000 base-T * 2 libxml2, zlib-1.2.3) 7

Installation of Control Plane Software Global Topology of DCN Web Interface • XML Topology registration • PerfSONAR Topology service • XML Topology • XML Topology IDC IDC • XML Request • XML Request • Authentication IDC • Schedule Reservation • Path Creation • Path Creation • Path Creation • Request VLAN • Request Bandwidth DC/vlsr DC/vlsr DC/vlsr DC/vlsr DC/vlsr DC/vlsr Network2 Network3 Network1 End-to-End Ethernet VLAN Path User End System End System 8

Control Plane Software -2- Inter-Domain Controller • OSCARS IDC(Inter-domain Controller) - 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 - System Requirements for Installation • OSCARS System - Linux BOX - RedHat Enterprise (Kernel version 2.4.2 or later) - OSCARS Package Software JGN2plus and APAN-JP hardware - Third-Party Library and Package Requirements - HP ProLiant DL360 G5 • OSCARS Package Software - Intel Xeon X5260 3.33GHz • MySQL5.0 / JDK5.0 / Tomcat 5.5 / Axis2 1.4.1/ Rampart DualCore - DDR2-667 2GB * 2 1.4.1/ Ant 1.7 - SAS146GB*2 (RAID1) - SMTP(sendmail) for e-mail notification of circuit activity - 10/100/1000 base-T * 2 - NTP source 9

JGN2plus DCN 10

DCN Use Case (1) JP-US e-VLBI Correlation 11

Kashima, JP Metsähovi, FI Austin, US DCN Dynamic Circuit Network Example of DCN Utility NICT e-VLBI Correlation over DCN at SC08 12

NICT SC08 Network Topology MPLS/L2VPN 13

DCN Use Case (2) JP-TH Telemedicine 14

DCN Telemedicine demo between Japan and Thailand 15

DCN Telemedicine demo between Japan and Thailand 16

DCN Use Case (3) JP-KR Live TV Broadcasting 17

Network Diagram of DCN demo for Broadcasting 18

Network Diagram of DCN demo for Broadcasting KOREN 19

Future Internet Testbed and DCN 20

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

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 other control framework • MAX + PlanetLab, GpENI • CoreLab + JGN2plus DCN 22

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 Pictures from GEC8 23

Demo over DCN/ION at GENI Engineering Conference  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 PlanetLab PlanetLab GEC7 Venue JGN2plus I2 ION MAX KOREN 24

MAX DCN Demo at GEC7 25

Collaboration with CoreLab Japan • 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 of them 26

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.) Node Sliver: Programmable VM CoreLab 27