Changes between Version 1 and Version 2 of WikiStart-ALT


Ignore:
Timestamp:
02/10/12 14:10:34 (8 years ago)
Author:
Vic Thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart-ALT

    v1 v2  
    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.
    55
     6To get a write account on this wiki, send e-mail to `help@geni.net`.
    67
    7 == Announcements ==
     8== Navigating the Wiki ==
    89
    9 '''For GENI Experimenters.'''  Please see the [wiki:GENIExperimenterWelcome GENI Experimenters Welcome page].
     10'''Interested in experimentation with GENI?''  See the [wiki:GENIExperimenterWelcome GENI Experimenters Welcome page].
    1011
    11 '''Interested in being a GENI Campus?''' See the [wiki:CampusInfo Campus Info] page.''  (Under construction.  Please email comments to [mailto:help@geni.net help])''
     12'''Interested in being a GENI campus?''' See the [wiki:CampusInfo Campus Info] page.''  (Under construction.  Please email comments to [mailto:help@geni.net help])''
     13
     14'''Interested in following GENI design activities?''' See the [wiki:GeniDesign GENI Design Activities] page.
     15
     16'''Looking for information on GENI projects?'''  See the [wiki:SpiralFour GENI Spiral Four] page.
     17
     18'''Looking for documents published by the GPO?''' See the [wiki:GpoDoc GPO Documents] page.
     19
     20== GENI Resource Map ==
    1221
    1322'''ProtoGENI Flash Client''' Live map showing ProtoGENI and !PlanetLab cluster resources (obtained via the GENI AM API).  Try it [wiki:ProtoGENIFlashClient here].[[br]][[Image(ProtoGENIFlashClient:pgfc-screenshot.jpg, 25%, nolink)]]
     
    2736 [OtherMeetings Past GEC and Other Meetings]
    2837
    29 == Design Activities ==
    30 
    31 The GENI design and prototyping community is working together to agree on the key functions and interfaces needed to meet GENI's requirements. Pointers to GENI design collaborations organized around GEC meetings are provided here: [wiki:GeniDesign GENI Design Activities].  Active efforts at this time include:
    32   * [GeniApi GENI APIs (including the GENI Aggregate Manager API)][[BR]]
    33   * [GeniIdentityAndAttributes Identity & Attributes][[BR]]
    34   * [GeniAuthorization Authorization (including ABAC)][[BR]]
    35   * [GeniRspec Resource Specification] [[BR]]
    36   * [GeniNetworkStitching Network Stitching] [[BR]]
    37   * [GeniArchTeam GENI Architecture Team] [[BR]]
    38   * [GeniInstMeas Instrumentation & Measurement]
    39   * [wiki:GeniRacks GENI Racks]
    40 
    41 == Spiral 3 Projects ==
    42 
    43 The GENI Project Office currently funds in ''design and prototyping'' and ''meso-scale deployment''.  Project technical information, schedules and milestones, and information from related projects can be found here: [wiki:SpiralThree Spiral Three]. 
    4438
    4539== Campus & Backbone Connectivity ==
     
    4741There are multiple options for connecting experimental networks in GENI; the choice depends on your experiment needs, existing networks, and possibilities for new connections. How-tos, background, and recommendations to help you set up GENI connections and experiments can be found here: [wiki:ConnectivityHome Connectivity Home].
    4842
    49 == Documents ==
    50 
    51 The GPO publishes system engineering and integration documents specifying the GENI design, integration, and operations.  Documents are review by the community via mailing list discussion and at GENI Engineering Conferences before being adopted by consensus.  A list of published documents can be found here: [wiki:GpoDoc GPO Docs]. '''Adopted Recommendations''' are documents that reflect the current GENI design, policy, or procedures in effect at this time.  The current set of adopted recommendations are listed below:
    52 
    53   __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]
    54 
    55   __GENI Aggregate Provider's Agreement___. ''GENI is a federated network testbed designed to allow researchers to experiment with network applications and ser- vices that benefit from distribution across a wide geographic area. All uses of GENI should be consistent with this high-level goal.  Management Authorities (MAs), providing aggregates and components operating as a part of GENI, are well-served by having a common set of principles to establish an expected level of service, and methods of cooperation. Such principles, presented in this agreement, benefit the security and stability of the entire GENI suite of infrastructures.''  This document was reviewed and approved by the COMIS working group (see [wiki:Gec9COMISAgenda]), and is adopted for use in GENI Spiral 3.  [http://groups.geni.net/geni/attachment/wiki/ComprehensiveSecurityPgm/Aggregate%20Provider%20Agreement%20v3.pdf PDF]
    56 
    57  __Emergency Stop Procedure__. ''One of the essential early operational requirements for the GENI facility is the need to manage and coordinate the stop and/or containment of GENI resources among all GENI projects in the case of an urgent request.  Emergency stop is the system used to respond to incidents of interference or resource exhaustion caused either unintentionally (misconfiguration), or intentionally (malware).  This is intended to protect GENI aggregates when they begin to integrate with other aggregates, and when GENI begins to interconnect with outside networks.  For Spiral 2, GENI aggregates will have active experimentation and increased integration and interconnection with other aggregates or non-GENI networks.  This document will provide an approach for an early emergency stop service in Spiral 2, as well as a potential evolution for emergency stop for future spirals.''  This document was reviewed and approved by the OMIS working group (see [wiki:Gec8OmisAgenda]), and is adopted for use in GENI Spiral 2 and 3. [http://groups.geni.net/geni/attachment/wiki/GENIMetaOps/Emergency_Stop_System_Description_v5.1.doc DOC]
    58 
    59 
    60  __GMOC Concept of Operations__. ''The GENI facility will require a model of operations moving forward that is both responsive enough to the needs of GENI users and stakeholders (researchers using the facility, users opting-in to GENI, and GENI operators) and flexible enough to evolve with the federated, reconfigurable nature of the facility.  We expect that GENI research users will require a facility that is highly available, with a clear and simple process for getting support, which provides a robust set of highly detailed data about its use and operations, and which communicates maintenance and experiment affecting issues in a responsive and transparent way.''  This document was reviewed and approved by the COMIS working group (see [wiki:Gec9COMISAgenda]), and is adopted for use in GENI Spiral 3. [http://groups.geni.net/geni/attachment/wiki/GENIMetaOps/GENI-Concept-of-Operations-v2.1.doc DOC]
    61 
    62 
    63  __Legal, Law Enforcement and Regulatory Plan__. ''At first glance, it may appear that the GENI federation and its governance entities have no legal responsibilities of their own since "GENI" owns virtually no infrastructure and researchers are ultimately responsible for the actions of their individual experiments. While both statements are true, there is a subtlety here as (1) lawyers, law enforcement and regulatory agencies (LLR) do not know this, and (2) no one party necessarily has all the information to address inquiries from these entities. Therefore, collaboration will be necessary to resolve some LLR issues and the need for a plan to handle such requests is established.  This document begins by further motivating this need with several scenarios or use cases, some based on previous experience in other federations and testbeds. These scenarios also drive the need for proactive measures, such as, having a simple mechanism to reach slice owners and heading off future DMCA requests which could discourage campus participation in GENI. Finally, it becomes clear that someone is needed to fulfill a facilitator role to help route LLR requests to the appropriate parties when a single institution is unable to address the request it receives entirely on its own.'' This document was reviewed and approved by the Ops Agreements meeting at GEC10 (see [wiki:GEC10OpsAgreements]), and is adopted for use in GENI Spiral 3.  [http://groups.geni.net/geni/attachment/wiki/ComprehensiveSecurityPgm/LLR%20Responsibilities%20of%20GENI.pdf PDF]
    64 
    65 
    66 ----
    6743
    6844