Changes between Version 4 and Version 5 of MonitoringArch


Ignore:
Timestamp:
06/06/12 18:33:48 (7 years ago)
Author:
sedwards@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MonitoringArch

    v4 v5  
    2626The operational monitoring architecture describes operational monitoring use cases which motivate the document and then describes the architecture including various actors, monitoring interfaces, and data collected.
    2727
    28 There are different ways of collecting data in GENI and the operational monitoring architecture describes one way of doing so (others include the future GENI Clearinghouse and Instrumentation and Measurement (I&M) infrastructure). In general, there is an authoritative party which is responsible for making each piece of data available. However that data can be shared or cached with other entities that need it. Likewise, there may be several portals or interfaces for accessing and viewing the data, but each portal should retrieve data from it's authoritative source.
     28There are different ways of collecting data in GENI and the operational monitoring architecture describes one way of doing so (others include the future GENI Clearinghouse and Instrumentation and Measurement (I&M) infrastructure). In general, there is an authoritative party which is responsible for making each piece of data available. However that data can be shared or cached with other entities that need it. Likewise, there may be several portals or interfaces for accessing and viewing the data, but each portal should retrieve data from its authoritative source.
    2929
    3030=== Path Forward ===
     
    192192
    193193Data to Collect
    194  * Points of contacts for various groups which are members of the GENI federation
    195  * Which resources are allocated to which slice.
    196  * Which IP address maps to which resource.
     194 * Points of contacts for various groups that are members of the GENI federation
     195 * For a given IP address, which resource and slice does it map to?
    197196
    198197Services Needed
     
    200199
    201200Interested Parties
    202  * Who needs to query this: Meta-operations and other operators.
     201 * Who needs to query this: Meta-operations and other operators. Perhaps LLR.
    203202 * Who needs to alert on this: None.  Done on demand.
    204203
     
    301300And finally, the I&M infrastructure collects and stores [#IMData data].
    302301
    303 Information about which resources are reserved in which slices may optionally be reported by the aggregate to the clearinghouse.  In the absence of this reporting aggregates should report this information to meta-operations directly.
     302Information about which resources are reserved in which slices may optionally be reported by the aggregate to the clearinghouse.  In the absence of this reporting, aggregates should report this information to meta-operations directly.
    304303
    305304=== Relationships to other parts of GENI ===
     
    321320networks).  GENI Meta-operations is the authoritative source for
    322321GENI-wide monitoring data (e.g. end-to-end
    323 connectivity across the GENI backbone). In addition,
     322connectivity across GENI). In addition,
    324323meta-operations is the authoritative source of monitoring data provided by
    325324aggregates, campuses and experimenters (when appropriate).  For
     
    333332The monitored data accessible from meta-operations is invariably collected by measuring the
    334333state of the world (for example, by polling a node periodically to see
    335 if it is operational) whereas the data available via the GENI
     334if it is operational) whereas the data via the GENI
    336335Clearinghouse is based on transitions (for example, an
    337 aggregate informs the GENI Clearinghouse about the creation of a sliver at it's aggregate for
     336aggregate informs the GENI Clearinghouse about the creation of a sliver at its aggregate, for
    338337which it definitively knows the resource allocated, the creator, and the
    339338creation time). 
     
    366365The accuracy of the data can be described as either: transition-based or sampled.
    367366
    368 ''transition-based'' data, like that made available by the GENI Clearinghouse, is data based on the knowledge of the entities being created or destroy.  An example of definitive data is "slice S was created at time T by user U".
     367''transition-based'' data, like that made available by the GENI Clearinghouse, is data based on the knowledge of the entities being created or destroyed.  An example of transition-based data is "slice S was created at time T by user U".
    369368
    370369''Sampled'' data, like that made available by GENI Meta-operations, is collected by measuring the state of the world periodically.  An example of sample data is the availability of an interface over time.
     
    375374The ''GENI clearinghouse'' is the authoritative source for information about GENI primitives like slices, projects, and users and event information about the creation and deletion of those same primitives.
    376375
    377 ''Meta-operations'' is the authoritative source for operationally critical data from various aggregates and campuses.  Examples of data stored in meta-operations is polled cpu usage and interface statistics on GENI compute resources.
     376''Meta-operations'' is the authoritative source for operationally critical data from various aggregates and campuses.  Examples of data stored in meta-operations are polled cpu usage and interface statistics on GENI compute resources.
    378377
    379378''Instrumentation & Measurement'' is the authoritative source for data collected in the course of individual experiments.