Changes between Version 16 and Version 17 of InstMeasCurrentDesignTopicsAll


Ignore:
Timestamp:
02/16/12 11:33:32 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InstMeasCurrentDesignTopicsAll

    v16 v17  
    5454[wiki:InstMeasTopic_4.2UseCasesExperimenters  Work in Progress]  [[BR]]
    5555
    56 === 1)  Goals ===
     561)  Goals  [[BR]]
    5757
    5858 From Sec. 2 of  the GENI I&M Architecture document:  [[BR]]
     
    6767 Define use cases for a wide range of experiments:  complex (by skilled experimenters) to simple (by novice experimenter, i.e., a student)  [[BR]]
    6868
    69 ===  2)  Tasks ===
     692)  Tasks  [[BR]]
    7070
    7171 Provide a concise but complete definition of I&M Use Cases for Experiments [[BR]]
     
    8181
    8282
    83 === 3)  Team ===
     833)  Team  [[BR]]
    8484 
    8585 CO-LEAD  Jim Griffioen (U Kentucky)  [[BR]]
     
    9999[wiki:InstMeasTopic_4.3UseCasesInfrastructure  Work in Progress]  [[BR]]
    100100
    101 1)  Definition of topic:  [[BR]]
    102 
    103 a)  Delineate what infrastructure monitoring is and is not covered by this approach.  [[BR]]
    104   1)  Yes:  monitoring of clusters/racks [[BR]]
    105   2)  Yes:  passive measurements of transport switches, etc.  [[BR]]
    106   3)  Yes:  active measurements of IP networks, of Layer 2 and OpenFlow paths [[BR]]
    107 
    108 b)  Nominal infrastructure measurement process:  [[BR]]
    109   1)  Setup persistent or on-demand infrastructure measurement slice.  [[BR]]
    110   2)  Make passive measurements or make active measurements.  [[BR]]
    111   3)  Gather MD, and observe as it is gathered;  formulate MDOD.  [[BR]]
    112   4)  Store MD in collector, describe with MDOD, and register MDOD so that MD can be shared.  [[BR]]
    113   5)  Typically share MD with Aggregate Operator, GMOC and/or Experimenters, per policy written into MDOD.  [[BR]]
    114   6)  Pull MD out of collector, analyze and visualize.  [[BR]]
    115   7)  Archive MD with MDOD.  [[BR]]
    116   8)  Share archived MD with others, per policy included within MDOD.  [[BR]]
    117   9)  Pull MD out of archive, to analyze and/or visualize.   [[BR]]
    118 
    119 c)  What support must be provided for Operator?  how?  [[BR]]
    120 
    121 2)  Who: LEAD  Martin Swany (Indiana U);  Eric Boyd (Internet2);  Jason Zurawski (Internet2);  Prasad Calyam  (Ohio Super Center);  Chris Small (Indiana U);  Ilia Baldine, for ExoGENI racks (RENCI);  ?, for InstaGENI racks (HP);  ?, for GMOC [[BR]]
     1011)  Goals  [[BR]]
     102
     103 From Sec. 2 of  the GENI I&M Architecture document:  [[BR]]
     104
     105  In addition, the GENI operations staff require extensive and reliable instrumentation and measurement capabilities to monitor and troubleshoot the GENI suite and its constituent entities.  Some of this data will be made available to experimenters, to help them conduct useful and repeatable experiments.   [[BR]]
     106
     107  The GMOC, providing GENI-wide operator services, needs to monitor essentially all GENI infrastructure on a 24x7 basis.  In this case, the GMOC Operator will gather, analyze and present MD that monitors hundreds of infrastructure elements.  [[BR]]
     108
     109
     1102)  Tasks  [[BR]]
     111
     112 Provide a concise but complete definition of I&M Use Cases for Infrastructure Measurement [[BR]]
     113
     114 Identify the support that should be available to operators  [[BR]]
     115
     116 Update the [http://groups.geni.net/geni/wiki/GeniInstrumentationandMeasurementsArchitecture  GENI I&M Architecture document]:  [[BR]]
     117   Sec. 3.3.  I&M Use cases for Central Operators (i.e., GMOC)  [[BR]]
     118   Sec. 3.4.  I&M Use cases for Aggregate Providers and Operators  [[BR]]
     119   Sec. 4.2.2  Typical Arrangements of I&M Services:  For Operator Gathering MD from GENI Infrastructure   [[BR]]
     120   Sec. 4.2.3  Typical Arrangements of I&M Services:  For Experimenters Gathering MD from their Slice and from GENI Infrastructure [[BR]]
     121   Sec. 4.3.3  Type 3 I&M Service:  Common Service with MD for Multiple Slices  [[BR]]
     122
     123 Use as guidance in the design of GENI I&M tools, particularly for the GEMINI and GIMI projects  [[BR]]
     124
     125
     126
     1273)  Team  [[BR]]
     128 
     129 LEAD  Martin Swany (Indiana U) [[BR]]
     130 Guilherme Fernandes  (?)  [[BR]]
     131 Eric Boyd (Internet2) [[BR]]
     132 Jason Zurawski (Internet2) [[BR]]
     133 Prasad Calyam  (Ohio Super Center) [[BR]]
     134 Chris Small, for NetKarma (Indiana U) [[BR]]
     135 Ilia Baldine, for ExoGENI racks (RENCI) [[BR]]
     136 Jonathan Mills (RENCI)  [[BR]]
     137 ?, for InstaGENI racks (HP) [[BR]]
     138 ?, for GMOC [[BR]]
     139 Sarah Edwards (GPO) [[BR]]
     140 Chaos Golubitski (GPO) [[BR]]
     141 Harry Mussman  (GPO) [[BR]]
    122142
    123143== 4.4)  GENI Environment  ==