Changes between Version 1 and Version 2 of GeniAggregate/SoxInstaGENI


Ignore:
Timestamp:
10/22/13 09:30:22 (6 years ago)
Author:
tupty@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniAggregate/SoxInstaGENI

    v1 v2  
    33'''Enter aggregate name'''
    44
    5 This InstaGENI aggregate supports the GENI Aggregate Provider Agreement (mm/dd/yyyy).
     5This InstaGENI aggregate supports the GENI Aggregate Provider Agreement (10/21/2013).
    66
    77= InstaGENI Aggregate Overview =
    88
    9 || Aggregate Manager URL || Enter Compute Aggregate: https://instageni.example.edu:12369/protogeni/xmlrpc/am or FOAM: https://foam.example.edu:3626/foam/gapi/2 ||
    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 ||
     9|| Aggregate Manager URL || https://instageni.sox.net:12369/protogeni/xmlrpc/am ||
     10|| Aggregate Manager URN || urn:publicid:IDN+instageni.sox.net+authority+cm ||
     11|| Aggregate Manager Common Name || sox-ig ||
    1212|| 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. ||
    1313|| 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.  ||
     
    1616|| Slice Authorities Recognized ||GENI Portal (https://portal.geni.net), ProtoGENI (http://www.emulab.net) ||
    1717|| 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. ||
     18|| Layer 2 Connectivity || Connects via the [http://groups.geni.net/geni/wiki/GeniAggregate/SoxOpenFlow SOX OpenFlow Network] ||
    1919
    2020For Compute Aggregate or FOAM, <<Insert Site Diagram Here>> Make sure to note firewalls, if any, on both control (layer 3) and data paths.
    21 
    22 For FOAM Aggregate only, insert <<Insert !OpenFlow Port List Here>>.  Otherwise remove this port list item for compute resource aggregate.
    2321
    2422
     
    2725= Aggregate Management =
    2826
    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.||
     27|| Aggregate Operator || [http://www.sox.net Southern Crossroads] ||
     28|| Resource Owner     || [http://www.sox.net Southern Crossroads] ||
    3129|| Technical POC      || [mailto:instageni-ops@flux.utah.edu]   ||
    3230|| 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] ||