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
< GOCDB‎ | Release4‎ | Development
Revision as of 18:05, 24 January 2012 by Davidm (talk | contribs)
Jump to navigation Jump to search

<< Back to GOCDB/Documentation_Index
<< Back to GOCDB/Release4/Development

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.xsd] [Sample Docs]

Data Models

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 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 enity).
  • 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 (excluding historical and future downtimes).