Changes between Initial Version and Version 1 of GeniAggregate/MissouriInstaGENI


Ignore:
Timestamp:
10/09/13 16:46:09 (10 years ago)
Author:
asydney@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniAggregate/MissouriInstaGENI

    v1 v1  
     1= InstaGENI Aggregate  =
     2
     3'''Enter aggregate name'''
     4
     5This InstaGENI aggregate supports the GENI Aggregate Provider Agreement (mm/dd/yyyy).
     6
     7= InstaGENI Aggregate Overview =
     8
     9|| Aggregate Manager URL || Enter Compute Aggregate: https://instageni.example.edu:12369/protogeni/xmlrpc/am or FOAM: https://foam.example.edu:3626/foam/gapi/1 ||
     10|| Aggregate Manager URN || Enter Compute URN: urn:publicid:IDN+instageni.sample.edu+authority+cm or FOAM URN urn:publicid:IDN+openflow:foam:foam.instageni.dample.edu+authority+am ||
     11|| Aggregate Manager Common Name || Enter site common name ||
     12|| Aggregate Resources || An InstaGENI aggregate includes 5 Hosts (3 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.  Rack servers are HP !ProLiant DL380p Gen8. ||
     13|| Typical Experiments || InstaGENI 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 ||
     30|| Resource Owner     || Enter PI that is responsible for site. This entry may also be same as POC ||
     31|| Technical POC      || [mailto:instageni-ops@flux.utah.edu]   ||
     32|| Developer Links    || Software pages: [https://wiki.emulab.net/Emulab/wiki/GitRepository InstaGENI],  [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/InstageniRacks InstaGENI Racks Project]; Developer mailing list: [mailto:instageni-design@geni.net] ||