Adopting GLUE 2.0 for Interoperation of Grid
Monitoring Systems
Timo Baur, Rebecca Breu, Tobias Lindinger, Anne Milbert,
Gevorg Pogoshyan, Mathilde Romberg
Leibniz Superc omputer Centre, Garching, Germany
Max Planck Institute for Gravitational Physics, Golm, Germany
Forschungszentrum Karlsruhe GmbH, Karlsruhe, Germany
Forschungszentrum Jџlich GmbH, Jџlich, Germany
Ludwig -Maximilians-Univers ity Munich, Germany
D-MON Team
CGW 08
Outline
•
•
•
•
•
•
•
•
Interoperability
Grid Monitoring Scenario
Integration Proxy Approach
GLUE 2.0 for Schema Mediation
Architecture
Implementation Experiences
Examples
Lessons learned
CGW 08
Interoperability
•
middleware architectures
•
•
•
•
•
enable interoperable manageability of a Grid’s services
for all vital components which need a cross-provider functionality
usually one -and only one- middleware or management architecture
Architecture constitutes finite technical border for component interaction
components of multiple Grid projects do not interoperate on a technical
level
• diverse spectrum of implementations
• multiple middlewares
• middleware-agnostic components
•
caused by concurrent co-implementation of resources, services and
components by multiple autonomous organizations
• differing understanding of Grid paradigm
• differing tastes, targets and realisation requirements
• differing standards, implementations, versions
CGW 08
Grid Monitoring Scenario
•
to enable comprehensive operations and management
–
–
Fault, Configuration, Accounting, Performance, Security
Grid Operation Centre, User Support, Scheduling
•
D-Grid would require Grid-wide monitoring repositories
•
on top of a broad spectrum of non-interoperable and heterogeneous
monitoring services
How can we realize this without regularly refactoring all components ?
CGW 08
Integration Proxy Approach
•
Low intrusive adaptor modules
–
Process:
•
•
•
•
proxy repository
–
–
•
Extract: connect to interfaces (XML)
Transform: translate information
models (XSLT)
Load: upload data to repository
(SQL)
store data
possibility to federate database
standardized data provisioning
–
–
–
for users (Webinterface) and
services
possibility to feed integrated data
back into source systems
support VO-specific views on data
CGW 08
Adopting GLUE 2.0 for Schema Mediation
•
GLUE 2.0
– adequate information model for
mediation of Grid resource and service
monitoring data
– describes a Grid‘s main characteristics:
Schema B
• VO modelling (UserDomains)
• mapping and access policies
– allocation of resources and services to
VOs
• resource and service scenarios
• resource provider modeling
(AdminDomains)
– extendable
– standardization (OGF draft)
Schema A
CGW 08
Architecture
CGW 08
Experiences
•
data transformation, e.g. GLUE 1.1. -> GLUE 2.0
– not everything is mappable
– differences in syntax and semantics
– possible loss of information
•
gathered and transformed most important data without loss of accuracy,
e.g.
– ComputingResources
– ComputingServices
– StorageResources
•
our prototype provides VO specific views on the data
– mappings of resources into VOs retrieved rom GRRS (Grid Resource
Repository Service)
– which acts as policy information base for VO resource management
– accordingly generates AccessPolicies and database views
CGW 08
Examples
• ComputingService (DB)
• VO-specific View (OGSA-DAI)
CGW 08
Lessons learned
• GLUE 2.0 fits well for resource and service monitoring in Grids
• monitoring gateways can be used to interoperably cache and
exchange resource and service monitoring data
• views can be generated for different VOs
.... thank you for your attention
CGW 08