Difference between revisions of "GOCDB/Release4/Development/GLUE2Compatibility"
Line 29: | Line 29: | ||
==GOCDB to GLUE2 Mapping== | ==GOCDB to GLUE2 Mapping== | ||
The diagrams below show how the GOCDB data maps to the GLUE2 XML rendering. | 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 probably have a 'flat' rendering as opposed to a nested/heirarchical structure shown below. | |||
[[File:GocdbGlue2Mapping1.jpg|720px|center|GOCDB to GLUE2 Mapping A]] | [[File:GocdbGlue2Mapping1.jpg|720px|center|GOCDB to GLUE2 Mapping A]] | ||
<br/> | <br/> | ||
[[File:GocdbGlue2Mapping2.jpg|720px|center|GOCDB to GLUE2 Mapping B]] | [[File:GocdbGlue2Mapping2.jpg|720px|center|GOCDB to GLUE2 Mapping B]] |
Revision as of 17:37, 5 September 2012
<< 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.
Useful links:
- [Glue2 Gridforge home]
- [GLUE2.xsd]
- [Latest Glue2.xsd on Github]
- [Sample Docs]
- [GOCDB GLUE2 Compatiblity, EGI UF 2012 Munich]
- [Proposal to update the GLUE2 XSD] The glue2 working group is currently considering a proposal to introduce AbstractService and AbstractEndpoint elements into the glue2.xsd with accompanying xsd:substitutionGroups to define concrete service and endpoint elements.
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 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 probably have a 'flat' rendering as opposed to a nested/heirarchical structure shown below.