Changes between Initial Version and Version 1 of EnterpriseGeni


Ignore:
Timestamp:
11/17/08 17:03:46 (15 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • EnterpriseGeni

    v1 v1  
     1'''Project Number'''
     2
     31613 [[BR]]
     4
     5
     6'''Project Title'''
     7
     8Enterprise GENI:  Prototype, Demonstrate and Create Kits for Replication[[BR]]
     9
     10a.k.a. ENTGENI
     11
     12'''Technical Contacts'''[[BR]]
     13
     14Principal Investigator Nick !McKeown nickm@stanford.edu
     15
     16Guru Parulkar parulkar@stanford.edu[[BR]]
     17
     18Guido Appenzeller guido@appenzeller.net appenz@cs.stanford.edu
     19
     20
     21'''Participating Organizations'''[[BR]]
     22
     23[http://www.stanford.edu/ Stanford University, Stanford CA][[BR]]
     24
     25[http://www.cisco.com Cisco][[BR]]
     26
     27
     28[http://www.hp.com HP][[BR]]
     29
     30
     31[http://www.nec.com NEC][[BR]]
     32
     33[http://nicira.com/alpha Nicira] [[BR]]
     34
     35
     36'''Scope'''[[BR]]
     37
     38The 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.   
     39
     40Priority activities that contribute to this scope include the following items: [[BR]]
     41[[BR]]
     421.      Deploy Enterprise GENI technology in a campus (wireline and wireless). [[BR]]
     432.      Integrate an !OpenFlow network with a GENI control framework in an Aggregate Component Manager.[[BR]]
     443.      Provide access to Enterprise GENI testbeds for GENI users. [[BR]]
     454.      Define an Enterprise GENI deployment kit for research and potential commercial transition. [[BR]]
     46
     47'''Milestones'''[[BR]]
     48
     49[milestone:"ENTGENI:  Version 0 Aggregate Component Manager"][[BR]]
     50[milestone:"ENTGENI:  Draft API/protocol between ENTGENI AM and Clearinghouse"][[BR]]
     51[milestone:"ENTGENI:  Demonstrate OpenFlow in GENI"][[BR]]
     52[milestone:"ENTGENI:  Deploy Phase 0 Enterprise GENI network at Stanford"][[BR]]
     53[milestone:"ENTGENI:  Start integrating interfaces from ENTGENI AM to Clearinghouse"][[BR]]
     54[milestone:"ENTGENI:  Collaborate with O&M and Security teams"][[BR]]
     55[milestone:"ENTGENI:  Host OpenFlow workshop at Stanford"][[BR]]
     56[milestone:"ENTGENI:  Integrate EntGENI with GENI virtual ethernets"][[BR]]
     57
     58
     59'''Project Technical Documents'''[[BR]]
     60
     61The 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.
     62
     63Links to wiki pages or repository locations for the project's technical documents eventually go here. The list should include any document submitted to GENI working groups, as well as other useful documents.
     64
     65'''Spiral 1 Connectivity'''
     66
     67An !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, [wiki:GpENI], OverlayHostingNodes, [wiki:GENISecurity], and [wiki: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.
     68
     69
     70'''GPO Liason System Engineer'''[[BR]]
     71
     72Heidi Picher Dempsey hpd@geni.net
     73
     74'''Related Projects'''[[BR]]
     75
     76[http://openflowswitch.org/ OpenFlow][[BR]]
     77
     78[http://netfpga.org/home.php NetFPGA]
     79
     80
     81