wiki:EnterpriseGeni

Version 28 (modified by Josh Smift, 10 years ago) (diff)

--

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
Guido Appenzeller guido@appenzeller.net appenz@cs.stanford.edu

Participating Organizations

Stanford University, Stanford CA
Cisco
HP
NEC
Nicira

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

Spiral 2

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

4Q08 Status Report
1Q09 Status Report
2Q09 Status Report
3Q09 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.

GPO Liaison System Engineer

Heidi Picher Dempsey hdempsey@geni.net

Related Projects

Project Number

1833H

Project Title

Nicira Networks Development and Support for Enterprise GENI
a.k.a. NiciraEntGeni, NiciraEGeni

Technical Contacts

Principal Investigator Martin Casado email@email

Participating Organizations

GPO Liaison System Engineer

Heidi Dempsey hdempsey@bbn.com

Scope

Nicira Networks will support enhancements to the NOX software base used in OpenFlow, and provide trouble-shooting support for OpenFlow shakedown in campus and backbone environments in GENI. Campuses and backbones are expected to use NOX for at least three years, with Nicira’s help (BBN and Stanford will also help support campuses).

The primary enhancements to NOX are:

  1. Upgrades for NOX compatibility with OpenFlow 1.0 in the GENI environment
  2. Design improvements that make it easier to install and run NOX in GENI
  3. A new console interface (SNAC) intended primarily for Campus IT staff to use to manage OpenFlow on their campuses.

Current Capabilities

BRIEF descriptions of resources/functions/tools that are available to anyone in the GENI community

Milestones

Spiral 2

Project Technical Documents

Links to wiki pages for the project's technical documents go here. List should include any document in the working groups, as well as other useful documents. Projects may have a full tree of wiki pages here.

Quarterly Status Reports

QuarterlyStatusReportTemplate use format

due 31Dec09: [wiki:ProjTemp-4Q09-status 4Q09 Status Report]

Spiral 2 Connectivity

Links to wiki pages about details of infrastructure that the project is using (if any). Examples include IP addresses, hostnames, URLs, DNS servers, local site network maps, VLANIDs (if permanent VLANs are used), pointers to public keys. GPO may do first drafts of any of these and have the PI correct them to bootstrap. May also include ticket links for pending or known connectivity issues. Many projects will have a full tree of wiki pages here.

Stanford connectivity diagram

Related Projects

Attachments (3)

Download all attachments as: .zip