OldGPGReferencesDevelopment: dev_VINI.txt

File dev_VINI.txt, 4.0 KB (added by peter.stickney@bbn.com, 12 years ago)


1Project: VINI: Virtual Network Infrastructure
3Jen Rexford and Larry Peterson
7Project Description: VINI (Virtual Network Infrastructure) is an
8experimental facility that allows researchers to evaluate prototypes
9of new network protocols and architectures in a controlled and
10realistic environment.  Physically, VINI is a distributed collection
11of network equipment and circuits, coupled with software that enables
12multiple researchers to simultaneously deploy and evaluate their ideas
13carrying real user traffic.  VINI is an early prototype of the GENI
14backbone, using high-end PCs co-located at NLR and Abilene Points of
15Presence (PoPs) as programmable nodes, to support an initial set of
16research experiments (such as the recently-funded FIND projects) and
17gain insights that can aid the design and implementation of the GENI
20Project Deliverables: The project has four main software deliverables:
21(i) kernel/virtual-machine modifications to support extended
22virtualization of the network protocol stack, (ii) management system
23for instantiating experiments in the VINI substrate, (iii) monitoring
24infrastructure to collect data for experiments and the management of
25VINI itself, and (iv) reference implementation of experimental
26software for IP and related protocols.  In addition, we will deploy
27VINI on top of high-end compute nodes in the National Lambda Rail and
28Abilene Internet2 backbones, with dedicated bandwidth between the
29sites, and support other research groups conducting experiments on top
30of the VINI as well as local deployments of the VINI software in their
31own labs.
33Project Status: At this time, we have completed the following
34deliverables in each category.  For item (i), we have built, deployed,
35and evaluated an initial prototype of VINI on top of PlanetLab, using
36Click and User-Mode Linux inside a slice.  For item (ii), we have
37created scripts to automatically create virtual topologies on VINI on
38behalf of an experimenter and configure routing protocols for
39control-plane experiments.  For item (iii), we have capitalized on the
40existing PlanetLab monitoring tools, coupled with conventional tools
41such as tcpdump, ping, and traceroute.  For item (iv), we have created
42and evaluated a reference design of the IP data and control planes,
43called the "Internet in a Slice" using Click, XORP, and OpenVPN on
44VINI.  We have evaluated VINI and IIAS on the PlanetLab nodes in the
45Abilene backbone and have deployed dedicated VINI nodes at two of the
46six planned National Lambda Rail sites.  VINI is described in a
47SIGCOMM'06 paper, and we hae made the initial software, along with a
48user's guide and developer's guide, available at the VINI Web site at
49http://www.vini-veritas.net/ <http://www.vini-veritas.net/> .  Several
50other research groups have already begun experimenting with VINI,
51providing us with an initial set of users to stress test the VINI
54Planned Demos: We are in discussions with the GENI Wireless Working
55Group about having a joint wireless/wired demo that connects wireless
56platforms at WINLAB with the VINI backbone to conduct an example
57experiment of a network architecture that supports mobile wireless
58devices communicating across a wired backbone network.
60Relationship to GENI: The VINI projects serves several important goals
61in relation to the larger GENI effort.  First, the VINI project
62provides an initial facility for researchers to start deploying and
63evaluating new network architectures, albeit without the programmable
64router hardware or flexible optics envisioned for the GENI backbone.
65Second, the design and deployment of VINI will demonstrate the
66feasibility of building and operating a wide-area distributed
67networking research facility, and will reduce the software risks for
68the design of the GENI backbone.  Third, the VINI project will reduce
69the user risk by gaining experience with researchers using VINI to
70conduct experiments with their new ideas and with the challenges of
71having end users "opt in" to experimental services running on top of