Changes between Version 50 and Version 51 of OperationalMonitoring/DataSchema


Ignore:
Timestamp:
03/31/14 10:59:47 (8 years ago)
Author:
rirwin@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OperationalMonitoring/DataSchema

    v50 v51  
    2121 * [http://www.gpolab.bbn.com/monitoring/schema/20140131/slice]: (inherits from [http://unis.incntre.iu.edu/schema/20120709/networkresource]): metadata about a slice at an authority, including GENI users with roles on that slice
    2222 * [http://www.gpolab.bbn.com/monitoring/schema/20140131/user]: (inherits from [http://unis.incntre.iu.edu/schema/20120709/networkresource]): metadata about a GENI user at an authority, including contact information
     23 * [http://www.gpolab.bbn.com/monitoring/schema/20140131/monitoringexperiment]: metadata about an operational monitoring experiment for monitoring the dataplane.
    2324 * [http://www.gpolab.bbn.com/monitoring/schema/20140131/data]: novel schema based on a combination of [http://unis.incntre.iu.edu/schema/20120709/metadata] and [http://unis.incntre.iu.edu/schema/20120709/tsdatum], contains both metadata and data about measurements.
    2425 * For now, we would use the `ops_monitoring` namespace for operations monitoring, meaning:
     
    3435 * `https://datastore.instageni.gpolab.bbn.com/`: datastore for gpo-ig aggregate
    3536 * `https://datastore.ch.geni.net/`: datastore for ch.geni.net authority
     37 * `https://datastore.externalchecks.geni.net/`: datastore for external checks in the monitoring framework (e.g. inter-aggregate pings, AM external availability)
    3638
    3739==== Data about operational monitoring configuration ====
     
    373375}
    374376}}}
     377
     378==== Data about an operational monitoring experiment ====
     379
     380Operational monitoring measures the dataplane with a set of simple tests between aggregates described using [http://www.gpolab.bbn.com/monitoring/schema/20140131/monitoringexperiment# the operational monitoring experiment schema].  Examples:
     381 Hypothetical REST call for missouri-ig to gpo-ig rtt experiment:
     382{{{
     383https://datastore.externalchecks.geni.net/info/experiment/missouri-ig_to_gpo-ig_rtt
     384}}}
     385 Response:
     386{{{
     387{
     388  "$schema": "http://www.gpolab.bbn.com/monitoring/schema/20140131/monitoringexperiment#",
     389  "id": "missouri-ig_to_gpo-ig_rtt",
     390  "selfRef": "https://datastore.externalchecks.geni.net/info/experiment/missouri-ig_to_gpo-ig_rtt",
     391  "slice_urn": "urn:publicid:IDN+ch.geni.net:gpo-infra+slice+tuptyexclusive",
     392  "slice_uuid": "8c6b97fa-493b-400f-95ee-19accfaf4ae8",
     393  "ts": 1391192685740849,
     394  "source_aggregate": {
     395    "urn": "urn:publicid:IDN+instageni.missouri.edu+authority+cm",
     396    "href": "https://datastore.instageni.missouri.edu/info/aggregates/missouri-ig"
     397  },
     398  "destination_aggregate": {
     399    "urn": "urn:publicid:IDN+instageni.gpolab.bbn.com+authority+cm",
     400    "href": "https://datastore.instageni.gpolab.bbn.com/info/aggregates/gpo-ig"
     401  }
     402}}}
     403
    375404
    376405==== Measurements used for the use cases ====