Changes between Version 5 and Version 6 of InstMeasTopic_4.3UseCasesInfrastructure


Ignore:
Timestamp:
02/15/12 16:27:56 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InstMeasTopic_4.3UseCasesInfrastructure

    v5 v6  
    2828
    2929
    30  
    3130
    3231== 3)  Team ==
     
    5857
    5958
    60 == 5)  Issues ==
     59== 5)  Open Issues ==
    6160
    62  1) Identify which passive measurement and monitoring options are to be supported [[BR]]
    63  2) Identify which event monitoring options are to be supported [[BR]]
    64  3) Identify which active measurement options are to be supported [[BR]]
    6561
    6662== 6)  Definition ==
     
    7167  3)  Active measurements of IP networks, of Layer 2 and OpenFlow paths [[BR]]
    7268
    73 == 4.2.7  Passive Measurement and Monitoring Options ==
     69== 7) Passive Measurement and Monitoring ==
     70
     71=== 1)  Supported Options ===
    7472
    7573 1)  Aggregate operator establishes MP to gather MD via SNMP, organizes it into time-series data, and formulates MDOD [[BR]]
     
    9290  6)  Time-series data, published to XML messaging service, subscribed transfer service that pushes using GMOC protocol, to GMOC server, and presented using ? service [[BR]]
    9391
     92=== 2)  Open Issues ===
    9493
    95 == 4.2.8  Event Monitoring Options ==
     94 
     95 1) Identify which passive measurement and monitoring options are to be supported [[BR]]
     96 2)  Need final definition of MDOD schema, and MDOD creation software [[BR]]
     97
     98== 8)  Event Monitoring ==
     99
     100=== 1)  Options ===
    96101
    97102 1)  Aggregate operator establishes MP to issue Event Records (ERs)   [[BR]]
    98103 
    99  2)  ER sinks: [[BR]]
    100   2b)  Local aggregate operator [[BR]]
    101   2c)  GMOC  (when authorized) [[BR]]
    102   2d)  Clearinghouse (when authorized) [[BR]]
    103   2e)  Experimenter (when authorized) [[BR]]
     104 2)  ER users: [[BR]]
     105  1)  Local aggregate operator [[BR]]
     106  2)  GMOC  (when authorized) [[BR]]
     107  3)  Clearinghouse (when authorized) [[BR]]
     108  4)  Experimenter (when authorized) [[BR]]
    104109
    105  3)  ER format and interface: [[BR]]
    106   3b)  Follows XML format defined by NetKarma, adapted from MDOD  [[BR]]
    107   3c)  Published to XML messaging service, can be subscribed by authorized user, logged using ? service, presented using ? service [[BR]]
     110 3)  ER interface transfers: [[BR]]
     111  1)  ER schema, published to XML messaging service, can be subscribed by authorized user, logged using ? service, presented using ? service [[BR]]
     112
     113=== 2)  Open Issues ===
     114
     115 1) Identify which event monitoring options are to be supported [[BR]]
     116 2) Need final definition of Event Record schema, XML format defined by NetKarma, adapted from MDOD;  include active up/down events
     117
     118== 9) Active Measurements ==
     119
     120=== 1) Options ===
     121
     122 1)  MD owner: [[BR]]
     123  1)  Aggregate operator [[BR]]
     124  2)  GMOC [[BR]]
     125  3)  Experimenter [[BR]]
     126
     127 2)  Owner establishes slice, includes active measurement services, configures emasurements, and formulates MDOD [[BR]]
     128  1)  Persistent long-term slice [[BR]]
     129  2)  On-demand short-term slice, i.e., for troubleshooting [[BR]]
     130
     131 3)  MD users: [[BR]]
     132  1)  Owner [[BR]]
     133  2)  Aggregate operator  (when authorized) [[BR]]
     134  3)  GMOC  (when authorized) [[BR]]
     135  3)  Experimenter (when authorized) [[BR]]
     136
     137 4)  MD interface and transfers: [[BR]]
     138  1)  Time-series data, gathered by perfSONAR MA, presented at perfSONAR interface, MDOD registered at global UNIS, can be pulled by authorized user, and presented using perfSONAR service  [[BR]]
     139  2)  Time-series data, pushed using OML protocol, to OML server, and presented using GIMI service [[BR]]
     140
     141 5) Active measurements: [[BR]]
     142  1)  For IP networks, i.e., ping and iperf [[BR]]
     143  2)  Specialized for L2 networks [[BR]]
     144  3)  Specialized for OF networks [[BR]]
     145
     146=== 2)  Open Issues ===
     147
     148 1) Identify which active measurement options are to be supported [[BR]]
     149 2) Define active measurement strategy for L2 networks [[BR]]
     150 3) Define active measurement strategy for OF networks [[BR]]
    108151
    109152
    110 == 4.2.9  Active Measurement Options ==
    111 
    112  1)  Owner: [[BR]]
    113   1b)  Aggregate operator [[BR]]
    114   1c)  GMOC [[BR]]
    115   1d)  Experimenter [[BR]]
    116 
    117  2)  Owner establishes slice, includes active measurements, and formulates MDOD [[BR]]
    118   2b)  Persistent [[BR]]
    119   2c)  On-demand [[BR]]
    120 
    121  3)  MD sinks: [[BR]]
    122   3b)  Owner [[BR]]
    123   3c)  Aggregate operator  (when authorized) [[BR]]
    124   3d)  GMOC  (when authorized) [[BR]]
    125   3e)  Experimenter (when authorized) [[BR]]
    126 
    127  4)  MD format and interface: [[BR]]
    128   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]]
    129   4c)  Time-series data, pushed using OML protocol, to OML server, and presented using GIMI service [[BR]]
    130 
    131  5) Active measurements: [[BR]]
    132   5b)  For IP networks, i.e., ping and iperf [[BR]]
    133   5c)  Specialized for L2 networks [[BR]]
    134   5d)  Specialized for OF networks [[BR]]
    135 
    136 == 4.2.10  Active Measurement Process ==
     153=== 3) Baseline Process ===
    137154
    138155 Baseline infrastructure measurement process:  [[BR]]
    139156  1)  Setup persistent or on-demand infrastructure measurement slice.  [[BR]]
    140   2)  Make passive measurements or make active measurements.  [[BR]]
     157  2)  Configure and make active measurements.  [[BR]]
    141158  3)  Gather MD, and observe as it is gathered;  formulate MDOD.  [[BR]]
    142159  4)  Store MD in collector, describe with MDOD, and register MDOD so that MD can be shared.  [[BR]]
     
    147164  9)  Pull MD out of archive, to analyze and/or visualize.   [[BR]]
    148165
    149 == 4.2.11 Support for Operators ==
     166== 10)  I&M Support for Operators ==
    150167
    151168 What support must be provided for Operator?  how?  [[BR]]