Changes between Version 7 and Version 8 of GeniAggregate/UtahUEN-OpenFlow


Ignore:
Timestamp:
10/08/12 14:03:18 (7 years ago)
Author:
joe.breen@utah.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniAggregate/UtahUEN-OpenFlow

    v7 v8  
    2020|| 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). ||
    2121|| Usage Policies || Aggregate specific policies on who can use resources, how many resources can be held for how long, etc. ||
    22 || Aggregate Manager URL     || URL for AM compatible with GENI AM API e.g. https://foam.example.edu:3626/foam/gapi/1 ||
     22|| Aggregate Manager URL     || https://foamyflow.chpc.utah.edu:3626/foam/gapi/1 ||
    2323|| Sample RSpecs             || Cut-and-paste text RSpecs that work for your resources ||
    2424[[BR]]
    2525= 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 ||
    29 || Technical POC || Contact information for the PI or research team that develops/maintains the aggregate ||
    30 || Developer Links ||   OpenFlow announcement list: https://mailman.stanford.edu/mailman/listinfo/openflow-announce
    31 OpenFlow development list: https://mailman.stanford.edu/mailman/listinfo/openflow-dev
    32 OpenFlow discussion list: https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
    33 OpenFlow Indigo firmware list: https://mailman.stanford.edu/mailman/listinfo/openflow-indigo
    34 OpenFlow announcement list: https://mailman.stanford.edu/mailman/listinfo/openflow-announce  ||
     26|| Aggregate Operator || Primary Contact: Emulab Operations group http://www.emulab.net/ will be the first contact for Operations since the device is handling [wiki:GeniAggregate/UtahProtoGeni ProtoGENI] and the GENI OpenFlow resources.  mailto:testbed-ops@flux.utah.edu  [[BR]]  Secondary Contact: Univ. of Utah Center for High Performance Computing (CHPC) http://www.chpc.utah.edu issues@chpc.utah.edu ||
     27|| Resource Owner || University of Utah and Utah Education Network - http://groups.geni.net/geni/wiki/UTAHREGIONAL||
     28|| Operation POC || Primary Contact: testbed-ops@flux.utah.edu [[BR]]  Secondary Contact: issues@chpc.utah.edu ||
     29|| Technical POC || issues@chpc.utah.edu ||
     30|| Developer Links ||   OpenFlow announcement list: https://mailman.stanford.edu/mailman/listinfo/openflow-announce [[BR]] OpenFlow development list: https://mailman.stanford.edu/mailman/listinfo/openflow-dev [[BR]] OpenFlow discussion list: https://mailman.stanford.edu/mailman/listinfo/openflow-discuss [[BR]] OpenFlow Indigo firmware list: https://mailman.stanford.edu/mailman/listinfo/openflow-indigo [[BR]] OpenFlow announcement list: https://mailman.stanford.edu/mailman/listinfo/openflow-announce  ||