Difference between revisions of "GOCDB/Release4/Development/GLUE2Compatibility"
Line 4: | Line 4: | ||
[[Category:GOCDB]] | [[Category:GOCDB]] | ||
<< Back to [[GOCDB/Release4/Development]] <br/> | << Back to [[GOCDB/Release4/Development]] <br/> | ||
<< Back to [[GOCDB/Release4/Development/ | << Back to [[GOCDB/Release4/Development/MultipleEndpointsPerService]] | ||
===Background=== | ===Background=== |
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