Version 15 (modified by, 14 years ago) (diff)


Project Number


Project Title

Instrumentation and Measurement for GENI a.k.a. GENI Inst & Meas (obsolete), MeasurementSystem, MeasurementSys

Technical Contacts

PI Paul Barford / / 608 262 6609
Co-PI Mark Crovella / / 617 353 8923
Co-PI Joel Sommers / / 315 228 7587

Participating Organizations

Computer Science Department
University of Wisconsin
1210 West Dayton St.
Madison, WI 53706

Computer Science Department
Boston University
111 Cummington St.
Boston, MA 02215

Computer Science Department
Colgate University
13 Oak Drive
Hamilton, NY 13346


The scope of work on this project is to develop, test and deploy a prototype implementation of network instrumentation and measurement systems for the GENI infrastructure.

Priority activities that contribute to this scope include the following items:

  1. Develop an instrumentation and measurement implementation for GENI that provides an interface for researchers, as well an interface to a GENI control framework.
  2. Develop an implementation that gives GENI users access to a shared measurement and instrumentation infrastructure that is extensible to several different kinds of measurement devices.
  3. Implement systems consistent with the GENI Instrumentation and Measurement Systems (GIMS) Specification, to help reduce risks in this as-yet-unimplemented area of GENI.

GIMS Conceptual Description.


Spiral 1

Spiral 2

Project Technical Documents

Requirements and Specifications for the Instrumentation and Measurement Systems for GENI

-- Notes from the review of the above document

Spiral 1 Connectivity

There is no deployment outside the PIs labs planned for Spiral 1. ProtoGENI is the control framework for integration.

The measurement devices being developed will be deployed on network links in the lab (taps or span ports on routers/switches). In the longer term (beyond the first year), measurement devices will be deployed in other labs and/or network locations. At this point, these devices will need IP addresses assigned so that they can be accessed by the control framework interface. The address may be private if the clearinghouse manages download and configuration as it would for a network node.

For Spiral 1, there is no requirement for layer 2 virtual ethernets to the project locations, although the measurement devices are aware of VLAN IDs. Longer-term requirements for VLANs are TBD.

Quarterly Status Reports

December 2008 Report
April 2009 Report

GPO Liaison System Engineer

Vic Thomas

Related Projects

ProtoGENI cluster.

Attachments (15)