Changes between Version 9 and Version 10 of GENIOperationsTrial


Ignore:
Timestamp:
06/15/15 17:40:41 (9 years ago)
Author:
hdempsey@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIOperationsTrial

    v9 v10  
    77= GENI Operations Responsibilities =
    88
    9 GENI Operations groups need to track and hand activities off to each other, based on the type of GENI event that happens.  Following is a table of organizations that provide support listed by area of operations responsibility:
     9GENI Operations groups need to track and hand activities off to each other, based on the type of GENI event that happens.  Following is a table of organizations that provide support listed by their area(s) of operations responsibility:
     10 
    1011 
    1112|| ''' Team '''        ||'''mail list'''|| ''' Area of !Responsibility/Tools''' ||
     
    1617|| Nick Bastin Dev* ||nick.bastin@gmail.com||FOAM and !FlowVisor ||
    1718|| RENCI !Ops/Dev ||exogeni-ops@renci.org ||ExoGENI Racks, ExoGENI Stitching ||
    18 || UKY !Ops/Dev || geni-ops@googlegroups.com  ||GENI Monitoring System, Stitching Computation System ||
    19 || U of Utah Ops||geni-ops@googlegroups.com ||InstaGENI Racks ||
     19|| UKY !Ops/Dev || geni-ops@googlegroups.com  ||GENI Monitoring System, Stitching Computation System (IG rack endpoints) (Note, UKY is coming up to speed on IG racks) ||
     20|| U of Utah Ops||geni-ops@googlegroups.com ||InstaGENI Racks (Note, Utah is gradually transitioning some IG activities to UKY) ||
    2021|| OpenGENI Ops||TBD ||OpenGENI Racks ||
    2122|| Utah Dev || geni-dev-utah@flux.utah.edu||  Jacks Tool,  Emulab, Apt||