CUTEi: Container-Based Unified Testbed for ICN

Transcription

1 CUTEi: Container-Based Unified Testbed for ICN Hitoshi Asaeda National Institute of Information and Communications Technology (NICT)

2 Information-/Content-Centric Networking (ICN/CCN) 2 Efficient content access without depending on server/content location From IP address based communications to content name based communications From server based communications to content based communication Better performance to retrieve contents From server distribution to content (or cache/repository) distribution Content retrieval from closest cache Flexible data forwarding Naturally support one-to-many or many-to-many transmission

3 3 In-Network Cache Interest (request) festival.img Data (content data) Router A Caching router B C D E F G J A B CCN s concept Name-based routing Content name for data retrieval / transmission ID / Location independent content access In-network cache Performance improvement Resource (or cost) reduction

4 Functional Components for ICN 4 Naming Global unique content IDs Content / cache resolver (or discovery mechanism) In-network cache From network s perspective:on-path caching / off-path caching From application s perspective:content type based algorithm Name-based routing Intra-domain vs. Inter-domain Transmission One-to-one / one-to-many / many-to-many Security From channel encryption to content or cache encryption Cache protection / integrity Mobility Prototype implementation Experiments in a large scale testbed

5 Motivation to Develop ICN Testbed 5 Reality Experiments that would actually be observed in testbeds must be as close as possible to those in real deployments Virtualization Virtualized network and resources to support a large number of users Resource and process isolation Isolation of resource usage and traffic for different testbed users Robustness Robustness of testbed nodes to increase the usability of users experiments Usability and extensibility Cost reduction for users to set up or configure experimental environment to test novel protocols, from the network layer to the upper application layer ICN-friendly Accommodate tests for the special features of ICN, e.g., name-based routing, in-network caching, etc.

6 6 Container-Based Unified Testbed Design Testbed node (i.e., base OS): Linux (Ubuntu is recommended) installed on VM or PC/workstation node (i.e., user space): Linux Container (LXC) based logical space Concept ICN (basically, CCN/NDN based) experiments All required components (e.g., compiler, library, CCNx, etc.) for ICN experiments are pre-installed/configured on s Save operational costs by eliminating install/set up common components by users themselves Does not prohibit to install original components in a user node It supports two types of experiments Application level experiment (e.g., I want to use CCNx, measure the performance of CCNx or newly developed CCN-based application) Network level experiment (e.g., I develop new routing daemon or caching algorithm, so want to measure its performance over the testbed, etc.) Developers own user node having private IP address space; hence possible to measure routing architecture

7 Container Configuration 7 VM1 VM2 (lxc1) (lxc2) (lxc1) (lxc2) Private IP Private IP Private IP Private IP Common (lxc0) Global IP Common (lxc0) Global IP VMware ESXi or VM Player Bridge Global IP Bridge

8 Clone Filesystem 8 Pre-installed and setting up common modules and libraries (e.g., CCNx) in s (keio_alice) /home /usr /opt/cutei (nict_bob) /home /usr /opt/cutei Common /home (common) /usr /opt/cutei VM1 Clone Mount Master (cutei1) /opt/cutei CCNx NLSR Blackadder Click... LV

9 9 High-Availability Container HA function Provides high availability (by logical volume mirroring and take-over function) PC 1 (master) PC 2 (slave) (lxc1) (lxc1) (lxc1) (lxc1) Private IP Private IP Private IP Private IP Common (lxc0) Synchronize Common (lxc0) Global IP Global IP

10 Experiments on Different Container Spaces 10 Two kinds of spaces Common space and user space space enables experiments including routing layer 2 s Containers LXCx LXC Space 1 s Containers LXC1 LXC1 LXCn... 1 Space Common Containers LXC0 LXC0 LXC0... Common Space Container Level LXC1... LXCx LXC0 LXC1... LXCy LXC1... LXCz LXC0 LXC0... Login via SSH 1 Connect via SSH tunnel (tun/tap device) 2 OS Level VM VM Host...

11 Current CCN Topology 11 Common Common

12 Conclusion 12 Global testbed dedicated for ICN protocol/application evaluation We deployed 9 sites as of today Reference Container-Based Unified Testbed for Information-Centric Networking, IEEE Network Magazine (to appear). We released the VM image version 1.0alpha (We hope) our next release (v.1.0b) will be released around the end of Dec If you are interested in participating in our ICN testbed, please contact me. Thank you