Changes between Initial Version and Version 1 of GeniAggregate/StarLightExoGENI


Ignore:
Timestamp:
05/29/14 14:55:07 (5 years ago)
Author:
tupty@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniAggregate/StarLightExoGENI

    v1 v1  
     1= ExoGENI Aggregate  =
     2
     3'''Enter aggregate name'''
     4
     5This ExoGENI aggregate supports the GENI Aggregate Provider Agreement (mm/dd/yyyy).
     6
     7= ExoGENI Aggregate Overview =
     8
     9|| Aggregate Manager URL || Enter Compute Aggregate: https://example-hn.exogeni.net:11443/orca/xmlrpc or FOAM: https://example-hn.exogeni.net:3626/foam/gapi/2 ||
     10|| Aggregate Manager URN || Enter Compute URN: urn:publicid:IDN+exogeni.net:XXvmsite+authority+am  or FOAM URN: urn:publicid:IDN+openflow:foam:XX-hn.exogeni.net+authority+am ||
     11|| Aggregate Manager Common Name || Enter site common name ||
     12|| Aggregate Resources || An ExoGENI aggregate includes 10 Hosts (8 VM Servers and 2 dedicated PCs) that can load experimenter specified OS images. Racks also support !OpenFlow topologies, usually including extensions onto campus !OpenFlow networks.   ||
     13|| Typical Experiments || ExoGENI provides a controllable, predictable, and repeatable network environment. Experimenters can get virtual machines or dedicated PCs on which they have full "root" access, run available operating systems of their choice, and connect nodes in an arbitrary topology that can support !OpenFlow.  ||
     14|| Sample RSpecs       || Link to RSpecs used successfully for rack site confirmation tests. ||
     15|| Aggregate Status || Operational monitoring not widely available, restricted access to monitoring at [https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl GMOC]||
     16|| Slice Authorities Recognized ||GENI Portal (https://portal.geni.net), ProtoGENI (http://www.emulab.net) ||
     17|| Usage Policies || A  [http://groups.geni.net/geni/attachment/wiki/RUP/RUP.pdf GENI Recommended Use Policy] is available. Site should also add links here to their own usage policies.  ||
     18|| Layer 2 Connectivity || Enter list GENI core networks, if any, or other layer 2 networks that connect to this aggregate. ||
     19
     20For Compute Aggregate or FOAM, <<Insert Site Diagram Here>> Make sure to note firewalls, if any, on both control (layer 3) and data paths.
     21
     22For FOAM Aggregate only, insert <<Insert !OpenFlow Port List Here>>.  Otherwise remove this port list item for compute resource aggregate.
     23
     24
     25[[BR]]
     26
     27= Aggregate Management =
     28
     29|| Aggregate Operator || Enter Site POC information, enter URL of organization.  This can be a person or (preferably) a mailing list that reaches all operators at a site. ||
     30|| Resource Owner     || Enter person that is responsible for site rack overall. This entry may also be same as POC. This is typically the person who would took responsibility for operating and maintaining the rack on behalf of their site, and who would make the final decision on policy that affects the rack such as usage policies.||
     31|| Technical POC      || [mailto:exogeni-ops@renci.org]   ||
     32|| Developer Links    || Software pages: [https://geni-orca.renci.org/trac/browser ExoGENI],  [https://wiki.emulab.net/Emulab/wiki/GitRepository ExoGENI],  [https://openflow.stanford.edu/display/FOAM/Home FOAM], and [https://github.com/OPENNETWORKINGLAB/flowvisor/wiki FlowVisor];  Project page: [http://groups.geni.net/geni/wiki/GENIRacksHome/ExogeniRacks ExoGENI Racks Project]; Developer mailing list: [mailto:exogeni-design@geni.net] ||