Changes between Version 2 and Version 3 of InstaGENITemplateAggregate


Ignore:
Timestamp:
02/14/13 16:19:49 (7 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InstaGENITemplateAggregate

    v2 v3  
    66
    77= InstaGENI Aggregate Overview =
    8 || Aggregate Resources || Brief description of the types and numbers of resources provided by the aggregate ||
    9 || Typical Experiments || InstaGENI is suited for experiments that require a controllable, predictable, and repeatable network environment. Experimenters can get virtual machines or dedicated PCs on which they have full "root" access, run an operating system of their choice, and connect nodes in an arbitrary topology.   ||
    10 || Aggregate Web Page || Link to web page with information about the aggregate ||
    11 || Aggregate Status || Link to monitoring web page with current status (operational status, resources available, etc) ||
    12 || Layer 2 Connectivity || Which GENI core networks, if any, or other layer 2 networks connect to this aggregate?  Please include a network diagram of GENI resource connectivity if possible.  Make sure to note firewalls, if any, on both control (layer 3) and data paths.||
     8
     9|| Aggregate Resources || An InstaGENI aggregate includes 5 Hosts (2 VM Servers and 3 dedicated PCs) that can load experimenter specified OS image s. Racks support !OpenFlow topologies.   ||
     10|| 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 an operating system of their choice, and connect nodes in an arbitrary topology that can support !OpenFlow.  ||
     11|| Aggregate Status || Monitoring is not widely available at this time.  There is restricted access monitoring at https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl ||
     12|| Layer 2 Connectivity || List GENI core networks, if any, or other layer 2 networks connect to this aggregate.  Please include a network diagram of GENI resource connectivity if possible.  Make sure to note firewalls, if any, on both control (layer 3) and data paths.||
     13
     14For !OpenFlow Aggregate only, insert the following item:
     15
     16<<Insert Site Diagram HERE>>
     17
     18<<Insert OF Port List Here>>
     19
     20
    1321[[BR]]
    14 = InstaGENI Experimenter Support =
    15 || Guides and Documents || Links to docs/web pages describing how experimenters can request, program/configure and control aggregate resources. If at all possible, help docs should include example experiments that use the aggregate resources. ||
    16 || Support || Link to experimenter support mailing list.  If available, information on mailing lists, newsgroups, blogs, call centers, etc. set up to support experimenters using aggregate resources. ||
    17 || Compatible Tools || Experiment control tools, instrumentation tools and programming tools that are compatible with this aggregate. ||
    18 [[BR]]
     22
    1923= Using this Aggregate =
    20 || Slice Authorities Recognized || Currently in GENI, a slice authority issues the user certificate, the user credential, and the slice credential. List recognized slice authorities in this space such as the GENI Project Office (http://pgeni.gpolab.bbn.com), ProtoGENI (http://www.emulab.net), and/or PlanetLab (http://www.planet-lab.org). ||
     24
     25|| Slice Authorities Recognized ||GENI Project Office (http://pgeni.gpolab.bbn.com), ProtoGENI (http://www.emulab.net) ||
    2126|| Usage Policies || Aggregate specific policies on who can use resources, how many resources can be held for how long, etc. ||
    2227|| Aggregate Manager URL     || URL for AM compatible with GENI AM API e.g. https://foam.example.edu:3626/foam/gapi/1 ||
    23 || Sample RSpecs             || Cut-and-paste text RSpecs that work for your resources ||
    2428[[BR]]
     29
    2530= Aggregate Management =
    26 || Aggregate Operator || Name of organization that operates the aggregate manager. Link to URL of organization. ||
    27 || Resource Owner || Name(s) of the organization(s) that owns the aggregate resources, if different from the operator of the aggregate manager. If this information cannot be provided (such as with aggregates consisting of contributed resources), provide a statement about who provides the resources. ||
    28 || Operation POC || Contact information for person or team that operates this aggregate ||
     31
     32|| Operator/Resource Owner || Enter Site Administrator/Site contact information for person or team that operates this aggregate ||
     33|| Operation POC || instageni-ops@flux.utah.edu, instageni-ops@gpolab.bbn.com ||
    2934|| Technical POC || Contact information for the PI or research team that develops/maintains the aggregate ||
    30 || Developer Links || Links to aggregate code base, design docs, developer mailing lists, etc. ||
     35|| Developer Links || IG Software: https://wiki.emulab.net/Emulab/wiki/GitRepository,  FOAM: https://openflow.stanford.edu/fisheye/browse/FOAM; !FlowVisor, InstaGENI design docs: http://groups.geni.net/geni/wiki/GENIRacksHome/InstageniRacks, Developer mailing lists: instageni-design@geni.net ||
     36