Changes between Version 1 and Version 2 of OperationalMonitoring/DataSchema20


Ignore:
Timestamp:
08/27/14 12:39:03 (5 years ago)
Author:
dwiggins@bbn.com
Comment:

change some schema datestamps from 0501 to 0828

Legend:

Unmodified
Added
Removed
Modified
  • OperationalMonitoring/DataSchema20

    v1 v2  
    22
    33== REST Data Schema ==
    4 All of these inherit from the [http://unis.incntre.iu.edu/schema/20120709/networkresource network resource schema] with the exception of the opsconfig schema (which inherits from [http://unis.incntre.iu.edu/schema/20120709/domain domain schema]).
    5 
    6  * [http://www.gpolab.bbn.com/monitoring/schema/20140501/opsconfig]: operational configuration metadata, including locations of and information about other datastores
    7  * [http://www.gpolab.bbn.com/monitoring/schema/20140501/aggregate]: metadata about an aggregate (including lists of resources and slivers at that aggregate, and where to look for measurements about the aggregate)
    8  * [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)
    9  * [http://www.gpolab.bbn.com/monitoring/schema/20140501/port]: metadata about a network interface (including resource properties termed "config" above)
    10  * [http://www.gpolab.bbn.com/monitoring/schema/20140501/port-vlan]: metadata about a tagged VLAN subinterface of a network interface
    11  * [http://www.gpolab.bbn.com/monitoring/schema/20140501/sliver]: metadata about a sliver at an aggregate, including resources to which that sliver is mapped
    12  * [http://www.gpolab.bbn.com/monitoring/schema/20140501/authority]: metadata about a GENI authority (including lists of GENI users and slivers at that authority)
    13  * [http://www.gpolab.bbn.com/monitoring/schema/20140501/slice]: metadata about a slice at an authority, including GENI users with roles on that slice
    14  * [http://www.gpolab.bbn.com/monitoring/schema/20140501/user]: metadata about a GENI user at an authority, including contact information
    15  * [http://www.gpolab.bbn.com/monitoring/schema/20140501/experiment]: metadata about an operational monitoring experiment for monitoring the dataplane.
    16  * [http://www.gpolab.bbn.com/monitoring/schema/20140501/data]: 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.
     4All of these inherit from the [http://unis.incntre.iu.edu/schema/20120709/networkresource UNIS network resource schema] with the exception of the opsconfig schema.
     5
     6 * [http://www.gpolab.bbn.com/monitoring/schema/20140828/opsconfig opsconfig]: operational configuration metadata, including locations of and information about other datastores
     7 * [http://www.gpolab.bbn.com/monitoring/schema/20140828/aggregate aggregate]: metadata about an aggregate (including lists of resources and slivers at that aggregate, and where to look for measurements about the aggregate)
     8 * [http://www.gpolab.bbn.com/monitoring/schema/20140828/node 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)
     9 * [http://www.gpolab.bbn.com/monitoring/schema/20140828/interface interface]: metadata about a network interface (including resource properties termed "config" above)
     10 * [http://www.gpolab.bbn.com/monitoring/schema/20140828/interfacevlan interfacevlan]: metadata about a tagged VLAN subinterface of a network interface
     11 * [http://www.gpolab.bbn.com/monitoring/schema/20140828/sliver sliver]: metadata about a sliver at an aggregate, including resources to which that sliver is mapped
     12 * [http://www.gpolab.bbn.com/monitoring/schema/20140828/authority authority]: metadata about a GENI authority (including lists of GENI users and slivers at that authority)
     13 * [http://www.gpolab.bbn.com/monitoring/schema/20140828/slice slice]: metadata about a slice at an authority, including GENI users with roles on that slice
     14 * [http://www.gpolab.bbn.com/monitoring/schema/20140828/user user]: metadata about a GENI user at an authority, including contact information
     15 * [http://www.gpolab.bbn.com/monitoring/schema/20140828/experiment experiment]: metadata about an operational monitoring experiment for monitoring the dataplane.
     16 * [http://www.gpolab.bbn.com/monitoring/schema/20140828/data data]: 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.
    1717 * For now, we would use the `ops_monitoring` namespace for operations monitoring, meaning:
    1818   * When we add monitoring-relevant optional properties to objects, we'll put them in an `ops_monitoring` dictionary