Changes between Version 21 and Version 22 of OperationalMonitoring/DataSchema
- Timestamp:
- 02/11/14 15:26:49 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OperationalMonitoring/DataSchema
v21 v22 82 82 83 83 I 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: 84 * [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 84 85 * [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) 85 86 * [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) 86 87 * [http://unis.incntre.iu.edu/schema/20120709/port]: metadata about a network interface (including resource properties termed "config" above) 88 * [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 89 * [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) 90 * [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 91 * [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 87 92 * [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. 88 * [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 mapped89 93 * For now, we would use the `ops_monitoring` namespace for operations monitoring, meaning: 90 94 * When we add monitoring-relevant optional properties to objects, we'll put them in an `ops_monitoring` dictionary