1 / 8

Testbeds

Explore the essential networking questions, distributed resource concepts, new architecture models, IPv6 deployment, multicast services, and more at the CRI workshop in Boston, MA. Understand the significance of testbeds, virtualization experimentation, industry restructuring, and the role of testbed models in advancing technology. Discover the reasons behind utilizing testbeds, the challenges they address, testbed goals, and the importance of testbed desirables in shaping the future of networking technologies.

virgenw
Download Presentation

Testbeds

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. Testbeds Henning Schulzrinne Columbia University CRI workshop (Boston, MA)

  2. Questions to get started • What are the fundamental networking questions? • content distribution - distributed resource • “new architecture”: airport model • > 4 billion devices: does IPv6 work? • deploying new services (multicast, QoS) • distributed data stream processing - computing in the core • application-sensitive (video); dyn. resource allocation; isolation • tolerance to (say) long latencies • security issues: network or not? • disconnected operation - network support • low-power networking CRI workshop (Boston, MA)

  3. Testbed goals • Testbed as an end, rather than (just) means to another end • Experiment with virtualization • Create smaller self-contained domains • Restructure the industry CRI workshop (Boston, MA)

  4. Why testbeds? • Which of these can be answered by testbeds? • experimental system: build, evaluate, write • PlanetLab, Emulab • deployment platform (e.g., Coral) • to be used by people • geographic scale (lots of users can reach it) • scale for routing? --> probably not • “show me” (industry, other researchers) • deploy things that are not yet mature CRI workshop (Boston, MA)

  5. Why testbeds? • Can’t build it at one institution • cost • scale (distances, nodes) • maintenance (technicians, programmers) • Can’t justify at one institution • cost vs. usage intensity CRI workshop (Boston, MA)

  6. Testbed models • “Internet3” • focus mainly on L2, L3 • high-performance, low-latency testbeds • Testbeds from commodity parts (e.g., routers) • subsystem components • transfer of technology to “real” routers? (cf. Linux model) • power as observable quantity • Federation of institution test beds • “cooperative” model (mutual resource sharing) • PlanetLab on steroids • resource-limited experiments (memory, CPU): who gets what? user count? • needs resources -- tiny right now • wireless motes, ORBIT: sign up for time • Kits and tools CRI workshop (Boston, MA)

  7. Testbeds and users • aware vs. oblivious users • old Gigabit testbeds, DARTnet ... Internet2 • roll out applications without access to actual testbed (Internet access) • performance isolation CRI workshop (Boston, MA)

  8. Testbed desirables • Representative testbed • large potential user population • running non-Linux • SETI@HOME for networking • Need programming model • language abstractions • data flow style, scheduling CRI workshop (Boston, MA)

More Related