1 / 8

NDN Demo May 2013 China

NDN Demo May 2013 China. John DeHart. NDN Demo Status (3/22/13). EC2 Gateway nodes working

darius
Download Presentation

NDN Demo May 2013 China

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NDN DemoMay 2013China John DeHart

  2. NDN Demo Status (3/22/13) • EC2 Gateway nodes working • Still a snag in that they don’t come up first time. I have to restart ccnx/OSPFN at least once to get them fully up. They get routes from the NDN testbed but the testbed doesn’t always get their routes until they are “fully up”. • Need one connection from PKU to Tokyo to complete connectivity. • NDN monitoring via CCNX is working • We are running it on our WashU node right now. • Will extend that to SPP nodes and EC2 nodes in next day or so. • Then we can decide whether to extend it to nodes at other sites. • New Routing protocol coming soon • We will work with Memphis folks to try out their new Routing protocol to try to work it into the testbed in time for the demo. • Lineup of Apps: • Live text chat • Firefox • Stored video playback with up to 1000 headless clients plus Patrick in Beijing • Security App • Live video with remote studio control • We should be seeing a demonstration of this from UCLA soon • UCLA plans to have a band in the studio at the time of the demo • Next Friday: Do as much of demo as possible • Including instances running apps in all regions

  3. NDN Demo ToDo List(4/03/13) • DONE: Add NDN monitoring via CCNX to SPPs • DONE: Add NDN monitoring via CCNX to EC2 gateways • DONE: Add connection from Tokyo to PKU • DONE: Add AMIs for foreign EC2 locations for running app instances. • Just more testing to do • DONE: New chat app: ccnc (ADDED: Does not include user name in text display.) • DONE: Build up scripts for actual demo • DONE: Ndnvideo: check on NEU, REMAP and UCI instances off their gateways are working… • DONE: Foreign sites don’t seem to always work. Timing? • DONE: Script for starting gateways. • DONE: Why does Singapore-Sydney, Sydney-SaoPaulo show 0/0 almost all time. • multipath ordering in ospf.conf related. Those paths would never be chosen because they are long

  4. NDN Demo ToDo List(4/03/13) • In Progress: Work with Memphis on new Routing protocol. • Our node installed, they are testing. • Not likely to be included in demo. • In Progress: Security demo • In Progress: Firefox demo • Add some more interesting content. Added some WU images. • Coordinate with someone at PKU/Beijing to try video from there. • Next Friday: Patrick: do as much of demo as possible • Haowei gone 4/12 – 4/21 • In Progress: Add PKU instances for ndnvideo • In Progress: Investigate usage on PKU and Tokyo links • related to OSPF multipath-order • Also, Michael Plass is working on bug fixes that might alleviate the multiple copies of content. • In Progress: Coordinate with Tian to do some testing while he is in China • What ISP does PKU go through? • Alex: Buffering algorithm for ndnvideo? • It adapts to round trip times. • Check on direction of bandwidth numbers on links on ndnmap. • Running key verify through Tokyo gateway.

  5. NDN/ccnx Plans • Demo in China in May • May 15 2013, 3:45 PM Beijing Time • 2:45AM St. Louis Time • Goals from Patrick, as of 1/24/2013 • Demo size and scope • >1000 devices • 3 continents: US, Europe, Asia • 5 continents: North America, Europe, Asia, South America, Australia • Applications and services • All the apps from the March 2012 demo • TODO: Incorporate new apps/services from J Burke and others • TODO: An ndn-based logging and monitoring infrastructure • Security and authentication • TODO: All components using the “new scheme” for organizing keys • Scalable forwarding • TODO: Use “Core”, “Edge” and “Device” perspective to organize the devices into a topology • TODO: “Core” components, such as SPPs, using Wash U forwarding code in place of ccnx • People involved in Demo development: • John, Jyoti, Haowei, Hila, Tian

  6. NDN Demo May 2013 • Old Applications from GEC-13 Demo (March 2012) • Ccnchat • Interactive • Robochat • Bulk file transfer • Recorded video playback • Live video feed (from?) • New Applications: • NDN dropbox (UCLA: Burke) • Web server javascript (UCLA: Burke) • Others? • Monitoring • ndnmap.arl.wustl.edu • NDN-based Logging and Monitoring • Core vs. Edge NDN nodes • Running NDN gateway routers on AWS EC2 Instances • And monitoring bandwidth via ndnmap

  7. Topics We Need to Address • Each of these will probably need a separate group presentation in the very near future. • Sync (3/1) Hila • NDN-based Logging and Monitoring (3/1 or 3/8) Hila and Jyoti • New Applications (3/8) Jyoti and John • Key Management (2/22) Haowei and John • What is the vision? • What is the current state of development and deployment? • Core Node (3/15) Haowei and Tian

  8. AWS Usage • AWS EC2 • Regions (5 Continents!) • US-EAST-1: Virginia • US-WEST-1: N. California • US-WEST-2: Oregon • EU-WEST-1: Ireland • AP-SOUTHEAST-1: Singapore • AP-SOUTHEAST-2: Sydney • AP-NORTHEAST-1: Tokyo • SA-EAST-1: Sao Paolo • Current Instance Limits • 300 at each of the US sites • 20 at each of the other sites • Current total number of active instances: 1000 • AMI built for ccnx-0.7.0 (in US regions, others coming soon) • AWS S3 • Used to store the AMI image • AWS Identity and Access Management (IAM) • One account may have multiple users • Users can be grouped (e.g. Admin, Power User, User, Tester, …) • Each group can have different policies controlling access and privileges. • AWS Cloudformation • Can be used for deploying resources on AWS

More Related