Changes between Version 32 and Version 33 of EnterpriseGeni


Ignore:
Timestamp:
09/30/10 09:41:43 (14 years ago)
Author:
Josh Smift
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • EnterpriseGeni

    v32 v33  
    1010a.k.a. ENTGENI, E-GENI
    1111
    12 == Technical Contacts ==
     12=== Technical Contacts ===
    1313
    1414'''PI:''' Nick !McKeown [mailto:nickm@stanford.edu][[BR]]
    1515Guru Parulkar [mailto:parulkar@stanford.edu][[BR]]
    16 Guido Appenzeller [mailto:guido@appenzeller.net] [mailto:appenz@cs.stanford.edu][[BR]]
    1716
    18 
    19 == Participating Organizations ==
     17=== Participating Organizations ===
    2018
    2119[http://www.stanford.edu/ Stanford University, Stanford CA][[BR]]
    … …  
    2321[http://www.hp.com HP][[BR]]
    2422[http://www.nec.com NEC][[BR]]
    25 [http://nicira.com Nicira] [[BR]]
     23
     24=== GPO Liaison System Engineer ===
     25
     26Josh Smift jbs@bbn.com
    2627
    2728== Scope ==
    … …  
    2930The 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.   
    3031
    31 Priority activities that contribute to this scope include the following items: [[BR]]
    32 [[BR]]
    33 1.      Deploy Enterprise GENI technology in a campus (wireline and wireless). [[BR]]
    34 2.      Integrate an !OpenFlow network with a GENI control framework in an Aggregate Component Manager.[[BR]]
    35 3.      Provide access to Enterprise GENI testbeds for GENI users. [[BR]]
    36 4.      Define an Enterprise GENI deployment kit for research and potential commercial transition. [[BR]]
     32Priority activities that contribute to this scope include the following items:
    3733
    38 == Current Capabilities ==
     34 1. Deploy Enterprise GENI technology in a campus (wireline and wireless).
     35 2. Integrate an !OpenFlow network with a GENI control framework in an Aggregate Component Manager.
     36 3. Provide access to Enterprise GENI testbeds for GENI users.
     37 4. Define an Enterprise GENI deployment kit for research and potential commercial transition.
    3938
    40 == Milestones ==
     39=== Current Capabilities ===
    4140
    42 === Spiral 1 ===
     41=== Milestones ===
     42
     43==== Spiral 1 ====
    4344
    4445 * [[MilestoneDate(ENTGENI: S1.a Deploy Phase 0 Enterprise GENI network at Stanford)]]
    … …  
    4849 * [[MilestoneDate(ENTGENI: S1.e Collaborate with O&M and Security teams)]]
    4950
    50 === Spiral 2 ===
     51==== Spiral 2 ====
     52
    5153 * [[MilestoneDate(ENTGENI: S2.a Continue to build E-GENI at Stanford)]]
    5254 * [[MilestoneDate(ENTGENI: S2.b Support use of E-GENI at Stanford)]]
    … …  
    6365Please 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.
    6466
    65 == Quarterly Status Reports ==
     67=== Quarterly Status Reports ===
    6668
    6769[wiki:EnterpriseGENI-4Q08-status 2008-Q4 Status Report][[BR]]
    … …  
    7173[attachment:wiki:OFSTAN:E-GENI-Status-report-Q1-2010.doc 2010-Q1 Status Report][[BR]]
    7274
    73 == Spiral 1 Connectivity ==
     75=== Spiral 1 Connectivity ===
    7476
    7577An !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.
    7678
    77 == GPO Liaison System Engineer ==
     79== Related Projects ==
    7880
    79 Heidi Picher Dempsey hdempsey@geni.net
     81[wiki:OFSTAN] [[BR]]
     82[wiki:OFCLEM] [[BR]]
     83[wiki:OFGT] [[BR]]
     84[wiki:OFIU] [[BR]]
     85[wiki:OFPR] [[BR]]
     86[wiki:OFRG] [[BR]]
     87[wiki:OFUWA] [[BR]]
     88[wiki:OFUWI] [[BR]]
     89[wiki:OFNOX] [[BR]]
     90[wiki:EnterpriseGeni] [[BR]]
    8091
    81 === Related Projects ===
    82  * [http://openflowswitch.org/ OpenFlow]
    83  * EnterpriseGeni
    84  * [http://www.netfpga.org/ NetFPGA]
    85  * [wiki:OFSTAN]
     92[wiki:OFI2] [[BR]]
     93[wiki:OFNLR] [[BR]]
     94
     95[http://openflowswitch.org/ OpenFlow] [[BR]]
     96[http://www.netfpga.org/ NetFPGA] [[BR]]
     97[http://www.openflowswitch.org/ The OpenFlow switch Consortium] [[BR]]
     98[http://noxrepo.org/wp/ NOX] [[BR]]
     99[http://www.openflowswitch.org/wp/snac/ SNAC] [[BR]]
     100[http://www.openflowswitch.org/wk/index.php/FlowVisor FlowVisor] [[BR]]
     101[http://www.openflowswitch.org/foswiki/bin/view/OpenFlow/Deployment/ Deploying OpenFlow] [[BR]]
     102[http://www.openflowswitch.org/wk/index.php/E-GENI Enterprise-GENI] [[BR]]
     103[http://www.openflowswitch.org/wk/index.php/Aggregate_Manager E-GENI Aggregate Manager] [[BR]]