Difference between revisions of "GOCDB/Release4/Development/GLUE2Compatibility"
< GOCDB | Release4 | Development
Jump to navigation
Jump to search
(Created page with '===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 propos…') |
|||
Line 7: | Line 7: | ||
===Data Models=== | ===Data Models=== | ||
There is a difference between the GOCDB and GLUE2 data models. In GLUE2, downtimes are defined against individual service Endpoint entities, while in GOCDB downtimes are defined against the Service as a whole. | There is a difference between the GOCDB and GLUE2 data models. In GLUE2, downtimes are defined against individual service Endpoint entities, while in GOCDB downtimes are defined against the Service as a whole. | ||
To address this issue we propose the following: | 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 | * 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. | * 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. | * 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). | * 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). |
Revision as of 19:00, 24 January 2012
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 service Endpoint entities, while in GOCDB downtimes are defined against the Service as a whole.
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).