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.
GOCDB/Release4/Development/VSites/VOFeedXML
< GOCDB | Release4 | Development | VSites
Jump to navigation
Jump to search
VO Feed Example
VO feed for the GOCDB EGI scoped data (ATP will recognize this gocdb data as the 'OPS' VO topology feed).
- This VO feed will include every 'EGI' scoped Physical Site, and each will be represented with an <atp_site> element.
- All services of that site will be nested as ATP <service> elements, regardless of scope (including both EGI and Local).
- The GOCDB Virtual Sites that aggregate those Services will be listed using child APT <group> elements.
- The feed specifies that all sites are under the ops VO using the <vo>OPS</vo> element.
In summary, the GOCDB to ATP mappings are:
- Site == <atp_site>
- ServiceEndpoint == <service>
- VSite == <group>
Questions for ATP:
- We've left the infrast="EGEE" attribute on the atp_site element. Is this correct?
todo