Changes between Version 28 and Version 29 of OperationalMonitoring/DatastorePolling


Ignore:
Timestamp:
05/01/14 17:23:13 (6 years ago)
Author:
rirwin@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OperationalMonitoring/DatastorePolling

    v28 v29  
    88This page describes the API to be used to poll Local datastores for monitoring data.   The API will be developed with a polling mechanism first.  Overview:
    99
    10  * Polls are done from the collector to the Local datastore via a REST API which returns JSON text.  All JSON text is
     10 * Polls are done from the collector to the Local datastore via a REST API which returns JSON text.
    1111
    1212 * First, the Collector polls a Local datastore at '/info/' of the local store url to get information about what the datastore has.  This is done through multiple polls, outlined below. 
     
    2727If the collector is tracking sliver and slice info, the collector 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.
    2828
    29 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 nodes' info at that local datastore.
     29The API does not support querying multiple objects in a single info query.  For example, <datastore_url>/info/node/ will not return all the nodes' info at that local datastore.
    3030
    3131== Data Queries ==