Project Number

1613

Project Title

Enterprise GENI: Prototype, Demonstrate and Create Kits for Replication
a.k.a. ENTGENI, E-GENI

Technical Contacts

PI: Nick McKeown ​nickm@stanford.edu
Guru Parulkar ​parulkar@stanford.edu

Participating Organizations

​Stanford University, Stanford CA
​Cisco
​HP
​NEC

GPO Liaison System Engineer

Josh Smift Josh Smift

Scope

The scope of work on this project is to illustrate how GENI can be deployed on local networks, such as campus and enterprise networks, and to develop a kit that allows the work demonstrated in this project to be easily replicated elsewhere.

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

1. Deploy Enterprise GENI technology in a campus (wireline and wireless).
2. Integrate an OpenFlow network with a GENI control framework in an Aggregate Component Manager.
3. Provide access to Enterprise GENI testbeds for GENI users.
4. Define an Enterprise GENI deployment kit for research and potential commercial transition.

Current Capabilities

Milestones

Spiral 1

• MilestoneDate(ENTGENI: S1.a Deploy Phase 0 Enterprise GENI network at Stanford)?
• MilestoneDate(ENTGENI: S1.b Start integrating interfaces from ENTGENI AM to Clearinghouse)?
• MilestoneDate(ENTGENI: S1.c Integrate EntGENI with GENI virtual ethernets)?
• MilestoneDate(ENTGENI: S1.d Demonstrate OpenFlow in GENI)?
• MilestoneDate(ENTGENI: S1.e Collaborate with O&M and Security teams)?

Spiral 2

• MilestoneDate(ENTGENI: S2.a Continue to build E-GENI at Stanford)?
• MilestoneDate(ENTGENI: S2.b Support use of E-GENI at Stanford)?
• MilestoneDate(ENTGENI: S2.c Provide training and documentation for E-GENI)?

Spiral 3

Enterprise GENI milestones for Spiral 3 are all in support of mesoscale OpenFlow campus deployment efforts, and are no longer tracked separately on this wiki. See OFSTAN for a list of relevant milestones.

Project Technical Documents

The Enterprise GENI project will be participating in the Control Framework working group. An API document for the "mimimal" interface between an OpenFlow Aggregate Manager and the PlanetLab GENI clearinghouse is expected as part of the project integration and design work.

The Stanford OpenFlow team demonstrated OpenFlow at ​GEC3. View the ​slides and listen to the audio (coming soon).

The Enterprise GENI Aggregate Manager code and documentation is availalbe on the ​OpenFlow Aggregate Manager page.

Please add other links to wiki pages or repository locations for the project's technical documents. Make sure to include any documents submitted to GENI working groups.

Quarterly Status Reports

2008-Q4 Status Report
2009-Q1 Status Report
2009-Q2 Status Report​
2009-Q3 Status Report​
2010-Q1 Status Report​

Spiral 1 Connectivity

An OpenFlow network will be installed at Stanford. The network will be serving locations in the Computer Science department, and one or more campus wireless access points. IP connectivity between Stanford and the PlanetLab clearinghouse at Princeton is required. IP connectivity to other projects in Cluster B is required for integration and demonstration (GushProto, ProvisioningService, MidAtlanticNet, GpENI, OverlayHostingNodes, GENISecurity, and GENIMetaOps). IP connectivity to other OpenFlow switches on Internet2 and NLR (not installed by GENI) and potentionally other core networks is desired. Virtual Ethernet (L2) connectivity between the OpenFlow switches at Stanford and Internet2 GENI virtual ethernets via CENIC is required. An already existing OpenFlow switch at Stanford tunnels through CENIC to access another already existing OpenFlow switch on Internet2, so it may be possible to reuse the existing infrastructure for GENI.

Related Projects

OFSTAN
OFCLEM
OFGT
OFIU
OFPR
OFRG
OFUWA
OFUWI
OFNOX
EnterpriseGeni

OFI2
OFNLR

​OpenFlow
​NetFPGA
​The OpenFlow switch Consortium
​NOX
​SNAC
​FlowVisor
​Deploying OpenFlow
​Enterprise-GENI
​E-GENI Aggregate Manager