Difference between revisions of "Infrastructure Viewer"
m |
|||
| Line 8: | Line 8: | ||
* The '''Data View''' presents the infrastructure organized in Collections. For each collection, the available metadata collection are reported by indicating the number of metadata objects, the format of the metadata, and the number of indices available for such a collection. For each metatada collection the type of indices and number of indexed objects are displayed. | * The '''Data View''' presents the infrastructure organized in Collections. For each collection, the available metadata collection are reported by indicating the number of metadata objects, the format of the metadata, and the number of indices available for such a collection. For each metatada collection the type of indices and number of indexed objects are displayed. | ||
| + | |||
| + | ==Implementation== | ||
| + | ===IV Data manipulation=== | ||
| + | All data show by the IV is retrieved from the IS using the IS-Client. | ||
| + | The profiles retrieved are elaborated to generate the information necessary to map generation. | ||
| + | Because the profiles elaboration require reusing same profiles multiple times a cache level has been inserted between the IS and the IV. | ||
| + | ====ASL Cache==== | ||
| + | The ASL cache aims to reduce the number of queries sent to IS-IC and to cache the retrieved the profiles for successive elaboration. | ||
| + | The ASL cache retrieve all profiles querying the IS-Client with a scheduled period. The profiles are retrieved for each VRE, VO and infrastructure. | ||
| + | |||
| + | |||
| + | There the detailed list of performed queries and retrieved profiles: | ||
| + | ; GCUBEHostingNode: GCUBEGHNQuery | ||
| + | ; GCUBEService: GCUBEServiceQuery | ||
| + | ; GCUBERunningInstance: a modified version of RIQuery so that some RI are not filtered | ||
| + | ; GCUBECollection: GCUBECollectionQuery | ||
| + | ; GCUBEMCollection: GCUBEMCollectionQuery | ||
| + | ; RPDocument: a specialized query to retrieve all XML indexes, common indices | ||
| + | ; GCUBEGenericResource: a specialized query for ScenarioCollectionRetrieving | ||
Revision as of 11:24, 4 August 2009
The Infrastructure Viewer is a monitoring tool that offers a new highly customizable visual infrastructure experience. It relies on TreeMaps technology and it was largely inspired by gridmap.cern.ch by customized and designed to accommodate the gCube needs. It offers three views, each designed to offer an immediate understanding of the infrastructure status.
- The gHN View presents the infrastructure organized in sites. For each site, the gHNs belonging to the site, their status, and the list of RIs per gHN with their status.
- The Service View presents the infrastructure organized in Service Classes. For each service class, the available services and the location and status of the running instances of that service. In particular ‘Outdated’ RIs are RIs whose profile is stored in the Information System but that are not running in any gHN (there are a number of cases that can drive to this anomaly. The new IS-Manager service will manage also these anomalies).
- The Data View presents the infrastructure organized in Collections. For each collection, the available metadata collection are reported by indicating the number of metadata objects, the format of the metadata, and the number of indices available for such a collection. For each metatada collection the type of indices and number of indexed objects are displayed.
Implementation
IV Data manipulation
All data show by the IV is retrieved from the IS using the IS-Client. The profiles retrieved are elaborated to generate the information necessary to map generation. Because the profiles elaboration require reusing same profiles multiple times a cache level has been inserted between the IS and the IV.
ASL Cache
The ASL cache aims to reduce the number of queries sent to IS-IC and to cache the retrieved the profiles for successive elaboration. The ASL cache retrieve all profiles querying the IS-Client with a scheduled period. The profiles are retrieved for each VRE, VO and infrastructure.
There the detailed list of performed queries and retrieved profiles:
- GCUBEHostingNode
- GCUBEGHNQuery
- GCUBEService
- GCUBEServiceQuery
- GCUBERunningInstance
- a modified version of RIQuery so that some RI are not filtered
- GCUBECollection
- GCUBECollectionQuery
- GCUBEMCollection
- GCUBEMCollectionQuery
- RPDocument
- a specialized query to retrieve all XML indexes, common indices
- GCUBEGenericResource
- a specialized query for ScenarioCollectionRetrieving
