Version 3 (modified by, 8 years ago) (diff)


Project 1861 Univ of Utah/UEN GENI Regional Project Annual Status Report

Period: Oct 2012 - Sep 2013


In the 2013, the Univ of Utah/UEN GENI Project 1861 successfully implemented and integrated the University of Utah Downtown Data Center switch infrastructure to support a very large InstaGENI installation (33 nodes). The project deployed a dedicated 10G wavelength between the Downtown Data Center and the University of Utah Eccles Broadcast Center (EBC) site. The project also deployed a dedicated 10G wavelength between the Univ of Utah EBC site and the Level3 Point of Presence where UEN peers with Internet2.

By leveraging network resources from the Univ of Utah, UEN, ProtoGENI, Internet2, and the GENI backbone, this project was able to deploy these installations. Personnel resources from the Univ of Utah, ProtoGENI, UEN, Internet2 and the BBN GPO were all instrumental in making these implementations and ongoing maintenance a success.

I. Major accomplishments

A. Milestones achieved

Milestone Status Begin Date End Date Notes
Acquire and implement GENI wavelengths (EBC <-> Level3, DDC <-> EBC) Complete
Acquire and implement UEN GENI DDC switch Complete
Support multi-campus demo that includes new resources from this deployment and existing meso-scale resources. Complete
Integrate and test with other existing Internet2 and NLR OpenFlow meso-scale deployments and GENI racks. Complete
Work with Univ of Utah Flux group to install large InstaGENI rack at DDC Complete

B. Deliverables made

  • GEC 15: attended by Joe Breen
  • GEC 16: attended by Steve Corbato and Joe Breen
  • GEC 17: attended by Joe Breen
  • Ongoing maintenance - FOAM and Flowvisor upgrades complete, implementation of additional OpenFlow VLANs
  • Deployed UEN Aggregate Switch at Downtown Data Center
  • Collaborated with Univ of Utah Flux Group to bring up large InstaGENI Rack
  • Deployed two 10G wavelengths dedicated for GENI between DDC and EBC and between EBC and Level3

II. Description of work performed during last quarter

A. Activities and findings

  • Put together design and reviewed with GPO and Utah Experimenter team
  • Installed HP 5406v2 in the Downtown Data Center
  • Setup FOAM and Flowvisor on virtual machine for controlling the UEN aggregate switch
  • Installed GENI wavelengths

B. Project participants

  • Steve Corbato - PI - University of Utah/UEN
  • Joe Breen - CHPC
  • Kevin Quire - UEN Senior Network Engineer
  • Jim Stewart - UEN Technical Director
  • Rob Ricci (and team) - Utah PI for ProtoGENI and other experiments

C. Publications (individual and organizational)


D. Outreach activities

UEN GENI Project participants have presented GENI, OpenFlow, UEN GENI project and other related discussions to multiple groups within the University of Utah and UEN. These presentations have raised awareness and received input from security engineers, network engineers, system engineers and other discipline scientists.

E. Collaborations

The UEN GENI Project participants have collaborated closely with BBN GPO staff and Internet2 staff in order to achieve success on the milestones. Tim U, Josh S of the BBN GPO and Ali of the Stanford staff were invaluable in getting the FOAM/Flowvisor installations functional. They provided the constant support necessary to ferret out all of the subtle issues around documentation, file permissions, etc. Tim U, Matt Z and Internet2/Indiana engineers helped put together a flexible implementation that leveraged the existing resources of the ProtoGENI backbone, Internet2 backbone and the GENI OpenFlow backbone.

Collaborations with UEN engineering staff, Univ of Utah Center for High Performance Computing staff, Univ of Utah IT staff (security, networking, systems, etc.) have made the implementation go smoothly. The interactions have raised awareness of the project and helped balance the research infrastructure with the production infrastructure of UEN and the Univ. of Utah.

Collaborations with Rob Ricci, the ProtoGENI staff and the Flux/Emulab staff have tuned the infrastructure to meet the experimenter needs, both in timing and feature-support. Rob provides oversight to the work and provides guidance on scheduling of experiments, etc. His group also act as a resource in understanding the experimenter perspective and experimenter requirements.

F. Other Contributions