1 / 9

VINI: A Virtual Network Infrastructure

VINI (Virtual Network Infrastructure) is a cutting-edge software toolkit developed by Andy Bavier at Princeton University, designed for network experimentation. It allows researchers to observe routing protocols "in the wild," evaluate new protocols, and carry real traffic on behalf of actual clients. VINI serves as a hands-on teaching aid, leveraging open-source tools like the XORP routing protocol suite and OpenVPN. It addresses challenges like overlay latency and enhances reproducibility for large-scale networking experiments, paving the way for innovative policies and kernel advancements.

mimi
Télécharger la présentation

VINI: A Virtual Network Infrastructure

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. VINI: A Virtual Network Infrastructure Andy Bavier Princeton University

  2. Internet In A Slice • Software toolkit for network experimentation • Observe routing protocols “in the wild” • Evaluate new protocols and proposed changes • Carry real traffic on behalf of real clients • Hands-on teaching aid • Leverage research, open source: • Click modular software router • XORP routing protocol suite • OpenVPN, User-Mode Linux

  3. IIAS Overview UML XORP OSPF updates Click Client Server UML UML XORP XORP UDP tunnels Open VPN Click Click NAT

  4. Demo: IIAS on Abilene STTL CHIN NYCM SNVA DNVR KSCY IPLS WASH LOSA ATLA HSTN

  5. IIAS on PlanetLab • Problem: overlay latency • DC – Seattle RTT on Abilene • Network: constant 74ms • Six-hop IIAS overlay: 76ms – 135ms • 50% > 82ms, 10% > 87ms • Reason: CPU scheduling delay on heavily-loaded PlanetLab nodes

  6. VINI: A Virtual Network Infrastructure • Balance reproducibility and reality • Dedicated resources for large-scale networking experiments like IIAS • Expose L2 circuits to slices • OS support for high speed packet forwarding • Federate with public PlanetLab • Moving away from PlanetLab’s best effort model • Experiment with new policies, kernels • Approach federation problem from both sides

  7. A Small Step: PL-VINI • What can we do right now for IIAS? • Use existing PlanetLab facilities • CPU reservations (new 3.2 CPU scheduler) • Boost priority of Click forwarder (Proper) • Problem: not mechanism, but policy

  8. RTT on Network, Overlay Overlay + PL-VINI: 98% of RTTs within 3ms of network

  9. Timeline 2002-present Feb 2006 Jun 2006 2007-08 • PlanetLab • PCs • tunnels • kernel • PL-VINI • PCs • tunnels • kernel’ • policies • VINI • PCs • Layer 2 • (Abilene, NLR) • kernel’’ • policies • VINI v2 • PCs • FPGAs • Layer 2 (other GREN) • Dynamic Layer 2 • kernel’’’ • policies

More Related