Changes between Version 59 and Version 60 of OperationalMonitoring/DataSchema


Ignore:
Timestamp:
05/07/14 12:42:21 (8 years ago)
Author:
rirwin@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OperationalMonitoring/DataSchema

    v59 v60  
    99The details of which data types are needed to meet which use cases, why that data was proposed, and any open questions about the data, are now listed at [wiki:OperationalMonitoring/DataForUseCases].
    1010
    11 == Proposed data schema ==
     11== REST Data Schema ==
    1212
    1313I propose a schema based on, and partially compatible with, [http://unis.incntre.iu.edu/schema/20120709/], for measurement data and metadata.  In particular, i suggest using:
    14  * [http://www.gpolab.bbn.com/monitoring/schema/20140131/opsconfig]: (inherits from [http://unis.incntre.iu.edu/schema/20120709/domain]): operational configuration metadata, including locations of and information about other datastores
    15  * [http://www.gpolab.bbn.com/monitoring/schema/20140131/aggregate]: (inherits from [http://unis.incntre.iu.edu/schema/20120709/domain]): metadata about an aggregate (including lists of resources and slivers at that aggregate, and where to look for measurements about the aggregate)
    16  * [http://unis.incntre.iu.edu/schema/20120709/node]: metadata about a resources (including resource properties termed "config" above, and a list of relevant ports (or of all ports, whichever is easier) on that resource)
    17  * [http://unis.incntre.iu.edu/schema/20120709/port]: metadata about a network interface (including resource properties termed "config" above)
    18  * [http://www.gpolab.bbn.com/monitoring/schema/20140131/port-vlan]: (inherits from [http://unis.incntre.iu.edu/schema/20120709/port]): metadata about a tagged VLAN subinterface of a network interface
    19  * [http://www.gpolab.bbn.com/monitoring/schema/20140131/sliver]: (inherits from [http://unis.incntre.iu.edu/schema/20120709/networkresource]): metadata about a sliver at an aggregate, including resources to which that sliver is mapped
    20  * [http://www.gpolab.bbn.com/monitoring/schema/20140131/authority]: (inherits from [http://unis.incntre.iu.edu/schema/20120709/domain]): metadata about a GENI authority (including lists of GENI users and slivers at that authority)
    21  * [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
    22  * [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.
    24  * [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.
     14 * [http://www.gpolab.bbn.com/monitoring/schema/20140501/opsconfig]: (inherits from [http://unis.incntre.iu.edu/schema/20120709/networkresource]): operational configuration metadata, including locations of and information about other datastores
     15 * [http://www.gpolab.bbn.com/monitoring/schema/20140501/aggregate]: (inherits from [http://unis.incntre.iu.edu/schema/20120709/networkresource]): metadata about an aggregate (including lists of resources and slivers at that aggregate, and where to look for measurements about the aggregate)
     16 * [http://www.gpolab.bbn.com/monitoring/schema/20140501/node]: metadata about a resources (including resource properties termed "config" above, and a list of relevant ports (or of all ports, whichever is easier) on that resource)
     17 * [http://www.gpolab.bbn.com/monitoring/schema/20140501/port]: (inherits from [http://unis.incntre.iu.edu/schema/20120709/networkresource])metadata about a network interface (including resource properties termed "config" above)
     18 * [http://www.gpolab.bbn.com/monitoring/schema/20140501/port-vlan]: (inherits from [http://unis.incntre.iu.edu/schema/20120709/networkresource]): metadata about a tagged VLAN subinterface of a network interface
     19 * [http://www.gpolab.bbn.com/monitoring/schema/20140501/sliver]: (inherits from [http://unis.incntre.iu.edu/schema/20120709/networkresource]): metadata about a sliver at an aggregate, including resources to which that sliver is mapped
     20 * [http://www.gpolab.bbn.com/monitoring/schema/20140501/authority]: (inherits from [http://unis.incntre.iu.edu/schema/20120709/networkresource]): metadata about a GENI authority (including lists of GENI users and slivers at that authority)
     21 * [http://www.gpolab.bbn.com/monitoring/schema/20140501/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
     22 * [http://www.gpolab.bbn.com/monitoring/schema/20140501/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/20140501/experiment]: metadata about an operational monitoring experiment for monitoring the dataplane.
     24 * [http://www.gpolab.bbn.com/monitoring/schema/20140501/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.
    2525 * For now, we would use the `ops_monitoring` namespace for operations monitoring, meaning:
    2626   * When we add monitoring-relevant optional properties to objects, we'll put them in an `ops_monitoring` dictionary