Changes between Version 1 and Version 2 of GeniAggregate/MillionNodeGeni


Ignore:
Timestamp:
03/09/11 11:10:16 (8 years ago)
Author:
Vic Thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniAggregate/MillionNodeGeni

    v1 v2  
    1414|| Guides and Documents || https://seattle.cs.washington.edu/wiki/ProgrammersPage  ||
    1515|| Support || [mailto:seattle-users@cs.washington.edu Support mailings list].  Email to this address goes to all subscribers of the mailing list.  ||
    16 || Compatible tools || Differentiate between different kinds of tools [http://groups.geni.net/geni/wiki/PGTools ProtoGENI Tools] and [http://groups.geni.net/geni/wiki/GushProto Gush] ||
     16|| Compatible tools || [http://groups.geni.net/geni/wiki/PGTools ProtoGENI Tools] and Million Node GENI tools ||
    1717[[BR]]
    1818= Using this Aggregate =
    19 || Clearinghouses Recognized || [http://groups.geni.net/syseng/wiki/HypoPGENIClearingHousePage ProtoGENI Clearinghouse] | PlanetLab Clearinghouse ||
    20 || Usage Policies || The ProtoGENI Emulab aggregate is a public facility; resources may be allocated and used by any GENI experimenter with suitable credentials. ProtoGENI Emulab users can ask for as many nodes as are currently available.  Experiments are "swapped out" of the testbed after a  "Maximum Duration" period of inactivity.   For details see https://users.emulab.net/trac/emulab/wiki/Swapping.  All users of ProtoGENI Emulab resources must abide by the [https://users.emulab.net/trac/emulab/wiki/SecReq Emulab Security Policy], [https://users.emulab.net/trac/emulab/wiki/AdminPolicies Emulab Acceptable Use Policy]  and [https://users.emulab.net/trac/emulab/wiki/Swapping Emulab Node Use Policy]. ||
     19|| Clearinghouses Recognized || [http://groups.geni.net/syseng/wiki/HypoPGENIClearingHousePage ProtoGENI Clearinghouse] ||
     20|| Usage Policies ||  Users who need access to more than 10 Million Node GENI nodes must make a platform available to use by other Million Node GENI users. <--- ANY OTHER POLICIES?AGREEMENTS THAT SHOULD BE MENTIONED HERE? ||
    2121|| URL ||   ||
    22 || Omni URN || ||
    23 || Sample Rspecs || ||
     22|| Sample Rspecs || DO YOU HAVE AN EXAMPLE WE CAN POINT TO HERE.  LOOKING FOR DESCRIPTION OF MNG RESOURCES IN PGENI RSPEC FORMAT ||
    2423[[BR]]
    2524= Aggregate Management =
    26 || Aggregate Operator || Flux Research Group, School of Computing, University of Utah. http://www.cs.utah.edu/flux/ ||
    27 || Resource Owner || Flux Research Group, School of Computing, University of Utah. http://www.cs.utah.edu/flux/ ||
    28 || Operation POC || [mailto:testbed-ops@emulab.net Testbed operations] ||
    29 || Technical POC || [mailto:ricci@cs.utah.edu Robert Ricci] ||
    30 || Developer Links || Source code: http://www.emulab.net/software.php3. Developer mailing list: [mailto:geni-dev@emulab.net] ||
     25|| Aggregate Operator || Department of Computer Science and Engineering, University of Washington. http://www.cs.washington.edu/ ||
     26|| Resource Owner || Most of the resources in this aggregate are owned by individuals and institutions that have volunteered resources for research and education. ||
     27|| Operation POC || [mailto:testbed-ops@emulab.net Testbed operations] <- WHO SHOULD THIS BE FOR MNG? ||
     28|| Technical POC || [mailto:justinc@cs.washington.edu Justin Cappos] ||
     29|| Developer Links || Developer portal: https://seattle.cs.washington.edu/wiki/ContributorsPage. ||