Difference between revisions of "GOCDB/Release4/Development/GLUE2Compatibility"
(34 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Template:Op menubar}} | |||
{{Template:GOCDB_menubar}} | |||
{{TOC_right}} | |||
[[Category:GOCDB]] | |||
<< Back to [[GOCDB/Release4/Development]] <br/> | |||
<< Back to [[GOCDB/Release4/Development/MultipleEndpointsPerService]] | |||
===Background=== | ===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 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. | ||
[[https://forge.ogf.org/svn/repos/glue/XSD/trunk/schema/GLUE2.xsd GLUE2.xsd]] | Useful links: | ||
[[https://forge.ogf.org/svn/repos/glue/XSD/trunk/schema/glue-sample0.xml Sample Docs]] | * Published Glue2 XSD/XML specification: http://www.ogf.org/documents/GFD.209.pdf | ||
* [[http://redmine.ogf.org/projects/glue-wg Glue2 home]] | |||
* [[http://redmine.ogf.org/dmsf/glue-wg?folder_id=31 Glue2 wiki]] | |||
<!-- | |||
*[[https://forge.ogf.org/sf/projects/glue-wg Glue2 Gridforge home]] | |||
*[[https://forge.ogf.org/svn/repos/glue/XSD/trunk/schema/GLUE2.xsd GLUE2.xsd]] | |||
*[[https://github.com/OGF-GLUE/XSD/blob/master/schema/GLUE2.xsd Latest Glue2.xsd on Github]] | |||
*[[https://forge.ogf.org/svn/repos/glue/XSD/trunk/schema/glue-sample0.xml Sample Docs]] | |||
*[[https://www.egi.eu/indico/getFile.py/access?contribId=206&sessionId=70&resId=3&materialId=slides&confId=679 GOCDB GLUE2 Compatiblity, EGI UF 2012 Munich]] | |||
*[[http://redmine.ogf.org/dmsf/glue-wg?folder_id=32 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. The schema is also flat rather than heirarchical. | |||
--> | |||
===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. --> | |||
<!--[[File:Glue2GocdbCompare.jpg|650px|center|Core entity comparison between gocdb and glue2]]--> | |||
<!--[[File:GocdbGlue2DataModels.jpg|680px|center|Core entity comparison between gocdb and glue2]]---> | |||
As per https://ggus.eu/ws/ticket_info.php?ticket=93966 and [[GOCDB/Release4/Development/MultipleGRIS]] there appears to be a requirement to define downtimes selectively against different member endpoints of the same service (like GLUE2). This would require the following changes to the GOCDB data model to become more GLUE2 centric: | |||
* Allow a single Service to define <b>many Endpoints</b> | |||
If this would address the requirements, then this will require some changes to the XML output of the ‘get_service_endpoint’ and ‘get_downtime’ PI methods with repercussions on other systems. Therefore, any proposed change would have to be widely agreed/tested. | |||
[[File:GocdbGlue2EntityModel.jpg|350px|center|Glue2 compatible gocdb data model]] | |||
[[ | <!-- | ||
* 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, Downtimes will be linked. | |||
* 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== | |||
TODO | |||
<!-- | |||
[[File:GocdbGlue2Mapping1.jpg|720px|center|GOCDB to GLUE2 Mapping A]] | |||
<br/> | |||
[[File:GocdbGlue2Mapping2.jpg|720px|center|GOCDB to GLUE2 Mapping B]] | |||
--> |
Latest revision as of 11:48, 2 December 2013
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/MultipleEndpointsPerService
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:
- Published Glue2 XSD/XML specification: http://www.ogf.org/documents/GFD.209.pdf
- [Glue2 home]
- [Glue2 wiki]
Data Models and Downtimes
As per https://ggus.eu/ws/ticket_info.php?ticket=93966 and GOCDB/Release4/Development/MultipleGRIS there appears to be a requirement to define downtimes selectively against different member endpoints of the same service (like GLUE2). This would require the following changes to the GOCDB data model to become more GLUE2 centric:
- Allow a single Service to define many Endpoints
If this would address the requirements, then this will require some changes to the XML output of the ‘get_service_endpoint’ and ‘get_downtime’ PI methods with repercussions on other systems. Therefore, any proposed change would have to be widely agreed/tested.
GOCDB to GLUE2 Mapping
TODO