1 / 6

PrimoGENI – Developing GENI Aggregate for Real-Time Large-Scale Network Simulation

PrimoGENI – Developing GENI Aggregate for Real-Time Large-Scale Network Simulation. Jason Liu, Julio Ibarra, Heidi Alvarez Florida International University. Background. Network Experimentation: analytical models, simulation, emulation, physical testbed Simulation vs. Emulation

ivor-tucker
Download Presentation

PrimoGENI – Developing GENI Aggregate for Real-Time Large-Scale Network Simulation

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. PrimoGENI – Developing GENI Aggregate for Real-Time Large-Scale Network Simulation Jason Liu, Julio Ibarra, Heidi Alvarez Florida International University

  2. Background • Network Experimentation: • analytical models, simulation, emulation, physical testbed • Simulation vs. Emulation • Real-time network simulation • Run simulation in real-time • Interact/integrate with real applications

  3. PRIME • Parallel real-time network modeling environment • LARGE network scenarios • Our solutions: • Run fast: parallel and distributed simulation • Run cheap: hybrid traffic models • Scalable emulation infrastructure: • VPN & virtual machines

  4. PrimoGENI-us Scope: • Prototype development • Aggregate manager • Experiment workflow tools • Infrastructure development • Region backbone: FLR, NLR, Internet2 • International connections: Kyatera, GIGA in Brazil

  5. Issues • PrimoGENI as an aggregate • Export “sliver” as a virtual network with simulated and/or emulated network entities • Define “resources” as simulated and/or emulated network entities  resource discovery/specification • Tricky for RSpec: need to specify resource types only (and associated supporting platform) • Ticketing: network topology, traffic, routing, … • Tools for configuring, building, connecting, servicing (data collection and visualization), steering, and tearing down “slivers” • Resource sharing issues • Model Opt-In

More Related