Changes between Version 5 and Version 6 of OperationalMonitoring/Overview

Timestamp:

02/18/14 10:04:30 (10 years ago)

Author:

rirwin@bbn.com

Comment:

--

OperationalMonitoring/Overview

@@ -32 +32 @@
 == Use Cases ==
 
-=== Detail of proposed monitoring system components for (use case 3) ===
+=== Simple Rack Health (use case 3) ===
 
 Use 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
@@ -49 +49 @@
 }}}
 
+=== Sliver Usage (use case 6) ===
+
+Use 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
+
+Use 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 an aggregator which can query the relevant datastores (since this is an on-demand real-time query, the aggregator doesn't need to be active all the time, though it may be). The aggregator data is used to run a report listing affected experimenters and their contact info.
+{{{
+#!html
+
+<table border="0" style="float:center">
+  <tr>
+       <td> <img src="http://groups.geni.net/geni/attachment/wiki/OperationalMonitoring/Overview/use_case_6.png?format=raw" width="300" height="285"> </td>
+  </tr>
+  <caption align="bottom"> <b> Sliver Resource Allocations </b></caption>
+</table>
+}}}