Changes between Version 151 and Version 152 of WikiStart


Ignore:
Timestamp:
03/07/11 14:49:02 (9 years ago)
Author:
Aaron Falk
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v151 v152  
    22= Welcome to the GENI Wiki =
    33
    4  This is the GENI Wiki, a living repository for information relating to the GENI design and GPO-led design process.  To get a write account on this wiki, send e-mail to `help@geni.net`.
     4This is the GENI Wiki, a living repository for information relating to the GENI design and GPO-led design process.  To get a write account on this wiki, send e-mail to `help@geni.net`.
    55
    66
     
    99 __GENI Experiments__::
    1010
    11  Information on GENI experiments and available GENI resources for experimenters is available at [wiki:GeniExperiments].  A support list for experimenters can be found [http://lists.geni.net/mailman/listinfo/experimenters here].
     11Information on GENI experiments and available GENI resources for experimenters is available at [wiki:GeniExperiments].  A support list for experimenters can be found [http://lists.geni.net/mailman/listinfo/experimenters here].
    1212
    1313 
     
    1717
    1818'''Future GENI Engineering Conferences.''' 
    19   The GEC is the GENI Project Office’s (GPO) regular open working meeting where researchers, developers, industrial & international partners and the GPO meet to advance infrastructure planning and prototyping for the GENI project. Further, the GEC focuses on how to design and build a suite of infrastructure that can best inspire and support creative research. The conference is open to all.  ''The dates and locations below should be considered mostly firm until registration opens.''
     19The GEC is the GENI Project Office’s (GPO) regular open working meeting where researchers, developers, industrial & international partners and the GPO meet to advance infrastructure planning and prototyping for the GENI project. Further, the GEC focuses on how to design and build a suite of infrastructure that can best inspire and support creative research. The conference is open to all.  ''The dates and locations below should be considered mostly firm until registration opens.''
    2020
    2121
     
    2929 [OtherMeetings Past GEC and Other Meetings]
    3030
     31== GENI Design Activities ==
     32
     33The GENI design and prototyping community is working together to agree on the key functions and interfaces needed to meet GENI's requirements. This page collects pointers to GENI design collaborations organized around GEC meetings: [wiki:GeniDesign GENI Design Activities].
     34 
    3135
    3236== GENI Spiral 3 Projects ==
    3337
    34  The GENI Project Office currently funds in ''design and prototyping'' and ''meso-scale deployment''.  Information about these projects can be found [wiki:SpiralThree here].  These pages include project technical information, schedules and milestones, and information from related projects not funded by GENI. 
     38The GENI Project Office currently funds in ''design and prototyping'' and ''meso-scale deployment''.  Information about these projects can be found [wiki:SpiralThree here].  These pages include project technical information, schedules and milestones, and information from related projects not funded by GENI. 
    3539
    3640== GENI Spiral 3 Backbone Services ==
    3741
    38  [wiki:Integration ProtoGENI backbone]  nodes are available in Internet 2 (Kansas City, MI, Salt Lake City, UT, Washington, DC).  Layer 2 data-plane access to these services is available via dedicated campus connections to Internet 2 or via Internet 2's ION service using the [https://www.protogeni.net/trac/protogeni/wiki/ComponentManagerAPI ProtoGENI Component Manager API] or the [http://www.emulab.net Emulab] interfaces.  Layer 3 access is also available via any Internet connection. Additional ProtoGENI node deployments are planned for Spiral 3 at Houston, TX, Atlanta, GA, and Seattle WA, and one other site.
     42[wiki:Integration ProtoGENI backbone]  nodes are available in Internet 2 (Kansas City, MI, Salt Lake City, UT, Washington, DC).  Layer 2 data-plane access to these services is available via dedicated campus connections to Internet 2 or via Internet 2's ION service using the [https://www.protogeni.net/trac/protogeni/wiki/ComponentManagerAPI ProtoGENI Component Manager API] or the [http://www.emulab.net Emulab] interfaces.  Layer 3 access is also available via any Internet connection. Additional ProtoGENI node deployments are planned for Spiral 3 at Houston, TX, Atlanta, GA, and Seattle WA, and one other site.
    3943
    40  [wiki:"Internet Scale Overlay Hosting" SPP] nodes for developing programmable IP overlay services are available at Kansas City, MI, Salt Lake City, UT, and Washington, DC. Contact the SPP PI [mailto:jon.turner@wustl.edu] for access to these nodes. Additional nodes at Houston, TX and Atlanta, GA are planned for Spiral 3.
     44[wiki:"Internet Scale Overlay Hosting" SPP] nodes for developing programmable IP overlay services are available at Kansas City, MI, Salt Lake City, UT, and Washington, DC. Contact the SPP PI [mailto:jon.turner@wustl.edu] for access to these nodes. Additional nodes at Houston, TX and Atlanta, GA are planned for Spiral 3.
    4145
    42  [wiki:OFNLR NLR National LambdaRail's OpenFlow] nodes are available and [wiki:OFI2 Internet 2's OpenFlow] node deployments are underway in Spiral 3.  See linked project pages for node locations.  Layer 2 data-plane access to these services is available via either: a dedicated campus connection to either backbone, an NLR !FrameNet (Sherpa) connection,  or an Internet2 ION connection.  Layer 3 access is also available via any Internet connection.
     46[wiki:OFNLR NLR National LambdaRail's OpenFlow] nodes are available and [wiki:OFI2 Internet 2's OpenFlow] node deployments are underway in Spiral 3.  See linked project pages for node locations.  Layer 2 data-plane access to these services is available via either: a dedicated campus connection to either backbone, an NLR !FrameNet (Sherpa) connection,  or an Internet2 ION connection.  Layer 3 access is also available via any Internet connection.
    4347
    44  [wiki:"Internet Scale Overlay Hosting" SPP] nodes for developing programmable IP overlay services are also available in the same locations at ProtoGENI nodes.  Contact the SPP PI [mailto:jon.turner@wustl.edu] for access to these nodes.
     48[wiki:"Internet Scale Overlay Hosting" SPP] nodes for developing programmable IP overlay services are also available in the same locations at ProtoGENI nodes.  Contact the SPP PI [mailto:jon.turner@wustl.edu] for access to these nodes.
    4549
    46  OpenFlow switch deployments on [wiki:OFNLR National LambdaRail] and [wiki:OFI2 Internet 2] are underway in Spiral 2.  Layer 2 data plane access to these services is available via a dedicated campus connection to either backbone, or via NLR Framenet (Sherpa) or Internet2 ION service.  Layer 3 access is also available via any Internet connection.
    47 
    48 == GENI API ==
    49 
    50  The [wiki:GeniApi GENI API] is an effort to enable interoperability between Control Frameworks/Clearinghouses and Aggregates.
    51 
    52  The [wiki:GeniApi GENI API] implements a key interface of the [wiki:SliceFedArch SFA 2.0 Draft], providing a common interface to Aggregate Managers. Experimenters can use the API to access resources belonging to any compliant Control Framework. The API lets you mix and match aggregates with control frameworks.
    53 
    54  [http://www.protogeni.net/trac/protogeni ProtoGENI], [http://www.planet-lab.org/ PlanetLab], and [http://www.openflow.org/ Openflow] all have implemented the API and are now interoperable, as demonstrated at GEC8 (mostly).
    55 
    56  Full details about the [wiki:GeniApi GENI API] and the reference implementation are available at the [wiki:GeniApi GENI API] page. From there you can also download code for the gcf reference aggregate manager and the Omni client.
     50OpenFlow switch deployments on [wiki:OFNLR National LambdaRail] and [wiki:OFI2 Internet 2] are underway in Spiral 2.  Layer 2 data plane access to these services is available via a dedicated campus connection to either backbone, or via NLR Framenet (Sherpa) or Internet2 ION service.  Layer 3 access is also available via any Internet connection.
    5751
    5852== Documents ==
     
    6256=== Adopted Recommendations ===
    6357
    64  GENI Recommended Use Policy:: ''This document communicates common guidelines for using the suite of GENI infrastructures to the GENI community.  GENI participants should be willing to follow the guidelines, and to support GENI community efforts to implement this policy.'' (GENI-INF-RUP-01.1) [http://groups.geni.net/geni/attachment/wiki/RUP/RUP.pdf PDF]
     58GENI Recommended Use Policy:: ''This document communicates common guidelines for using the suite of GENI infrastructures to the GENI community.  GENI participants should be willing to follow the guidelines, and to support GENI community efforts to implement this policy.'' (GENI-INF-RUP-01.1) [http://groups.geni.net/geni/attachment/wiki/RUP/RUP.pdf PDF]
     59
     60----
    6561
    6662