Changes between Version 10 and Version 11 of OperationalMonitoring/DataSchema20

Timestamp:

08/27/14 20:58:34 (10 years ago)

Author:

dwiggins@bbn.com

Comment:

--

OperationalMonitoring/DataSchema20

@@ -7 +7 @@
 This page gives examples of these REST calls and responses.
 These examples assume the following (fictitious) local datastore URLs.
-For simplicitly, we show one local datastore per aggregate here, but the architecture does ''not'' require that --- it would be perfectly fine to have the data for an aggregate be split among multiple datastores.
+For simplicitly, we show one local datastore per aggregate here, but the architecture does ''not'' require that.  It is fine to have the data for an aggregate be split among multiple datastores.
  * `https://datastore.geni.net/`: datastore containing configuration data for operational monitoring
  * `https://datastore.instageni.gpolab.bbn.com/`: datastore for gpo-ig aggregate
@@ -13 +13 @@
  * `https://datastore.externalchecks.geni.net/`: datastore for external checks in the monitoring framework (e.g. inter-aggregate pings, AM external availability)
 
-
 ==== Aggregate call and response ====
 
-Aggregates are indexed by GENI-agreed short name.
-
-data about an aggregate (including lists of resources and slivers at that aggregate, and where to look for measurements about the aggregate)
+Retrieves information about an aggregate, including lists of resources and slivers at that aggregate, version information, and where to look for measurements about the aggregate.
+
+General form of the REST call:
+{{{
+https://<datastore-host>/info/aggregate/<aggregate-id>
+}}}
+
+<aggregate-id> is usually the aggregate's GENI-assigned nickname (short name).
+
 Example REST call for aggregate gpo-ig:
 {{{
 https://datastore.instageni.gpolab.bbn.com/info/aggregate/gpo-ig
 }}}
-Response conforms to the [http://www.gpolab.bbn.com/monitoring/schema/20140828/aggregate# aggregate schema], [http://www.gpolab.bbn.com/monitoring/schema/20140828/aggregate# commented version of the aggregate schema].
+Response conforms to the [http://www.gpolab.bbn.com/monitoring/schema/20140828/aggregate# aggregate schema], [http://www.gpolab.bbn.com/monitoring/schema/20140828/aggregate.schema.jwc commented version of the aggregate schema].
 {{{
 {
@@ -99 +104 @@
 https://datastore.grnoc.iu.edu/info/link/arbitrary_id_001
 }}}
-Response conforms to the [http://www.gpolab.bbn.com/monitoring/schema/20140828/link# link schema], [http://www.gpolab.bbn.com/monitoring/schema/20140828/link.schema.jwc# commented version of the link schema].
+Response conforms to the [http://www.gpolab.bbn.com/monitoring/schema/20140828/link# link schema], [http://www.gpolab.bbn.com/monitoring/schema/20140828/link.schema.jwc commented version of the link schema].
 {{{
 {
@@ -312 +317 @@
 https://externalcheckstore.gpolab.bbn.com/info/externalcheck/gpo
 }}}
-Response conforms to the [http://www.gpolab.bbn.com/monitoring/schema/20140828/externalcheck external check schema], [http://www.gpolab.bbn.com/monitoring/schema/20140828/externalcheck commented version of the external check schema], .
+Response conforms to the [http://www.gpolab.bbn.com/monitoring/schema/20140828/externalcheck external check schema], [http://www.gpolab.bbn.com/monitoring/schema/20140828/externalcheck.schema.jwc commented version of the external check schema], .
 {{{
 {