Changes between Version 13 and Version 14 of OperationalMonitoring/DataSchema20


Ignore:
Timestamp:
08/28/14 11:29:07 (5 years ago)
Author:
dwiggins@bbn.com
Comment:

address Luisa's comments

Legend:

Unmodified
Added
Removed
Modified
  • OperationalMonitoring/DataSchema20

    v13 v14  
    2222}}}
    2323
    24 <aggregate-id> is usually the aggregate's GENI-assigned nickname (short name).
     24<aggregate-id> is usually the aggregate's GENI-assigned nickname (common name).
    2525
    2626Example REST call for aggregate gpo-ig:
     
    449449If <list of object ids> is "*", it means "all objects known to the datastore of type <object type name>."
    450450
    451 The response is a list "[...]" in which each element conforms to the  [http://www.gpolab.bbn.com/monitoring/schema/20140828/data data]: data schema], [http://www.gpolab.bbn.com/monitoring/schema/20140828/data.schema.jwc commented version of the data schema].
     451The response is a list "[...]" in which each element conforms to the  [http://www.gpolab.bbn.com/monitoring/schema/20140828/data data schema], [http://www.gpolab.bbn.com/monitoring/schema/20140828/data.schema.jwc commented version of the data schema].
    452452Each element of the list applies to one (eventType, object id) pair.
    453453
     
    669669
    670670Retrieves a variety of configuration information, including:
    671 * locations (URLs) of and information about other datastores
    672 * GENI authorities
    673 * Database schemas used to store monitoring information
    674 * A list of possible event types for time-series measurements
     671 * locations (URLs) of and information about other datastores
     672 * GENI authorities
     673 * Database schemas used to store monitoring information
     674 * A list of possible event types for time-series measurements
    675675
    676676Example REST call for geni-prod,  a hypothetical config datastore listing production aggregates and authorities: