wiki:WikiStart

Version 140 (modified by Aaron Falk, 9 years ago) (diff)

--

Welcome to the GENI Wiki

This is the GENI Wiki, a living repository for information relating to the GENI design and GPO-led design process. The structure, governance, and charters for GENI working groups can be found at wiki:GeniWorkingGroups. Join working group mailing lists at http://lists.geni.net/mailman/listinfo/. To get a write account on this wiki, send e-mail to help@geni.net.

GENI Announcements

GENI Experiments

Information on GENI experiments and available GENI resources for experimenters is available at GeniExperiments. A support list for experimenters can be found here.

Old Announcements

GENI Meetings

GENI Engineering Conferences.

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.

GEC1 October 9-11, 2007 Univ. Minnesota, Minneapolis, MN archives
GEC2 March 3-4, 2008 NSF, Arlington, VA archives
GEC3 October 20-31, 2008 HP, Palo Alto, CA archives
GEC4 March 31-April 2, 2009 Florida Int'l Univ., Miami, FL archives
GEC5 July 20-22, 2009 Univ. Washington, Seattle, WA archives
GEC6 November 16-18, 2009 Univ. Utah, Salt Lake, UT archives
GEC7 March 16-18, 2010 Duke Univ., Durham, NC archives
GEC8 July 20-22, 2010 UCSD, San Diego, CA archives
GEC9 November 2-4, 2010 Washington, D.C. archives
GEC10 March 15 - 17, 2011 Univ. Puerto Rico & Polytechnic Univ. Puerto Rico, San Juan, PR agenda
demos
GEC11 July 26-29, 2011 Northwestern Univ., Chicago, IL
GEC12 November 2011 Univ. Missouri, Kansas City, MO dates TBD
GEC13 March, 2012 UCLA, Los Angeles, CA dates TBD
GEC14 July, 2012 Boston, MA dates TBD
GEC15 November, 2012 IUPUI, Indianapolis, IN dates TBD

Other GENI Meetings & Workshops

[GeniTalks GENI Speaking Engagements]

Working Group Pages

Working groups are expected to be the locus of technical work required to develop the GENI architecture and design. They will author & review requirements and design documents and evaluate software and services contributed by Working Group (WG) members (some of which may be sponsored by the GENI Project Office). Working groups are expected to provide input to integration activities, design bake-offs, and other prototyping tasks. Emphasis is placed on technical contribution, including expression of the research community's needs and use cases, regardless of the source of financial support. Academic, industrial, and government lab participants are encouraged. wiki:GeniWorkingGroups

Each GENI working group has its own wiki home page:

  • Campus/Operations, Management, Integration and Security WG -- wiki:GeniOmis

The following GENI working group is no longer active, but its results on opt-in and privacy are still of interest to GENI:

SPIRAL 2 Integration Information

The GENI Project Office works with projects to post information on what they are doing at wiki:SpiralTwo. 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.

GENI Spiral 3 Backbone Services

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 ProtoGENI Component Manager API or the 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.

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 Jon Turner for access to these nodes. Additional nodes at Houston, TX and Atlanta, GA are planned for Spiral 3.

NLR National LambdaRail's OpenFlow nodes are available and 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.

SPP nodes for developing programmable IP overlay services are also available in the same locations at ProtoGENI nodes. Contact the SPP PI Jon Turner for access to these nodes.

OpenFlow switch deployments on National LambdaRail and 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.

GENI API

The GENI API is an effort to enable interoperability between Control Frameworks/Clearinghouses and Aggregates.

The GENI API implements a key interface of the 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.

ProtoGENI, PlanetLab, and Openflow all have implemented the API and are now interoperable, as demonstrated at GEC8 (mostly).

Full details about the GENI API and the reference implementation are available at the GENI API page. From there you can also download code for the gcf reference aggregate manager and the Omni client.

Documents

GPO Documents: The GPO publishes system engineering and integration documents specifying the GENI design, integration, and operations at wiki:GpoDoc.

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.

Contributed Documents: Documents contributed by members of the GENI community. May come from D&P projects. A listing may be found at wiki:ContributedDocs.

Older Documents: Pre-GPO documents (from 2005-2007) can be found at wiki:OldGPGDesignDocuments.

Mailing Lists

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.

  • GENI Announce is a moderated list carrying important announcements about upcoming meetings, solicitations, and other useful information for the developer community.
  • dev is an open list for GENI prototype developers.
  • Experimenters is an open list for discussion and assistance for researchers using the GENI infrastructure.

See working group pages for information on working group mailing lists.


GENI Wiki Information

Getting Started: See wiki:GeniWikiGettingStarted for information on how to post and site-wide conventions.

Admin: Need help? Send mail to help@geni.net

Wiki Docs: GENI is using the Trac wiki and issue tracking software package. All GENI members currently share a single wiki. For help with the Trac software, including pages that explain how to format wiki text and create new pages, TracGuide is a good place to start. Please contact help@geni.net for help, changes, or problems with this site.

Permissions: You must log in to the project wiki before you can edit any page. See wiki:GeniWikiGettingStarted for how to get a login. Most pages in the wiki are editable by any logged-in user. This page (WikiStart) is a read-only page (admins can read and write). Project milestones can only be edited by the GPO. Contact a GPO member or help@geni.net if you want to make changes to this or any other read-only page.

Index: For a complete list of local wiki pages, see TitleIndex.