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.
Difference between revisions of "GOCDB/Release4/Development/GLUE2Compatibility"
| Line 25: | Line 25: | ||
===Data Models and Downtimes=== | ===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. | <!-- | ||
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:Glue2GocdbCompare.jpg|650px|center|Core entity comparison between gocdb and glue2]]--> | ||
[[File:GocdbGlue2DataModels.jpg|680px|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: | 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> | |||
* 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. | 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. | ||
Revision as of 14:19, 10 October 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/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 public comment:
- GLUE2 XML rendering http://redmine.ogf.org/boards/9/topics/10
Useful links:
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