Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

GOCDB/Release4/Development/GLUE2Compatibility

From EGIWiki
Jump to navigation Jump to search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


GOC DB menu: Home 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. The Glue2 XSD is currently in development and a first GFD draft for public commment is expected to be released during OGF 37 (11-13 March).

Useful links:


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).


Core entity comparison between gocdb and glue2


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 as explained at GOCDB/Release4/Development/MultipleGRIS.
  • In doing this, with a bit of query2Xml conversion, it will be possible to generate GLUE2.xsd compatible documents from the gocdb data (see below).
  • 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).

GOCDB to GLUE2 Mapping

The diagrams below show how the GOCDB data maps to the GLUE2 XML rendering. Note, the sample XML is subject to change (the GLUE2 XSD is currently being finalized and will have a 'flat' rendering as opposed to a nested/heirarchical structure.