Changes between Version 4 and Version 5 of MonitoringArch
- Timestamp:
- 06/06/12 18:33:48 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MonitoringArch
v4 v5 26 26 The 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. 27 27 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.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 its authoritative source. 29 29 30 30 === Path Forward === … … 192 192 193 193 Data 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? 197 196 198 197 Services Needed … … 200 199 201 200 Interested 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. 203 202 * Who needs to alert on this: None. Done on demand. 204 203 … … 301 300 And finally, the I&M infrastructure collects and stores [#IMData data]. 302 301 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.302 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. 304 303 305 304 === Relationships to other parts of GENI === … … 321 320 networks). GENI Meta-operations is the authoritative source for 322 321 GENI-wide monitoring data (e.g. end-to-end 323 connectivity across the GENI backbone). In addition,322 connectivity across GENI). In addition, 324 323 meta-operations is the authoritative source of monitoring data provided by 325 324 aggregates, campuses and experimenters (when appropriate). For … … 333 332 The monitored data accessible from meta-operations is invariably collected by measuring the 334 333 state of the world (for example, by polling a node periodically to see 335 if it is operational) whereas the data availablevia the GENI334 if it is operational) whereas the data via the GENI 336 335 Clearinghouse is based on transitions (for example, an 337 aggregate informs the GENI Clearinghouse about the creation of a sliver at it 's aggregatefor336 aggregate informs the GENI Clearinghouse about the creation of a sliver at its aggregate, for 338 337 which it definitively knows the resource allocated, the creator, and the 339 338 creation time). … … 366 365 The accuracy of the data can be described as either: transition-based or sampled. 367 366 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 definitivedata 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". 369 368 370 369 ''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. … … 375 374 The ''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. 376 375 377 ''Meta-operations'' is the authoritative source for operationally critical data from various aggregates and campuses. Examples of data stored in meta-operations ispolled 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. 378 377 379 378 ''Instrumentation & Measurement'' is the authoritative source for data collected in the course of individual experiments.