[[PageOutline(2, Table of Contents)]] = 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. 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`. == GENI Announcements == __GENI Experiments__:: 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]. __[OldAnnouncements Old Announcements]__:: == GENI Meetings == '''Future 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.'' ||'''GEC10''' ||'''March 15 - 17, 2011''' || '''Univ. Puerto Rico & Polytechnic Univ. Puerto Rico, San Juan, PR''' ||'''[https://www.genicon.net/public/welcome.aspx register]'''[[br]]'''[wiki:Gec10Agenda agenda]''[[br]]''[wiki:GEC10DemoInfo 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 || __'''[OtherMeetings Past GEC and Other Meetings]'''__ == GENI [SpiralThree Spiral 3] Development & Deployment Projects == 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. == GENI Spiral 3 Backbone Services == [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. [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. [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. [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. 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. == GENI API == The [wiki:GeniApi GENI API] is an effort to enable interoperability between Control Frameworks/Clearinghouses and Aggregates. 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. [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). 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. == 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. == Useful Links == * wiki:GeniNewcomers * wiki:GeniGlossary * [http://www.geni.net/office/office.html GENI Project Office] * wiki:RelatedProjects == 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. * [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. * GENI [http://lists.geni.net/mailman/listinfo/discuss discuss] is an open list for general community discussion. * [http://lists.geni.net/mailman/listinfo/dev dev] is an open list for GENI prototype developers. * [http://lists.geni.net/mailman/listinfo/experimenters experimenters] is an open list for discussion and assistance for researchers using the GENI infrastructure. ---- == GENI Wiki Information == '''Getting Started:''' See wiki:GeniWikiGettingStarted for information on how to post and site-wide conventions. '''Admin:''' Need help? Send mail to [mailto: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 [mailto: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 [mailto: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.