Changes between Version 1 and Version 2 of OperationalMonitoring/UseCases


Ignore:
Timestamp:
04/18/14 10:24:18 (7 years ago)
Author:
rirwin@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OperationalMonitoring/UseCases

    v1 v2  
    22
    33This page describes the use cases.
     4
     5=== Simple Rack Health (use case 3) ===
     6
     7Use case description: Track node compute utilization, interface, and health statistics for shared rack nodes, and allow operators to get notifications when they are out of bounds
     8
     9Use case implementation story: Node statistics are time-series data, and are either collected on the node and pushed to the compute aggregate, or polled from each node by the compute aggregate (doesn't matter for our purposes). Statistics end up in a local database on each rack. Any group of operators that wants to send notifications on these statistics runs a collector, which polls all racks of interest to that group. The collector shares current values with an alerting service, which sends alerts.
     10
     11{{{
     12#!html
     13
     14<table border="0" style="float:center">
     15  <tr>
     16       <td> <img src="http://groups.geni.net/geni/attachment/wiki/OperationalMonitoring/Overview/use_case_3.png?format=raw" width="285" height="300"> </td>
     17  </tr>
     18  <caption align="bottom"> <b> Simple Rack Health Statistics </b></caption>
     19</table>
     20}}}
     21
     22=== Sliver Usage (use case 6) ===
     23
     24Use case description: Find out what slivers will be affected by a maintenance or outage of some resource, and get contact information for the owners of those slivers so targeted notifications can be sent
     25
     26Use case implementation story: Aggregates collect up-to-date information about what slivers exist and what resources they have reserved (including sliver details such as expiration time), and make this information available via a local datastore. GENI trust authorities (e.g. clearinghouses) collect up-to-date information about experimenters and their contact information, and make this information available via a local datastore. Operators who want to be able to get this information run a collector which can query the relevant datastores (since this is an on-demand real-time query, the collector doesn't need to be active all the time, though it may be). The collector data is used to run a report listing affected experimenters and their contact info.
     27{{{
     28#!html
     29
     30<table border="0" style="float:center">
     31  <tr>
     32       <td> <img src="http://groups.geni.net/geni/attachment/wiki/OperationalMonitoring/Overview/use_case_6.png?format=raw" width="300" height="285"> </td>
     33  </tr>
     34  <caption align="bottom"> <b> Sliver Resource Allocations </b></caption>
     35</table>
     36}}}
     37=== External Checks Datastore for Control and Data Plane Monitoring ===
     38
     39
     40{{{
     41#!html
     42
     43<table border="0" style="float:center">
     44  <tr>
     45       <td> <img src="http://groups.geni.net/geni/attachment/wiki/OperationalMonitoring/Overview/extck_store_cp_dp.png?format=raw" width="400" height="285"> </td>
     46  </tr>
     47  <caption align="bottom"> <b> External Check Datastore part of Monitoring Control and Data Planes </b></caption>
     48</table>
     49}}}
     50
     51=== Aggregate Datastores for Control and Data Plane Monitoring ===
     52
     53
     54{{{
     55#!html
     56
     57<table border="0" style="float:center">
     58  <tr>
     59       <td> <img src="http://groups.geni.net/geni/attachment/wiki/OperationalMonitoring/Overview/agg_store_cp_dp.png?format=raw" width="400" height="285"> </td>
     60  </tr>
     61  <caption align="bottom"> <b> Aggregate Datastores part of Monitoring Control and Data Planes </b></caption>
     62</table>
     63}}}
     64