Changes between Version 149 and Version 150 of WikiStart


Ignore:
Timestamp:
02/14/11 17:26:03 (14 years ago)
Author:
Aaron Falk
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v149 v150  
    22= Welcome to the GENI Wiki =
    33
    4 
    5 
    6 This is the GENI Wiki, a living repository for information relating to the GENI design and GPO-led design process.  Join GENI mailing lists at [http://lists.geni.net/mailman/listinfo/].  To get a write account on this wiki, send e-mail to `help@geni.net`.
     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`.
    75
    86
    … …  
    119 __GENI Experiments__::
    1210
    13   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].
     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].
    1412
    1513 
    16  __[OldAnnouncements Old Announcements]__::
     14 [OldAnnouncements Old Announcements]::
    1715
    1816== GENI Meetings ==
    … …  
    2927 ||GEC15    ||November, 2012            || IUPUI, Indianapolis, IN || dates TBD ||
    3028
    31  
    32 
    33 __'''[OtherMeetings Past GEC and Other Meetings]'''__
     29 [OtherMeetings Past GEC and Other Meetings]
    3430
    3531
     32== GENI Spiral 3 Projects ==
    3633
    37 
    38 
    39 == GENI [SpiralThree Spiral 3] ''Design & Prototyping'' and ''Meso-Scale Deployment''  Projects ==
    40 
    41 The GENI Project Office works with projects to post information on what they are doing at wiki:SpiralThree.  These pages include project technical information, schedules and milestones, and information from related projects not funded by GENI.  Keeping these pages current helps make planning, participating, and integrating easier for the GENI community.
     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. 
    4235
    4336== GENI Spiral 3 Backbone Services ==
    4437
    45 [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.
     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.
    4639
    47 [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.
     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.
    4841
    49 [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.
     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.
    5043
    51 [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.
     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.
    5245
    53 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.
     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.
    5447
    5548== GENI API ==
    5649
    57 The [wiki:GeniApi GENI API] is an effort to enable interoperability between Control Frameworks/Clearinghouses and Aggregates.
     50 The [wiki:GeniApi GENI API] is an effort to enable interoperability between Control Frameworks/Clearinghouses and Aggregates.
    5851
    59 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.
     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.
    6053
    61 [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).
     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).
    6255
    63 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.
     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.
    6457
    6558== Documents ==
    6659
    67 '''GPO Documents:''' The GPO publishes system engineering and integration documents specifying the GENI design, integration, and operations at wiki:GpoDoc.
     60The GPO publishes system engineering and integration documents specifying the GENI design, integration, and operations [wiki:GpoDoc here].  Documents are review by the community via mailing list discussion and at GENI Engineering Conferences before being adopted by consensus.
    6861
    69 '''Working Group Documents:''' GENI working groups develop and publish documents.  Unless otherwise noted, these documents represent the consensus of the publishing working group.  Working drafts can be found on the individual working group wiki pages.
     62=== Adopted Recommendations ===
    7063
    71 '''Contributed Documents:'''  Documents contributed by members of the GENI community.  May come from D&P projects.  A listing may be found at wiki:ContributedDocs.
    72 
    73 '''Older Documents:''' Pre-GPO documents (from 2005-2007) can be found at wiki:OldGPGDesignDocuments.
     64 GENI Recommended Use Policy (GENI-INF-RUP-01.1) ''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.'' [http://groups.geni.net/geni/attachment/wiki/RUP/RUP.pdf PDF]
    7465
    7566
    7667== Useful Links ==
    7768
    78   * wiki:GeniNewcomers
     69 * [wiki:GeniNewcomers For Newcomers to GENI]
    7970
    80   * wiki:GeniGlossary
     71 * [wiki:GeniGlossary Glossary]
    8172
    82   * [http://www.geni.net/office/office.html GENI Project Office]
     73 * [http://www.geni.net/office/office.html GENI Project Office]
    8374
    84   * wiki:RelatedProjects
     75 * [wiki:RelatedProjects Related Projects]
    8576
    8677
    8778==  Mailing Lists ==
    8879
    89 It is a very good idea to subscribe to the GENI Announce list.  If you are a GENI technology developer, you should aslo subscribe to the GENI Developer list.
     80 * Announcements: [http://lists.geni.net/mailman/listinfo/geni-announce signup]
    9081
    91   * [http://lists.geni.net/mailman/listinfo/geni-announce geni-announce] is a moderated list carrying important announcements about upcoming meetings, solicitations, and other useful information for the developer community.
     82 * Community Discussion: GENI [http://lists.geni.net/mailman/listinfo/discuss signup]
    9283
    93   * GENI [http://lists.geni.net/mailman/listinfo/discuss discuss] is an open list for general community discussion. 
     84 * Developers: [http://lists.geni.net/mailman/listinfo/dev signup]
    9485
    95   * [http://lists.geni.net/mailman/listinfo/dev dev] is an open list for GENI prototype developers.
    96 
    97   * [http://lists.geni.net/mailman/listinfo/experimenters experimenters] is an open list for discussion and assistance for researchers using the GENI infrastructure.
     86 * Experimenters: [http://lists.geni.net/mailman/listinfo/experimenters signup]
    9887
    9988