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"
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
--> | --> | ||
===Multiple Endpoints Per Service=== | ===Multiple Endpoints Per Service=== | ||
Revision as of 11:16, 15 April 2014
| Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
| GOC DB menu: | Home • | Documentation Index • |
Current Developments
The developments we are currently working on are listed below. They come from the agreed development list, as defined by the Operational Tools Advisory Group (OTAG) who filters and prioritizes user requests.
- See: [GOCDB development items is available in the EGI RT ticket tracker]
- Also priortised in following doc: https://documents.egi.eu/secure/ShowDocument?docid=1997
Multiple Endpoints Per Service
Render GOCDB data in GLUE2 Format
Add downtime PI method
- [Not confirmed] Programatic/writable PI query to insert downtimes as an alternative to the portal GUI.
- Probably would use GLUE2 XML as message format (GFD is in prep).
- RT: https://rt.egi.eu/rt/Ticket/Display.html?id=4935
- [Not confirmed] Support for VOs (maybe query SEs by supported VO)
[Not confirmed] Regionalisation- RT: https://rt.egi.eu/rt/Ticket/Display.html?id=2788
- GOCDB4 Regionalisation Status and Plans - More details on regionalisation and progress of Standalone deployments within NGIs.
- GOCDB/Release4/Regionalisation/Transfer_Mechanism
- GOCDB/Release4/Regionalisation/Data_Transfer_Format
- GOCDB/Release4/Regionalisation/PI_Updates
- [Not confirmed] VO Feed for ATP GOCDB/Release4/Development/VSites/VOFeedXML
- Use the Service Groups (VSites) to build a VO feed for ATP.