Changes between Version 7 and Version 8 of OperationalMonitoring/DatastorePolling

Timestamp:

02/17/14 17:04:49 (10 years ago)

Author:

rirwin@bbn.com

Comment:

--

OperationalMonitoring/DatastorePolling

@@ -18 +18 @@
 The aggregator retrieves from a config local datastore (to be developed and is hardcoded for now), a set of urls of local datastores that are associated with one or more aggregate managers (AMs).  This allows the aggregator to poll local datastores for information about the data associated with each local datastore and AM at <datastore_url>/info/aggregate/<aggregate_id>.  The information returned is a list of properties about the aggregate as well as a list of nodes, slivers, and VLANs (slivers and VLANs not implemented as of 17-Feb).   Here is  [wiki:OperationalMonitoring/DataSchema#Dataaboutanaggregate a detailed example of an aggregate info query].
 
-The aggregator will then query for information about particular objects one at a time (i.e., a node).  The query returns a list of properties about the object as well as a list of associated objects (i.e., a node's interfaces).  In this example, a node info query will be at <datastore_url>/info/node/<node_id>.  Here is a [wiki:OperationalMonitoring/DataSchema#Dataaboutanode a detailed example of a node info query].
+The aggregator will then query for information about particular objects one at a time (i.e., a node).  The query returns a list of properties about the object as well as a list of associated objects (i.e., a node's interfaces).  In this example, a node info query will be at <datastore_url>/info/node/<node_id>.  Here is a [wiki:OperationalMonitoring/DataSchema#Dataaboutanode a detailed example of a node info query].  The aggregator would repeat for other nodes it received in the list in the aggregate info query.
+
+Depending on what the aggregator is supporting above it in the form of different monitoring applications, it may continue querying the local datastore about objects or resources it has data about.  They are of similar form.  Here are links to examples:
+
+ * [wiki:OperationalMonitoring/DataSchema#Dataaboutaninterface An example interface query]
+ * [wiki:OperationalMonitoring/DataSchema#DataaboutaGENIsliver An example sliver query]
+
+If the aggregator is tracking sliver and slice info, the aggregator may also be directed to a slice authority local datastore, which is a different datastore than one containing shared host nodes.  Here is a [wiki:OperationalMonitoring/DataSchema#Dataaboutasliceauthority detailed example slice query], and here is a [wiki:OperationalMonitoring/DataSchema#DataaboutaGENIuser detailed example of a user query].  Both of these queries are of similar form with <datastore_url>/info/slice/<slice_id> and <datastore_url>/info/user/<user_id> respectively.
+
+As of 17-Feb, we currently do not support querying multiple objects in a single info query.  For example, <datastore_url>/info/node/ will not return all the node info at the local datastore.
+
+== Data Queries ==
+
 
 The REST noun and JSON format include the following: