Changes between Version 2 and Version 3 of InstMeasTopic_4.3UseCasesInfrastructure


Ignore:
Timestamp:
02/10/12 17:52:20 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InstMeasTopic_4.3UseCasesInfrastructure

    v2 v3  
    1010
    1111 Update the [http://groups.geni.net/geni/wiki/GeniInstrumentationandMeasurementsArchitecture  GENI I&M Architecture document]:  [[BR]]
    12    Sec. 3.1.  I&M Use cases for Experimenters  [[BR]]
    13    Sec. 4.3.1  Type 1 I&M Service:  Service Contained within a Slice  [[BR]]
     12   Sec. 3.3.  I&M Use cases for Central Operators (i.e., GMOC)  [[BR]]
     13   Sec. 3.4.  I&M Use cases for Aggregate Providers and Operators  [[BR]]
     14   Sec. 4.2.2  Typical Arrangements of I&M Services:  For Operator Gathering MD from GENI Infrastructure   [[BR]]
     15   Sec. 4.2.3  Typical Arrangements of I&M Services:  For Experimenters Gathering MD from their Slice and from GENI Infrastructure [[BR]]
     16   Sec. 4.3.3  Type 3 I&M Service:  Common Service with MD for Multiple Slices  [[BR]]
    1417
    1518 Use as guidance in the design of GENI I&M tools, particularly for the GEMINI and GIMI projects  [[BR]]
     
    1720== 4.3.2)  Issues ==
    1821
    19  1)  Can an Operator (e.g., GMOC) ever see MD owned by an Experimenter, e.g., to verify acceptable use of GENI resources or to troubleshoot problems in GENI infrastructure?  If so, how?  [[BR]]
     22 
    2023
    21 == 4.3.2)  Team ==
     24== 4.3.3)  Team ==
    2225 
    23  LEAD  Martin Swany (Indiana U)
    24  Eric Boyd (Internet2)
    25  Jason Zurawski (Internet2)
    26  Prasad Calyam  (Ohio Super Center)
    27  Chris Small (Indiana U);  Ilia Baldine, for ExoGENI racks (RENCI);  ?, for InstaGENI racks (HP);  ?, for GMOC [[BR]]
     26 LEAD  Martin Swany (Indiana U) [[BR]]
     27 Eric Boyd (Internet2) [[BR]]
     28 Jason Zurawski (Internet2) [[BR]]
     29 Prasad Calyam  (Ohio Super Center) [[BR]]
     30 Chris Small, for NetKarma (Indiana U) [[BR]]
     31 Ilia Baldine, for ExoGENI racks (RENCI) [[BR]]
     32 ?, for InstaGENI racks (HP) [[BR]]
     33 Luke Fowler?, for GMOC [[BR]]
     34 Sarah Edwards (GPO) [[BR]]
     35 Chaos Golubitski (GPO) [[BR]]
    2836 Harry Mussman  (GPO) [[BR]]
    2937
    30 == 4.2.3)  Meetings ==
     38== 4.2.4)  Meetings ==
    3139
    3240 Review with operators at GEC13  [[BR]]
    3341
     42== 4.2.5)  Vision ==
     43
     44 From Sec. 2 of  the GENI I&M Architecture document:  [[BR]]
     45
     46  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]]
     47
     48  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]]
    3449
    3550
    36 1)  Definition of topic:  [[BR]]
    3751
    38 a)  Delineate what infrastructure monitoring is and is not covered by this approach.  [[BR]]
    39   1)  Yes:  monitoring of clusters/racks [[BR]]
    40   2)  Yes:  passive measurements of transport switches, etc.  [[BR]]
    41   3)  Yes:  active measurements of IP networks, of Layer 2 and OpenFlow paths [[BR]]
     52== 4.2.6  Definition ==
    4253
    43 b)  Nominal infrastructure measurement process:  [[BR]]
     54 Definition of infrastructure monitoring:  [[BR]]
     55  1)  Passive monitoring of clusters/racks, including transport switches, etc.  [[BR]]
     56  2)  Event monitoring, provides log entries  [[BR]]
     57  3)  Active measurements of IP networks, of Layer 2 and OpenFlow paths [[BR]]
     58
     59== 4.2.7  Passive Monitoring Options ==
     60
     61 1)  Aggregate operator establishes MP to gather MD via SNMP, organizes into time-series data, and formulates MDOD [[BR]]
     62  1b)  Directly from cluster/switch/etc. [[BR]]
     63  1c)  Via Ganglia [[BR]]
     64  1d   Via Nagios [[BR]]
     65  1e)  Via Cacti [[BR]]
     66
     67 2)  MD sinks: [[BR]]
     68  2b)  Local aggregate operator [[BR]]
     69  2c)  GMOC  (when authorized) [[BR]]
     70  2d)  Experimenter (when authorized) [[BR]]
     71
     72 3)  MD format and interface: [[BR]]
     73  3b)  Time-series data, presented at perfSONAR MA, MDOD registered at global UNIS, can be pulled by authorized user, and presented using perfSONAR service  [[BR]]
     74  3c)  Time-series data, pushed using OML protocol, to OML server, and presented using GIMI service [[BR]]
     75  3d)  Time-series data, pushed using GMOC protocol, to GMOC server, and presented using ? service [[BR]]
     76  3e)  Time-series data, published to XML messaging service, can be subscribed by authorized user, and presented using ? service [[BR]]
     77
     78
     79== 4.2.8  Event Monitoring Options ==
     80
     81 1)  Aggregate operator establishes MP to issue Event Records (ERs)   [[BR]]
     82 
     83 2)  ER sinks: [[BR]]
     84  2b)  Local aggregate operator [[BR]]
     85  2c)  GMOC  (when authorized) [[BR]]
     86  2d)  Clearinghouse (when authorized) [[BR]]
     87  2e)  Experimenter (when authorized) [[BR]]
     88
     89 3)  ER format and interface: [[BR]]
     90  3b)  Follows XML format defined by NetKarma, adapted from MDOD  [[BR]]
     91  3c)  Published to XML messaging service, can be subscribed by authorized user, logged using ? service, presented using ? service [[BR]]
     92
     93
     94== 4.2.9  Active Measurement Options ==
     95
     96 1)  Owner: [[BR]]
     97  1b)  Aggregate operator [[BR]]
     98  1c)  GMOC [[BR]]
     99  1d)  Experimenter [[BR]]
     100
     101 2)  Owner establishes slice, includes active measurements, and formulates MDOD [[BR]]
     102  2b)  Persistent [[BR]]
     103  2c)  On-demand [[BR]]
     104
     105 3)  MD sinks: [[BR]]
     106  3b)  Owner [[BR]]
     107  3c)  Aggregate operator  (when authorized) [[BR]]
     108  3d)  GMOC  (when authorized) [[BR]]
     109  3e)  Experimenter (when authorized) [[BR]]
     110
     111 4)  MD format and interface: [[BR]]
     112  4b)  Time-series data, presented at perfSONAR MA, MDOD registered at global UNIS, can be pulled by authorized user, and presented using perfSONAR service  [[BR]]
     113  4c)  Time-series data, pushed using OML protocol, to OML server, and presented using GIMI service [[BR]]
     114
     115 5) Active measurements: [[BR]]
     116  5b)  For IP networks, i.e., ping and iperf [[BR]]
     117  5c)  Specialized for L2 networks [[BR]]
     118  5d)  Specialized for OF networks [[BR]]
     119
     120== 4.2.10  Active Measurement Process ==
     121
     122 Baseline infrastructure measurement process:  [[BR]]
    44123  1)  Setup persistent or on-demand infrastructure measurement slice.  [[BR]]
    45124  2)  Make passive measurements or make active measurements.  [[BR]]
     
    52131  9)  Pull MD out of archive, to analyze and/or visualize.   [[BR]]
    53132
    54 c)  What support must be provided for Operator?  how?  [[BR]]
     133== 4.2.11  Support for Operators ==
    55134
    56 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]]
     135 What support must be provided for Operator?  how?  [[BR]]
     136