GOCDB/Release4/Development/GLUE2Compatibility
<< Back to GOCDB/Documentation_Index
<< Back to GOCDB/Release4/Development
<< Back to GOCDB/Release4/Development/MultipleGRIS
Background
GLUE2 defines an OGF standard for describing data similar in scope to the GOCDB data (Sites, Admin Domains, Services, Service Endpoints, Downtimes etc). A proposal exists for GOCDB to generate valid GLUE2 XML documents and expose these via the PI.
[Glue2 Gridforge home] [GLUE2.xsd] [Latest Glue2.xsd on Github] [Sample Docs] [GOCDB GLUE2 Compatiblity, EGI UF 2012 Munich]
Data Models and Downtimes
There is a difference between the GOCDB and GLUE2 data models. In GLUE2, downtimes are defined against individual Endpoint entities, while in GOCDB downtimes are defined against the Service as a whole (the ServiceEndpoint entity).
To address this issue we propose the following:
- A service in gocdb currently links to one ‘Endpoint_Location’ entity, which in turn wraps the service's URL (other glue2 Endpoint attributes such as WSDL can easily be added to the Endpoint_Location entity).
- We are planning to make the cardinality of this relationship one-to-many.
- In doing this, with a bit of query2Xml conversion, it should be possible to generate GLUE2.xsd compatible documents from the gocdb data.
- Since GLUE2 defines only one downtime per Service Endpoint (the next/current downtime), the proposed GOCDB GLUE2 docs would only show the next/current downtime for the service (historical and future downtimes would be excluded).